IND vs AUS: Jasprit Bumrah In, Umesh Yadav Out For India In Nagpur T20I: Reports

In the first T20I at Mohali — Team India India did not include Jasprit Bumrah because the team’s management did not want to rush him back from a lengthy injury layoff.

The bowler is anticipated to be healthy for Friday’s second T20I match against Australia.

The Men in Blue lost the first T20I against Australia despite putting up a valiant fight, and all the Indian cricketing fraternity could speak about was Jasprit Bumrah’s absence. The speedster Umesh Yadav assumed the role of the third pacer for the squad because Bumrah was not yet fully healthy. However, he was not quite able to perform well.

Indeed, bowlers like Harshal Patel, Bhuvneshwar Kumar, and Umesh all gave up a lot of runs, each of whom finished with an economy rate of more than 10 per over. Jasprit Bumrah has allegedly been cleared to play and will be included in the starting XI, which is fantastic news ahead of the second T20I.

Jasprit Bumrah is ready for action: BCCI

Bumrah will replace Umesh in the lineup, with Harshal and Bhuvi serving as the other two pacers, as per a report in Cricbuzz.

“The team management did not want to rush him and that is the reason for his absence in the Mohali game,” a source in the Board of Control for Cricket in India (BCCI) told the portal about Bumrah’s absence in the first T20I.

“He has been bowling full blast at the nets and he is ready for action,” the source further said ahead of the second match of the series.

In Jasprit Bumrah’s absence, the Indian bowlers have struggled to contain the opposition batsmen, which has harmed India three times this month as the squad completes its preparations for the major tournament in Australia.

In his 19th overs against Pakistan (September 4), Sri Lanka (September 6), and Australia (1st T20I, September 20), the most seasoned pacer, Bhuvneshwar Kumar, was pounded for runs, and this is something that is currently causing concern.

Also Read: Shahid Afridi Discloses How He Tampered With Pitch After A ‘Cylinder Explosion’ In 2005