Seales gives WI advantage over BD

The visitors were bowled out for just 164


News Desk December 03, 2024

print-news

Jayden Seales registered astonishing figures of 15.5-10-5-4 as West Indies bowled out Bangladesh for 164 on the second day of the second Test at Sabina Park.

Seales' analyses were the most economical in Test cricket since 1977 (minimum 60 balls). In response, West Indies lost Mikyle Louis early but Kraigg Brathwaite and Keacy Carty took them to 70 for 1 before bad light forced early stumps for the second successive day.

It was Shamar Joseph, though, who first rocked the Bangladesh innings. At one stage, the visitors were 83 for 2. In the next 34 balls, they collapsed to 98 for 6 as Shamar picked up three of the four wickets to fall. He first ended a patient stand of 73 between Shadman Islam and Shahadat Hossain by castling the latter for 22. Soon after, he had Jaker Ali caught behind with a short ball. The batter was late on the pull; he top-edged it onto his shoulder and the ball lobbed behind the stumps for an easy catch to Joshua Da Silva.

In his next over, Shamar found the outside edge of Shadman to provide Da Silva his fourth catch of the innings. In between, Seales had Litton Das caught at first slip for 1.

After lunch, however, Shamar and Alzarri Joseph overused the short-ball ploy against Mehidy Hasan Miraz and Taijul Islam. The two batters hung around for 116 balls and added 41. Eventually, Taijul fended a short ball from Alzarri to third slip.

Seales then snared the last three wickets for five runs.

The Bangladesh seamers also started miserly, giving away only 16 runs in the ten overs before tea. After tea, Rana breached the 150kph mark multiple times and had Louis caught behind for 12.

Taijul also found help from the surface and neither Brathwaite nor Carty could get him away. Seven of his ten overs were maidens but he could not pick up a wicket.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