The irony is almost too sharp. The very venue where Abhishek Sharma made his greatest innings in international cricket — 135 off 54 balls against England at Wankhede in January 2025, the highest score by an Indian batter in T20 internationals — became the venue where his 2026 T20 World Cup nightmare reached its most painful chapter. In a semi-final. Against the same opponents. On the same ground. And he lasted seven balls.

Abhishek Sharma’s nine off seven in India’s second semi-final against England on Thursday extended one of the most perplexing individual runs of the entire T20 World Cup 2026 campaign. Six scores of 15 or below in seven matches at the biggest stage of the game. And the manner of this latest dismissal — once again against off-spin, once again failing to read the length, once again caught in the deep — has reignited the debate that the Indian team management has been desperately trying to suppress all tournament.

The Dismissal: Will Jacks Exploits the Same Old Weakness

England captain Harry Brook made the most tactically obvious decision in this semi-final: he handed the ball to Will Jacks in the second over. Not the third or the fourth. The second over — before Abhishek had even settled, before he had navigated the pace of Jofra Archer or Mark Wood, before he had had time to find the rhythm that turned him into a wrecking ball in the group stage against Pakistan in 2025.

The plan was simple because the data is simple. Abhishek has now been dismissed three times by off-spinners in this T20 World Cup across five innings against such bowling, scoring only 29 runs at an average of 9.66 and a strike rate of 107.40. For a batter who averages 33.59 in T20 internationals at a strike rate of 189.41 across his career, those numbers represent a specific, diagnosed, repeatable weakness.

Jacks’ dismissal ball on Thursday was a slower delivery that drifted back in off the pitch, angled into Abhishek’s body. He jogged down the track, backed away to create room, and attempted a slog-sweep aerial flick — the same bottom-handed shot that has undone him against Roston Chase, against Pakistan’s off-spinners, and against South Africa’s part-time spinners throughout this tournament. The ball caught the bottom edge and lobbed to Phil Salt, who had been stationed specifically at deep mid-wicket for exactly this delivery. Abhishek was caught for nine. Salt took the catch. England celebrated as if they’d broken the match open — because, in a sense, they had.

The Tournament Scorecard That Tells the Full Story

Entering Thursday’s semi-final, Abhishek’s T20 World Cup 2026 numbers looked like this:

Total: 89 runs. Average: 13.33. Strike rate: 131.15 across the tournament — a number that, from a batter whose T20I career strike rate is 189.41, represents a staggering underperformance of nearly 58 percentage points.

The one exception — his 55 against Zimbabwe in Chennai, the innings that temporarily silenced the critics and gave the team management breathing space — now reads more like a statistical outlier than a form revival. Zimbabwe’s attack on a flat Chepauk surface, missing Blessing Muzarabani’s extra bounce on that particular evening, provided the conditions Abhishek needed. Every other game in this tournament, something — illness early on, the off-spin plan later — has disrupted his ability to impose himself.

Why He Kept Playing — And Why the Debate Will Continue

Gautam Gambhir has been unwavering in his support of Abhishek throughout this tournament, and that backing deserves context. The head coach was the architect of Abhishek’s emergence at KKR — he saw the 25-year-old dismantle opposition attacks in the IPL with a consistency that made him one of the most productive T20 openers in the world by late 2024. He knows what the batter is capable of, and he decided — reasonably — that three ducks in the group stage against weaker opposition were not sufficient justification to drop the world’s top-ranked T20I batter.

There is an argument for that loyalty, and there is an argument against it. The argument for: Sanju Samson’s return to form was directly enabled by having Abhishek at the other end — even a Abhishek scoring nine off seven creates enough of a distraction, enough of a left-right awkwardness, to give Samson early momentum. The 97 against West Indies and the 89 against England on Thursday did not happen in a vacuum. They happened with Abhishek providing early disruption that forced bowling captains to bring their primary spinner (Hosein, Jacks) inside the powerplay rather than saving them for the middle overs.

The argument against: in a T20 World Cup semi-final, asking your opponent to gift you a wicket in the second over is too large a concession. England’s plan for Abhishek was so well-executed and so apparently well-researched that it raises the uncomfortable question of whether continuing to pick him — without any visible adjustment in his approach to off-spin — amounts to giving opponents a head start.

Social media was predictably brutal on Thursday. “Blind slogger” was among the more printable labels. “Why is he still in the team” trended in India within minutes of the wicket falling. The anger is understandable even if the language isn’t.

What Happens Next

India’s total of 253 for seven means the dismissal didn’t cost them the match in the first innings — Samson, Dube, Kishan and Pandya ensured that. Whether Abhishek features in an India T20 World Cup final — if India beat England’s chase tonight — will depend entirely on whether the team management is willing to make a change in the most important match of their year, or whether Gambhir’s faith in his disciple runs all the way to the title shot.

If India do make the final, the selection question will be loud and uncomfortable. And Abhishek Sharma — who once blew up 135 at this very ground against these very opponents — will have to find the answer in the nets, not in the press conferences.