New Delhi: England wicketkeeper batter Jos Buttler has become the highest run scorer in T20 cricket history, surpassing former West Indies captain Kieron Pollard during a match in The Hundred on Wednesday.
Buttler achieved the landmark while representing Manchester Super Giants against Welsh Fire at Old Trafford. Needing 22 runs to overtake Pollard’s record of 14,803 T20 runs, the England star crossed the milestone during his unbeaten knock of 51 from just 20 balls, guiding his side to a comfortable chase of 156 with 69 balls to spare.
The record breaking innings came in Buttler’s 522nd T20 appearance, taking his career tally to 14,833 runs in 492 innings. Pollard, who now moves to second place, has scored 14,803 runs in 746 matches, while legendary West Indies batter Chris Gayle occupies third position with 14,562 runs.
The top five highest run scorers in T20 cricket are now Jos Buttler, Kieron Pollard, Chris Gayle, Alex Hales and David Warner, while India’s Virat Kohli is sixth on the all time list with 14,218 runs.
A key figure in England’s victorious 2022 ICC Men’s T20 World Cup campaign, Buttler has built an outstanding record across franchise and international cricket. He has scored 4,212 runs in 160 T20 Internationals and has also enjoyed remarkable success in the Indian Premier League, where he has accumulated 4,646 runs for Mumbai Indians, Rajasthan Royals and Gujarat Titans, including seven centuries.
The latest half century also underlined Buttler’s excellent form in the ongoing edition of The Hundred. He has now scored 277 runs in six matches, making him the tournament’s second highest run scorer behind Australia’s Mitchell Marsh.
The knock marked Buttler’s fourth fifty of the season, equalling the record for the most 50 plus scores in a single edition of the men’s Hundred. Before him, only Dawid Malan and James Vince had achieved the feat.
With another milestone added to his illustrious career, Buttler has further strengthened his reputation as one of the greatest T20 batters in cricket history.
Sorry, there was a YouTube error.
