Shaheens on top against Bangladesh A

They set a 428-run target thanks to Omair’s unbeaten ton


News Desk July 22, 2024
Pakistan cricket team pacer Shaheen Afridi. PHOTO: FILE

print-news

Pakistan Shaheens had a commanding day in the field with bat and ball against Bangladesh A as they set them a target of 428 on day three in the first four-day match at the DXC Arena in Darwin.

Bangladesh A require 408 runs as they closed the day with 20-0 in seven overs.

Earlier, Bangladesh A resumed their innings from the overnight score of 203-4 before succumbing to 266 all out in 76.2 overs as Shaheens took no time in wrapping up their innings. Shahadat Hossain was stranded for 36 not out while none of the batters apart from Rejaur Rehman Raja (32, 18b, 4x4s) offered any resistance as their team added only 63 runs for six wickets leaving a deficit of 201 runs.

Test fast bowler, Khurram Shahzad was the chief destroyer as he dismissed five batters in the first session claiming figures of 6-72 in 21.2 overs, his sixth five-wicket haul in first-class cricket. Mohammad Ali finished with 2-64 in 22 overs, while also holding up one end on the morning of day three. Shahnawaz Dahani had one scalp to his name.

With a lead of 201 runs, Pakistan Shaheens began their second innings copping two early blows. Haseebullah departed for a six-ball duck while Sahibzada Farhan was dismissed for eight, leaving Shaheens 20-2 in 5.1 overs.

Omair Bin Yousuf (100 not out, 123b, 6x4s, 2x6s) and Mubasir Khan (95, 134b, 8x4s, 1x6), promoted up the order, put on a mammoth 170-run third-wicket partnership to help Pakistan extend the lead over 400-mark.

Mubasir missed out on his fourth first-class century while Omair, playing his 50th first-class game, registered his 11th ton in the format. The declaration call came right after he reached his ton, with Shaheens scorecard reading 226-3 in 47.2 overs, setting Bangladesh 428 runs to win.

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