Tilak Varma’s dismissal in the India vs West Indies 3rd T20I was one of the most unusual run-outs of the series and came at a decisive stage of India’s innings. The India vice-captain was out for 28 off 16 balls after a misjudged call with Axar Patel in the 17th over at Holkar Stadium, Indore.
The dismissal mattered not only because of its rarity, but because it arrived during India’s acceleration phase. Varma had struck at a strike rate of 175.00 and had already hit four boundaries, making the communication error a significant interruption to India’s late-innings scoring pattern.
How the run-out happened
The ball came from Gudakesh Motie, who bowled a low full toss that Axar Patel worked toward the leg-side boundary region. West Indies fielder Kamil Pooran reacted sharply and dived to prevent the ball from reaching the rope.
Both Indian batters appeared to assume the ball had crossed the boundary, and the running stopped midway through the pitch. That brief pause was enough for the West Indies fielders to complete the dismissal, with the ball returned to Shai Hope before the stumps were broken at the non-striker’s end.
Key dismissal details
| Metric | Value |
|---|
| Batting position | Vice-captain |
| Runs scored | 28 |
| Balls faced | 16 |
| Strike rate | 175.00 |
| Boundaries | 4 |
| Over of dismissal | 17th |
Why the dismissal was costly
At that point, India were looking to maximise their final five overs and build toward a challenging total. Losing a set batter on 28 off 16 reduced their late-overs continuity and forced the lower order to take on more responsibility sooner than planned.
India still finished with 223 in 20 overs, but the wicket highlighted how single-ball events can affect end-innings output. Varma’s strike rate suggested he was contributing efficiently, and even a short stay at that pace can materially lift a team’s death-over run rate.
Historical context of the run-out
The dismissal also stood out because of the unusual chain of events that created it. Rare run-outs often involve a combination of poor awareness, fielding pressure and momentary overconfidence, and this was a textbook example of all three factors converging.
For India, it was another reminder that communication between partners is as important as shot selection, especially in overs 15 to 20 when margins are smaller and fielders are closer to boundary-saving angles.
India’s innings snapshot
| Team phase | Output |
|---|
| Final total | 223/10 |
| Overs faced | 20 |
| Target set | 224 |
| Varma contribution | 28 off 16 |
| West Indies fielding impact | Boundary save turned dismissal |
Axar Patel’s run-out trend
The incident also brought unwanted attention to Axar Patel’s run-out record. The left-hander entered a small group of players who have been dismissed multiple times in run-out fashion, a statistical reminder that even experienced finishers can be affected by pressure moments in the final overs.
In T20 cricket, such dismissals are often judged more by situational awareness than by batting skill alone. For India, the episode underlined the importance of reading the ball all the way to the rope before committing to a run.
What this means for India
India eventually secured a 14-run victory to take a 2-1 lead in the five-match series, so the run-out did not alter the result. However, from a performance-analysis standpoint, it remains a valuable case study in how small communication errors can erase momentum at a high run rate.
Varma’s innings showed efficiency, while the dismissal exposed the thin margin between a boundary opportunity and a lost wicket. In the closing overs, that margin often decides whether a team finishes with 215 or pushes beyond 225.
Analytical takeaway
Tilak Varma’s run-out was less about shot execution and more about split-second judgment. With a strike rate of 175 and a high-pressure finish underway, India lost a batter in rhythm, while West Indies gained a wicket through sharp fielding awareness.