Bangladesh beat Afghanistan to win ODI series 2-1

Opener Tamim Iqbal's century helped hosts defeat visitors by 141 runs


Afp October 01, 2016
Bangladesh cricketer Tamim Iqbal celebrates his half century during the third One-Day International(ODI) between Bangladesh and Afghanistan at the Sher-e-Bangla National Cricket Stadium in Dhaka on October 1, 2016. PHOTO: AFP

DHAKA: Opener Tamim Iqbal scored a record century as Bangladesh beat Afghanistan by 141 runs in the third ODI to win the three-match series 2-1 in Dhaka on Saturday.

Chasing a stiff target of 280 to win the series, visitors were dismissed for 138 runs in 33.5 overs thanks to some sublime bowling performance from left-arm spinner Mosharraf Hossain, who picked three wickets in his comeback match in the 50-over format.

Earlier, Tamim made the most of an early life to hit 118 in as many balls to give Bangladesh a platform for a big total but the home side lost the momentum once he fell to Mohammad Nabi.

Afghanistan beat Bangladesh by two wickets in ODI


Substitute fielder Naveen-ul-Haq took the catch at long-off to end the onslaught of Tamim, who hit 11 fours and two sixes in his seventh ODI hundred, the most by a Bangladesh cricketer.

Dropped by Afghanistan captain Asghar Stanikzai when he was only on one run, Tamim never looked back and completed his century with a single off Dawlat Zadran before hitting Rahmat Shah two sixes off successive balls.

The stylish left-hander got good support from one down Sabbir Rahman, who scored his career best 65 off 79 balls and put 140 runs for the third wicket with the experienced opener after the early dismissal of Soumya Sarkar (11).

Bangladesh recall spinner Mosharraf for Afghan ODI


Tamim was awarded man-of-the-match for his match-winning innings, and he was also named the man-of-the-series after finishing as the the highest run getter with 218 runs at an average of 72.66.

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