India Tour of South Africa
161

India vs South Africa: Arshdeep Singh Poised to Break Yuzvendra Chahal’s T20I Record for India

bowling records. He’s just four wickets away from surpassing Yuzvendra Chahal’s tally of 96 and aims to top the India-South Africa T20I wicket charts, currently led by Keshav Maharaj. A five-wicket haul in Johannesburg could also break Bhuvneshwar Kumar’s 2022 record of 37 T20I wickets.

Arshdeep Singh all set to break Indias T20I record.
Image: Arshdeep Singh all set to break India's T20I record / © English Jagran

India’s star bowler and a key member of the 2024 T20 World Cup-winning team, Arshdeep Singh, is on the brink of creating history. As India faces South Africa in the fourth and final T20I at Johannesburg’s New Wanderers Stadium, Arshdeep has a golden opportunity to become the leading wicket-taker for India in T20Is. Currently sitting at 92 wickets in 59 matches, Arshdeep is just four shy of overtaking Yuzvendra Chahal’s record of 96 wickets in 80 games.

Not only is the 25-year-old chasing an all-time record, but he’s also in line to dominate the India-South Africa T20I wicket charts. With 15 wickets in nine matches, he’s close to surpassing South African spinner Keshav Maharaj’s tally. Moreover, Arshdeep has an added incentive—five wickets in this match would break Bhuvneshwar Kumar’s 2022 record of 37 T20I wickets in a calendar year.

PlayerMatchesInningsBallsOversRunsWicketsAverageEconomyStrike Rate45
Yuzvendra Chahal80791764294.024099625.098.1918.3721
Arshdeep Singh59591222203.417009218.478.3413.282
Bhuvneshwar Kumar87861791298.320799023.106.9619.9032
Jasprit Bumrah70691509251.315798917.746.2716.95
Hardik Pandya108961721286.523628826.848.2319.553
Most Wickets for India in T20I

Debuting in 2022, Arshdeep has made a significant impact on India’s bowling lineup. His ability to deliver under pressure makes him indispensable. Alongside him, veterans like Bhuvneshwar Kumar (90 wickets), Jasprit Bumrah (89), and Hardik Pandya (88) are part of India’s elite bowling group.

Comments

Thank you! We’re reviewing your comment.
We were unable to post your comment. Please, try again.