Babar Azam set to break ODI record, surpassing Virat Kohli and Hashim Amla

A Babar Azam century in the upcoming ODIs would be record-breaking


News Desk December 21, 2024
Babar Azam. PHOTO: AFP

Listen to article

Babar Azam is approaching a historic milestone in ODI cricket, with a remarkable achievement that will see him surpass modern greats Virat Kohli and Hashim Amla.

The internationally top-ranked ODI batsman is poised to become the fastest player to reach 6,000 runs in the format.

South Africa's Hashim Amla currently holds the record for 6,000 runs in 123 innings, while Babar Azam, with 5,905 runs in 119 innings, is within striking distance of this remarkable feat. Meanwhile, India's Virat Kohli reached 6,000 runs in 136 innings.

Babar’s recent performance in the second ODI against South Africa on December 19 marked his return to form, as he scored a vital 73 runs off 95 balls, leading Pakistan to an 81-run victory.

In the series-clinching second ODI against South Africa, Babar Azam scored his first ODI fifty since last year's World Cup, sharing a century partnership with Mohammad Rizwan.

With the half-ton Babar surpassed MS Dhoni’s record for most half-centuries against the "SENA countries" (South Africa, England, New Zealand, and Australia).

Dhoni had held the record with 38, but Babar now leads with 39.

With 19 ODI centuries to his name, Babar Azam is also closing in on Saeed Anwar’s record for the most centuries by a Pakistani cricketer.

Left-handed batting great Anwar scored 20 ODI centuries for Pakistan during his career.

However, Babar has been under some scrutiny due to a lack of centuries since his last ton in the 2023 Asia Cup against Nepal.

As Pakistan prepares for the third and final ODI against South Africa on December 22, all eyes will be on Babar Azam, who is not just aiming for a team win but also eyeing more records to further cement his legacy in ODI cricket.

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