Thirty-Six Balls in Wellington: Abhishek Sharma's 113 and the Price of a Powerplay That Made 199 Look Cheap

At Sky Stadium in Wellington, the scoreboard read 100 by the end of the fifth over. A hundred in five overs — the fastest team hundred in the history of T20 international cricket. At the end of the powerplay India were 118 without loss. The target was 199 and twenty overs were still available.

I took the match apart to see which part was still warm. The answer was not the part the highlights package was selling. India reached 199 in 13.2 overs — that is 80 balls. The powerplay accounted for 118 of those runs in 36 balls. The remaining 44 balls produced 81 runs and four wickets. The chase was won in six overs and merely survived for the next 44. Six wickets and forty balls to spare is the scoreline that turns the night into a 'record chase'. But a match that moves from 118/0 to 81/4 has already had its price paid in the first 36 balls.

This is an accounting of that price: what was bought, who sold it, and whose invoice arrives next match.

Wellington is a variable, not a myth

Wind in Wellington is not poetry; it is a measurable unit. Sky Stadium is a drop-in surface, which means the pitch carries whatever character the weather and its usage give it, and under evening floodlights the ball comes onto the bat quicker. When the wind blows from one direction, a batter at one end can trust his timing and a batter at the other cannot; a fast bowler at one end finds his swing, and at the other pushes the ball into the wind. All of this can be entered into a spreadsheet before the match. None of it can be entered by a captain standing on the outfield.

New Zealand lost the toss and chose to bat. That decision was itself a bet. They made 198/3 — not 150, not 200, but exactly in the zone where a side batting first on a drop-in pitch should land. Daryl Mitchell finished 89 not out. In twenty overs India took only three wickets. That number returns later in this piece, because 198/3 means India's bowling never broke a partnership that mattered.

The series in context: three-nil, two to play

With this win India moved to an unassailable 3-0 lead in a five-match series, with two games still to play. This is where I make myself stop and think, because 3-0 does not tell you whether the three wins came out of the same machine or out of three separate accidents. Here, the third-match powerplay tells you there was a machine, and it was running in the first two matches as well.

India's batting structure has changed. The opening pair is new, and the job of a new opening pair is not merely to score runs but to set the tone of the innings. Abhishek Sharma and Vaibhav Suryavanshi — a left-handed attacking opener who also bowls part-time left-arm spin, and a teenage left-hander at the start of his career — put on 133 in 44 balls. That stand was two-thirds of the target.

Let me state the limits of the data first

The brief in front of me has no ball-by-ball data. Mitchell's balls faced are not recorded. The square boundary dimensions at Wellington are not recorded. No source is attached to any of the numbers. So some figures below come straight from the brief, some I have derived arithmetically, and where arithmetic also runs out I will write 'verification pending' rather than invent an estimate. Forcing a calibrated model onto a one-off drop-in surface is my oldest habit and my biggest error.

The thirty-six-ball match

The powerplay permits only two fielders outside the circle. That is the clause on which the whole architecture of modern T20 batting rests. You have two fielders and 360 degrees to cover — the arithmetic says you can protect two zones, not three. Powerplay batting is therefore the game of pushing a fielder into the zone you can beat. India did exactly that, making 118 in 36 balls, a rate of 19.67.

Look at Abhishek Sharma's numbers separately. 113 runs off 38 balls. A strike rate of 297.4. Of those runs, 102 came in fours and sixes — 11 sixes and nine fours, meaning 90.3 per cent of his runs came in boundaries. Twenty boundaries in 38 balls is one every 1.9 deliveries. The hundred came off 35 balls, India's fastest, a shade slower than the 30-ball hundred he had made against Afghanistan the previous month. He already held India's fastest T20I hundred and has now competed with himself.

