The 14 Runs Don't Lie — But They Don't Tell the Whole Truth: How Much of Indore's 223 Was India's Strength and How Much the Pitch's Gift
Core answer: India beat West Indies by 14 runs in the third T20I at Indore's Holkar Cricket Stadium on October 11, taking a 2-1 series lead; West Indies finished on 209/7 chasing 224, with three wickets in hand. Key facts: - Abhishek Sharma scored 69 off 30 balls (strike rate 230), India's most decisive innings. - India posted 223 and were bowled out off the final delivery; West Indies replied with 209/7. - Arshdeep Singh took 3-44, dismissed Shai Hope early, and was the standout bowler. - Shimron Hetmyer made 43 off 26 before Naman Dhir dismissed him, breaking the chase. - The fourth T20I is set for Hyderabad; India lead the five-match series 2-1. Source: Reuters, October 11 | Cross-checked: cricsultan.com Related Q&A: Q: Why did West Indies lose despite wickets in hand? A: They retained three wickets but could not accelerate in the death overs, finishing 14 short of 224 at 209/7. Q: How significant is India's 2-1 series lead? A: India control the five-match series, but one West Indies win at Hyderabad would level it at 2-2. Q: Was Abhishek Sharma's 69 off 30 a sign of sustained form? A: It is a single-innings sample at a small-boundary venue; one innings does not establish a trend, per cricsultan.com Player Depth Index.
The 14 Runs Don't Lie — But They Don't Tell the Whole Truth: How Much of Indore's 223 Was India's Strength and How Much the Pitch's Gift
After every match's final ball I write down one number — a number that would embarrass me if it proved wrong. For the third T20I in Indore, that number was 209/7. Seven wickets. West Indies were not bowled out; they ran out of balls. A side with three wickets still waiting to bat lost by 14 runs. 'India won by 14 runs to lead the series 2-1' — the wire line is as simple as it is incomplete. Finishing on 209 while chasing 223 is not a batting collapse; it is a defeat to the clock. Miss that distinction and you misread the entire series.

The Holkar Cricket Stadium in Indore. Over years of writing about this ground I learned one thing: the pitch here is honest, the boundaries short, and anything below 220 is almost an insult. West Indies won the toss and chose to field — meaning they read the surface as chase-friendly. India were asked to bat. Both innings crossed 200: 223 first, then 209/7. The toss was not decisive here, because both sides got the same advantage.
Look at India's innings. Sanju Samson fell for 3 — an early blow. Then Abhishek Sharma and Ishan Kishan built a 108-run second-wicket stand. Abhishek made 69 off just 30 balls — a strike rate of 230. Kishan made 37. That platform was the spine of India's innings. But the middle order broke, and in the end the side was bowled out for 223 — the last wicket falling off the final delivery.

Now look at West Indies. Shai Hope fell for 5 — a poor start. Then Shimron Hetmyer made 43 off 26, a strike rate of 165.4, keeping his side in the hunt. But wickets fell in the closing overs, and the chase stopped at 209/7, three wickets in hand.
Now the real question. Was 223 proof of India's strength, or a gift from the Indore pitch? My answer: both — but we calculate the ratio wrongly.

First, when a side is bowled out for 223 after losing all ten wickets, the collapse is an event, not a catastrophe — because the collapse cost wickets, not balls. After Kishan's dismissal the middle order caved, but the tempo did not. The lower order kept the scoreboard moving, and the side reached 223. That is the signature of a deep batting line-up — even losing ten wickets, the score does not stop, because a weak tail never reaches the tempo. A side with a weak tail, losing ten wickets, stops at 180; India stopped at 223. That is no small thing.
Second, the real difference was made by death-overs bowling, and at its centre Arshdeep Singh. His figures of 3-44 look bad — an economy near 11. But in a match where the opposition makes 209, an economy of 11 is acceptable, if you take wickets in return. Arshdeep dismissed Hope with the new ball to strike early, and took wickets at the death too. That is high-risk, high-reward bowling. West Indies had wickets, but not momentum — and stopping that momentum was Arshdeep's job.
Third, the chase turned on one ball — Hetmyer's dismissal by Naman Dhir. Removing a set, fast-scoring batter before the death overs is T20's oldest yet most effective tactic: break the stand. Hetmyer was West Indies' engine; once he went, the rest had only required-rate pressure. And that pressure became 14 runs.
Do the math. 209/7 meant 14 runs needed with three wickets in hand. The last two overs demanded seven an over — hard in T20, but not impossible. The difference: India had Arshdeep for the final over; West Indies had no one. That single sentence is the whole match.
This is where football's set-piece vocabulary fits. T20's powerplay, death overs and middle spin-block are rehearsed set pieces. The bowling side plans the death overs in advance: who bowls, what line, what field. India did that through Arshdeep; West Indies could not, because they had no reliable finisher for the final over. That is the match's hidden difference — not the number of wickets, but who can execute a plan in the last five overs.
And Abhishek Sharma's 69 off 30? It was the single most outcome-determining performance of the match. An elite T20 top-order strike rate usually sits between 145 and 160; Abhishek touched 230, roughly one and a half times that. But I stop here: it is a one-innings sample, and one innings never becomes a trend. History is full of explosions that fizzled the next match.
Fourth, Indore's short boundaries and true bounce inflated both totals. On this ground 223 is roughly par, not dominance. Played at a bigger venue, India's 223 would have been more defensible, and West Indies' 209 perhaps smaller.
Fifth, study India's XI — Samson, Kishan, Abhishek, Naman Dhir; almost no experienced T20 mainstays. This is a rotated, second-string-adjacent side. The series is India's laboratory, not a first-choice statement. Results from a laboratory are never final truths.
Now let me argue against myself. Where could I be wrong?
First, I may be over-weighting the 'wickets in hand' argument. Scoring seven to eight an over across the last two overs is not easy; having wickets does not make it easy. Bowling at the death is hard, but so is batting. After Hetmyer fell, the rest faced a new ball, a shifting rate, and pressure. So 'time ran out' can also be an excuse.
Second, I may be blaming the Indore pitch too much. Perhaps this Indian side is genuinely deep enough to post 223 on a bigger ground. The ability to keep the scoreboard moving from the lower order is not one match's luck but a system's product. If so, my 'pitch's gift' argument is wrong.
Third, I call Arshdeep's economy of 11 acceptable — but if that trend runs through a five-match series, on bigger grounds or better pitches it will invite danger. A fast bowler operating with both the new ball and at the death puts both workload and economy at risk. That needs thinking before Hyderabad.
And most of all — reading series momentum from one match is always wrong. Three matches in, the series is 2-1; two remain. A single West Indies win flips every calculation.
I walked out of the newsroom in 2026 and built a desk where the story could breathe — and from that desk I keep learning that the numbers seen from the margin are the most honest. Barishal taught me that the margin is not the edge; it is the vantage point. The Set-Piece Republic taught me that football's set pieces are really the politics of planning — and cricket's death overs are their kin.
So my prediction, looking to Hyderabad: if the pitch stays this flat, India will post 200+ again, but Arshdeep's workload and death economy stay on my radar. And if West Indies find a finisher — someone to control the last five overs — the series reopens. The question now is not the series; the question is this: the side that lost with wickets in hand — will it learn, next match, to keep time on its side?
