T20 World Cup 2024
Rohit Sharma Shouted At Rishabh Pant For Misjudging A Catch
By CricShots - Jun 24, 2024 10:37 pm
Views 83

In the ongoing T20 World Cup 2024 clash between India and Australia at the Daren Sammy National Cricket Stadium in St Lucia, Rohit Sharma expressed his displeasure with wicketkeeper Rishabh Pant’s performance during Australia’s chase of India’s imposing total of 205 runs.

Rohit Sharma
Rohit Sharma shouted at Rishabh Pant

India’s start with the ball was promising, with Arshdeep Singh striking early to dismiss David Warner for just 6 runs in the opening over, much to the delight of Indian fans. In the following over, Jasprit Bumrah created another opportunity, but it was squandered due to a missed chance by Rishabh Pant behind the stumps.

WATCH – Mitchell Starc’s Revenge: Dismisses Rohit Sharma Just Shy Of Century

On the fourth delivery of Bumrah’s over, a well-directed short ball surprised Mitchell Marsh, who attempted a pull shot but ended up gloving it towards Pant. The ball appeared to be a straightforward chance for Pant to take a catch and secure India’s second wicket early in the innings. However, Pant seemed to lose his footing slightly, which prevented him from making a clean attempt at the catch, resulting in the ball landing safely.

Rohit Sharma, observing Pant’s missed opportunity, was visibly frustrated. He had anticipated a crucial breakthrough for India, only to see the chance go begging due to Pant’s slip-up. The captain’s disappointment was evident as he expressed his frustration vocally, directing his displeasure towards Pant for the missed opportunity.

WATCH – Rohit Sharma Smashes Mitchell Starc For 29 Runs Follows It With 19-ball Fifty

The incident highlighted the intensity and high stakes of the match, where every opportunity counts in a tight contest between two competitive sides. As India aimed to defend their formidable total, Rohit Sharma’s reaction underscored the importance of maintaining sharpness and focus in crucial moments of the game.

Here are the videos of the incident: