199 in 13.2 overs at Wellington: Abhishek Sharma's record and the column the scorebook leaves blank

Two overs, two balls, fifty runs.

I was not in Wellington. I was at my desk in Kolkata, the same hand-ruled scorebook open in front of me that I had built in the Eden Gardens media overflow during the 2026-18 Bengal season. Filling in the first six overs, I did not believe my own handwriting — 118 runs, no wickets. I rubbed it out twice with the pencil and wrote it again, as though the mistake were mine and not the score's.

On the second ball of the seventh over the opening stand reached 133, off 44 balls. On the second ball of the thirteenth over the target was gone. 199 runs, 13.2 overs, four wickets in hand. A five-match series settled with two matches to spare, a 3-0 lead.

The scorebook says one thing; the ball-by-ball log was saying another. That gap is the real story of this match, and it is not in the century everyone is talking about.

The Wellington context the headline drops

India won the toss and chose to field. The wind at Sky Stadium, the drop-in pitch, the short square boundaries — this is a ground where 200 does not feel safe for the side batting first. New Zealand made 198 for 3, at 9.9 an over. Daryl Mitchell finished 89 not out; his balls faced are not in the brief, so I will not comment on his strike rate. What is recorded is this: in twenty overs India took three wickets.

That is the information no record list will show you, because records are always built in the winner's name. But the shape of the match was decided here: New Zealand had 198 and no bowler the Indian openers were afraid of.

The arithmetic of 38 balls

Abhishek Sharma: 113 runs, 38 balls. Strike rate 297.4. Eleven sixes, nine fours. That means 102 of his 113 came in boundaries alone — 90.3 per cent. Twenty boundaries in 38 balls, one every 1.9 deliveries.

The number should be read this way: this was not fast batting, it was over-termination. When you are hitting a boundary every second ball, you are not playing for ones and twos, you are erasing the bowler's plan. By the third ball of an over the bowler stops thinking about what to bowl next, because the over has become boundary-based. In my ledger, against Bengal's seamers, I had seen exactly this pattern — when the strike-rotation ratio breaks, the field settings break with it.

The hundred came off 35 balls. Last month, against Afghanistan, India's fastest T20I hundred was 30 balls. This one arrived five balls later — and that is the most interesting part. It was late because Abhishek did not stop; he went on and lasted 38 balls. A batter who does that after reaching three figures is not building a record, he is raising the team's run rate. The difference looks small, but in T20 it is the difference between a win and a narrow win.

The powerplay is now design, not accident

India made 118 in six overs, at 19.67. The highest powerplay score by any full member. Fifty in 2.2 overs (joint record), 100 in five overs (fastest).

In one match those numbers could be a streak. Two months, two different opponents, two different kinds of bowling — here it has become a method. The 30-ball hundred against Afghanistan and 118 in six overs at Wellington are not two events; they are two proofs of one system.

The biggest consequence of that system is that the middle overs become administration. The real contest of the innings is over inside the first six, and the remaining sixteen merely complete the paperwork. From a captaincy view this is efficient. From a coaching view it is risky, and the reason comes later.

Suryavanshi: the real job at a strike rate of 236.8

Vaibhav Suryavanshi made 45 off 19 — a strike rate of 236.8. Beside Abhishek's number it looks pale, but the partnership maths tells you what his job was. 133 runs in 44 balls, a rate of 18.14. If we assume the stand broke when Suryavanshi was dismissed, Abhishek's share during it would have been roughly 88 off 25 — and that must stay an inference, because the fall-of-wicket data is not in the brief.

A fast batter needs a partner who can play alongside him, and this partnership held — the two were moving at 236 and 297 together. This was not a two-part assault; it was a single strategy.

This is where I have to resist an old habit of Indian coverage: turning a teenager into an idol. Suryavanshi's age, his small-town background, his IPL contract — an industry has already grown around all of it, well outside the cricket field. I do not have the fitness or workload report for this match, so I will only point at it: the thrill of nineteen balls and the strain of nineteen overs on a teenager's body are calculated in different books.

The century ledger, and its limit