I will deliberately not go past the word 'century', because a century is a count and a count does not tell you what matters. The question is: which problem did the innings solve? India needed 199 at 9.95 an over. Abhishek's 38 balls removed 56.8 per cent of that requirement — 113 of 199. And of the 133-run stand, extras aside, roughly 88 were his. The stand ran at 18.14 an over across 44 balls, which is the rate that lets the rest of a chase be played in safety mode.

Vaibhav Suryavanshi's nineteen-ball job

45 off 19 balls. A strike rate of 236.8. On the highlights reel this innings looks small next to Abhishek's storm, and that is the great injustice of it. In a powerplay where one opener is going at 297, the other opener's job is not to score runs but to save strike — to keep his wicket expensive so the fast scorer can keep his rhythm. Nineteen balls is the period in which he took no risk beyond requirement and still scored at 236. It is quiet work, and in T20 it is worth as much as aggression.

The combined product was 133/0 in 44 balls. Against New Zealand's attack that was the moment the match's price was set. I have rarely seen a side lose the toss, make 198, and still feel cheap — but that is what happened. New Zealand scored at 9.9; India scored at 19.67 in the first six overs. The chasing side went at roughly double the rate of the side that batted first, on the same pitch, in the same light, in the same wind. That is not a talent gap. It is a planning gap.

The half of the match nobody watched

198/3. Twenty overs. Three wickets. India's bowling found success only three times all night. Daryl Mitchell finished 89 not out, meaning India could not dismiss him even in the closing overs. In a match that ends at 199/4 in 13.2 overs, the bowling failure is hidden. It is a dangerous assumption that bowling does not matter when you are chasing 200. Once your batting reaches 118/0, you win matches in which your bowling is poor. The question is whether 118/0 will be there next time.

If I reduce 198/3 to a single row in my spreadsheet, that row says: India did not break a single partnership of consequence across twenty overs. No wicket in the powerplay, none through the middle, none at the death. Bowling is priced by pressure, not by wickets — and 198 was not pressure by any definition.

Invisible variables: wind, dew and light

When the IPL was played across three stadiums with zero crowds inside a biosecure bubble in 2026, I noticed that empty stands made the field changes audible on broadcast — a data source nobody had logged. Three stadiums, zero crowd: the model heard what the noise used to hide. Wellington had a crowd, and the noise, which means those field changes will not be audible again. But the biggest invisible variable that night was not dew. Evenings in New Zealand are cool and dry; dew does not create the pressure it creates in Dubai or Mumbai. New Zealand's bowlers therefore had no wet-ball alibi available. A ball that is not slipping cannot be blamed for slipping.

The second variable was wind and the third was light. On a drop-in pitch under floodlights the new ball comes onto the bat quickly — a gift for India, whose opening pair is built on leaning forward and sending the ball straight. For a side with openers of that shape, Wellington's pace and bounce is less a threat than an opportunity. Edgbaston taught me what Russia could not: same grid, different ground, and this time the grid said bounce is the real currency here.

The records market and its price

The innings took Abhishek to four T20I centuries. Rohit Sharma and Glenn Maxwell sit ahead on five each. His overall T20 tally is being quoted at 11 hundreds, against Babar Azam's 13 and Chris Gayle's 22. I need to be clear here, because that list is a dirty market: 'T20 centuries' is a bag into which both franchise and international cricket are thrown, and the two do not share bowling quality, fielding standards or the shape of pressure. A league where you face four different attacks in four weeks prices a hundred differently from a bilateral series where the same opponent studies your weakness five times in ten days.

So I will not place Abhishek in Rohit's list, nor stand him beside Babar or Gayle. The accurate sentence for now is this: no one has made a faster T20I hundred for India, the 30-ball record against Afghanistan last month was also his, and only seven hundreds in world T20I history have come off fewer than 35 balls — one of them is his new one. That is a very narrow door, and very few have walked through it. The cost of narrowness is that the sample on either side of the door stays small.

The Chopra line and pundit pricing

