Border-Gavaskar Trophy
137

India vs Australia: Sunil Gavaskar Urges Jasprit Bumrah to Prioritize Playing All Five Tests for India

Sunil Gavaskar emphasized Jasprit Bumrah's importance in the ongoing Border-Gavaskar Trophy, urging him to play all five Tests. Bumrah, the leading wicket-taker with 12 scalps at 11.25 in two matches, has taken 53 wickets this year at 15.28. Gavaskar called him India's "battering ram", crucial for taking 20 Australian wickets, especially with Mohammed Shami absent.

Sunil Gavaskar emphasized Jasprit Bumrah's importance in the ongoing Border-Gavaskar Trophy.
Image: Sunil Gavaskar emphasized Jasprit Bumrah's importance in the ongoing Border-Gavaskar Trophy / © English Jagran

After the defeat in the 2nd Test against Australia at Adelaide, Sunil Gavaskar emphasized the importance of Jasprit Bumrah playing all five matches in the ongoing Border-Gavaskar Trophy (2024-25). Bumrah, India’s leading wicket-taker in the series, has been in sensational form, taking 12 wickets in two matches at an impressive average of 11.25.

This year, he has bagged 53 wickets in 11 matches at an average of 15.28, underlining his critical role in India’s bowling attack. Bumrah’s stellar performance in the first Test at Perth, where he took key wickets and won the Player of the Match award, led India to a commanding 295-run victory. Although India suffered a 10-wicket loss in Adelaide, Bumrah claimed four wickets, even battling a scare of cramps during the match. In the statement given by Gavaskar, he said:

He is your battering ram. If you’re not going to play him in all 5 matches, you reduce your chance of taking 20 Australian wickets. How he is used is up to the captain. He has to be used in such a way that he is effective each time he comes to bowl.

Gavaskar called Bumrah India’s “battering ram”, stating that resting him could reduce India’s chances of taking 20 Australian wickets. The third Test at Gabba, starting December 14, will test India’s reliance on their ace pacer.

Comments

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