Abhishek now has four T20I centuries. Rohit Sharma and Glenn Maxwell have five each. In all T20s he is on 11, where Babar Azam has 13 and Chris Gayle 22. Seven centuries under 35 balls are recorded in T20Is, and Abhishek is on that list with one of them.

There is a lazy way to add these numbers up: treat T20 centuries as one ladder. They are not. The quality of franchise bowling, the steadiness of a two-team international attack and the weight of the tournament are all different. Four T20I hundreds is a solid signal precisely because bowlers arrive with a plan and come back the next match looking for revenge. But four hundreds is not the full picture until they are repeated against different bowling rates and different conditions — a moving new ball, a cold morning, an eight-one field.

That examination is not scheduled in this series. It is scheduled in the next one, and that one will not be T20.

The empty column: the bowling

Here is the part I wrote first in my notebook after a chase of 199, and it was not about the century.

New Zealand made 198 for 3. India took three wickets in twenty overs. Mitchell finished 89 not out. In a match India won by six wickets with forty balls unused, their bowling conceded nearly ten an over and took three wickets.

That figure is not a crisis — it is a door that is currently shut and will open later. It is not that India's bowling was poor; it is that India's bowling was never examined in this series. When your batters finish the target in thirteen overs, not one bowler's mistake shows on the scoreboard. The death-overs plan, the yorker's consistency, the decision to bowl the slower ball under pressure — none of it gets accounted for.

Aakash Chopra's pre-match observation is recorded in the Stage-1 brief without a quotation. I will not print it without a source. But the substance usually drawn from that observation matches my worry: a batting line so fast that it covers the bowling's gaps.

66 for 4 in 36 balls: the middle order's hunger

Now the number that surprises me most. At 44 balls the score was 133 for 0. The innings ended at 13.2 overs, 199 for 4. Do the arithmetic: in the last 36 balls India made 66 and lost four wickets, at 11 an over.

That is not in the headlines, because the match was already won and the margin was comfortable. But it points to the illness that should be in the coaching staff's notebook: even at 3-0 up, India's batters from number three to six have faced only a handful of balls between them in this series.

When your openers take both the wickets and the runs inside the powerplay every match, the middle order's job becomes batting in an empty stadium — no runs needed, just stay not out. That is not real practice. And in a World Cup knockout that same middle order will be woken when the openers are out in the second over, with no temperature to start from in the eighth.

The outside misreading

A reader who takes only the scoreboard from this report will conclude: India's batting is from another planet, New Zealand were scattered, and the series is one-way traffic.

Wellington's ground files an objection. Short square boundaries, a flat drop-in pitch, and that wind which sometimes drifts to leg and sometimes to square — boundaries come cheap here. Where boundaries are cheap, 90 per cent of runs arriving in boundaries stops being as supernatural as it would be elsewhere.

The second objection is that a big score makes us stop looking at the bowling column. The attack that conceded 198 is happy watching 199 chased in thirteen overs, but that same attack took three wickets in twenty overs. In T20, taking wickets is the most reliable way of stopping runs; when you cannot break an innings regularly, success starts depending on the batting.

The third objection is the important one. In this series India's middle order has been systematically kept out of practice. That is the price of this success, and it will be paid in the innings where paying is expensive.

What to watch next

Nobody seriously expects Wellington's records to repeat in the next two matches. But two things will be worth watching, and neither of them is batting.

First: the day India's openers are out before the tenth over, the middle order gets its first real test — and that day will tell us whether this 3-0 lead is squad depth or two men in form. Second: whether India's bowling changes its plan to take wickets in the death overs, or whether it is still waiting to be rescued by the batting.

I kept the chart long after everyone went home. This series' chart is only half full, because the column where the bowling goes has not dried yet. Somewhere in row 47 of that Eden Gardens media overflow, where I first drew the powerplay column, a pattern started to breathe — and the pattern was this: a big score is not always a big batter's.

The question is whether India, with two matches left and a 3-0 lead, will use them to find out where its real protection lies — or discover it in the next tournament's knockout, when there is no time left to look.