Jaiswal Run Out on 175: Shubman Gill's Hesitation Sparks Blame Game; Bangar Points Finger at Captain

Heartbreak in Delhi. That’s the only way to describe it. On Day 2 of the second Test against the West Indies, Yashasvi Jaiswal was on fire, cruising towards a double century, only to be stopped short at 175 by a disastrous run-out involving his captain, Shubman Gill. The dismissal ignited a fierce debate online and among experts. So, what really happened?

Key Takeaways

Yashasvi Jaiswal was run out for a brilliant 175, just 25 runs shy of a double hundred.
The dismissal was caused by a miscommunication with captain Shubman Gill over a quick single.
Experts are divided: Aakash Chopra felt Jaiswal made a risky call, but Sanjay Bangar put the blame squarely on Gill’s hesitation.
Jaiswal showed immense maturity, calling it “part of the game” and defending Gill from online criticism.

How It All Unfolded

Look, it was a moment of pure chaos. Jaiswal, batting magnificently on 175, pushed a delivery towards mid-off and immediately called for a quick single. He was halfway down the pitch before he realized his partner, Gill, wasn’t going anywhere. Gill, the striker, hesitated, gave a “half-and-half” call, and then waved him back. It was too late. Jaiswal was stranded, and his incredible innings came to a crushing end.

Despite the dismissal, his 175 was his fifth score of 150 or more before turning 24, putting him in the same league as Graeme Smith. A small consolation for what could have been his third Test double century.

The Blame Game: Experts Divided

As soon as the wicket fell, the analysis began. Who was really at fault? The cricket world was split right down the middle.

Get the Latest Updates

Be part of our sports community for daily news, expert analysis, and insider info.

Join on Telegram Join on WhatsApp

Expert Analysis

Initially, voices like Aakash Chopra and Anil Kumble suggested that Jaiswal, as the caller for a risky single, should take the responsibility. But then former batting coach Sanjay Bangar dropped a bombshell. He controversially placed the blame primarily on Shubman Gill. Bangar argued that Gill’s hesitation and unclear signal left Jaiswal completely exposed, making the non-striker the unfortunate scapegoat.

Social Media Storm

You can bet the fans had their say. Social media erupted, with hashtags trending and loyalties divided. Many criticized Gill for his indecisiveness at a crucial moment. But here’s the thing that stands out the most.

Jaiswal’s Classy Response

While the internet was busy pointing fingers, Yashasvi Jaiswal himself stepped up and showed incredible maturity. He completely downplayed the incident. In a post-match statement, he defended his captain, insisting that these things happen and are simply “part of the game.”

He urged fans to focus on the team’s dominant performance rather than individual milestones. India declared at a massive 518/5, putting them firmly in control of the Test match. Jaiswal’s response was a masterclass in sportsmanship, shutting down the controversy with pure class. But the question remains for the fans: was it just a mix-up, or a captain’s error?

Jaiswal Run Out on 175: Shubman Gill’s Hesitation Sparks Blame Game; Bangar Points Finger at Captain

Key Takeaways

How It All Unfolded