The pre-match comment from Aakash Chopra reaches me in the Stage-1 brief without a verbatim quote, so I will not put words in his mouth. But the mechanism is worth naming, because a pundit is also a price-setter. When the commentary box questions an opening pair, the question usually arrives as 'is this pair international class', when the real question is 'what plan is this pair playing to, and what does that plan cost'. The spreadsheet had the answer three weeks before the pundits did — that is not a difference in intelligence but in information flow. Anyone holding three years of powerplay rate data could not have called that 118/0 an accident.

The contrarian turn: the shape of the win, the shape of the risk

This is where I have to distrust my own pleasure. Six wickets and 40 balls to spare is the brightest evidence of performance and also the most misleading. After 118/0, India made 81 runs in 44 balls and lost four wickets. A chasing side that is 81 away with four wickets down is not a side cruising; it is a side briefly uncomfortable. The difference was that the first 36 balls had bought so much room that the next 44 could afford mistakes.

The technical meaning is that India's chase template is front-loaded. It depends on a 19-an-over start. Had the powerplay on the same pitch against the same opponent been 62/1, the same batting order would have been trying to find 137 off 84 — and the entire valuation of the innings would change. When the model sees 118/0 it predicts a win; it does not tell you how rare 118/0 is.

Second, three chases completed early in three matches has one very direct cost: the batters from four to seven got no time in the middle. When a target is knocked off in the 14th over, where does middle-order sharpness come from? In a tournament knockout the day arrives when the powerplay is 40/2 and the middle order must find 150 off 120 balls. Nobody has been prepared for that day. That is the invoice not yet delivered.

Third, Abhishek's 297.4 strike rate is the right tail of a distribution, not the distribution. A batter who makes 90 per cent of his runs in boundaries has a left tail just as sharp — some innings will be 113 off 38, others 11 off 8. Indian cricket has an old habit of remembering the right tail as 'form' and filing the left tail away as 'a bad patch'. The real question is what the team's plan is while he is passing through the left tail.

Fourth, and I have kept this deliberately for last, there is Vaibhav Suryavanshi's age and workload. A teenage batter who has played a 19-ball role at international level is still physically developing, and the T20 fixture calendar is not designed for teenagers. Age verification, contracts for minors, caps on playing load — these read as administrative topics until a 19-year-old plays three series in a row. I do not have the data to say his load is already too high. I do have grounds to say nobody has started measuring it.

What this defeat says about New Zealand

New Zealand lost the toss, batted first, made 198 — and that was the right decision. What was wrong was the bowling plan. On a drop-in pitch, against a batter going at 297, the only route is hard length, no width, and a spinner in the powerplay to slow the ball down. A hundred and eighteen in six overs means that plan was not applied in any form. This is a failure of plan, not of talent — and a failure of plan is good news, because plans can be changed.

There is a concern underneath it, though: New Zealand's bowling depth. To make 198 and still lose with 40 balls remaining, at home, to go 3-0 down, says the gap in this series is not in batting but in bowling options. And when a series is decided with two matches left, the remaining games become a laboratory — new bowlers tried, senior ones rested. That is fine, provided you keep the results of those two matches separate from the result of the series.

What to watch next

Three things hold my attention in the next match. First, New Zealand's powerplay plan — do they change the line, do they bring spin into the first six overs, do they bowl closer to Abhishek's body. Second, India's middle order — is it deliberately put under stress, or do the last two matches also end in the 14th over and we never learn how the number five bats. Third, and most important, the bowling rate — if India repeat 198/3, then despite a 3-0 lead I will believe we are watching a side using its batting to hide its bowling.

And finally the question I attach to every piece: who put this five-match series in the calendar, in which window, and who gets the bill? The week this series is being played sits in the shadow of both franchise auctions and league windows. Player load, injury risk and the protection of teenage batters all flow from the same calendar that broadcasters and boards write together. Thirty-six balls in Wellington decided a match. The real price of that match will show up in the fixture list of the next six months.

One new row has been added to my spreadsheet today: 19.67. Whether that row repeats next match is the actual story of this series. Everything else is scoreboard decoration.