Abhishek Sharma's 35-Ball Century and a 118-Run Powerplay Take India to an Unassailable 3-0

My notebook always splits the powerplay into two columns — runs in one, the ball that was never bowled in the other. On Tuesday night in the third T20I against New Zealand, the second column became the biggest question of the match. By the end of six overs India had 118, and Mitchell Santner had not bowled a single ball in that powerplay. I pulled the page back, because the first field map began where the L4 cracked: whenever a decision does not add up, I still draw nine fielders on paper. Santner's four overs were nowhere on that page. India chased 199 with 40 balls to spare, won by six wickets, and took an unassailable 3-0 lead in the five-match series. What the scoreboard hides is that this match was won in six overs and very nearly lost in the last 22 balls.

Shreyas Iyer won the toss and chose to bowl, taking on the risk of batting second. Tim Seifert went early, but Finn Allen and Daryl Mitchell counter-attacked to hand the hosts a platform. Allen fell in the forties; Mitchell carried the innings to an unbeaten 89. Bevon Jacobs chipped in usefully and New Zealand were kept under the 200 mark, leaving India a target of 199.

India's bowling was mixed. Bhuvneshwar Kumar again failed to make the kind of impact his experience promises, but the visitors recovered at the death: Prince Yadav produced an impressive comeback and Arshdeep Singh and Nitish Kumar Reddy landed their yorkers. That discipline kept 199 from becoming an unreachable score — the same discipline that will decide who breathes easier under pressure later in this series.

The 118 run powerplay: a record, and what it means plainly

India changed the top of the order, sending Vaibhav Sooryavanshi out with Abhishek Sharma. The move paid better than anyone expected. Two left-handers attacked the New Zealand attack from ball one, and India reached 118 in the powerplay — the highest powerplay total by a Full Member nation in men's T20 internationals. At ten overs the figure read 178. The opening stand was worth 133.

Sooryavanshi missed a half-century but supported Abhishek so aggressively that the opposing captain never got a field to settle. Matthew Fisher dismissed him for a maiden T20I wicket — a personal moment, but the damage was already booked by then.

Abhishek made 113 off 38 balls with nine fours and eleven sixes. His strike rate sat near 297, and the number that surprised me most is this: 102 of those 113 runs came in boundaries — roughly ninety per cent of the innings travelled over the fielders rather than between them. A 35-ball hundred. Kyle Jamieson dismissed him, Glenn Phillips took the catch at deep mid-wicket, and by then the result was fixed.

With that hundred Abhishek now has 11 in men's T20 cricket, moving past Virat Kohli's 10 for India. Globally only Chris Gayle (22) and Babar Azam (13) are ahead; Quinton de Kock, Kohli and David Warner sit on 10 each.

Santner's unbowled over: where the mistake was, and where it wasn't

The line everyone will repeat is that keeping the spinner away from two left-handers cost New Zealand. The data backs the conclusion — by the time spin came on, India had complete control. But calling it a mistake means first identifying which layer failed.

In T20 captaincy, shielding a left-arm spinner from left-handers is a standard match-up move. Santner's decision did not sit outside that logic. The problem is that the logic works when you are bowling with a rate to defend. Here New Zealand were defending 199 — already a short score. Holding spin back meant the only wicket-taking option in the powerplay was never placed on the table. When Santner finally bowled, India needed 21 off 55 balls. No spinner, from any angle, could have slowed that rate.

I keep two notebooks: one for what happened, one for what almost did. The second one says that had New Zealand posted something near 220, the same decision would read as smart captaincy. At 199, the decision became a shortcut explanation for the result rather than its cause. This is retro-fitting at its most comfortable — blaming the process after seeing the outcome.

Sixty-six runs for five wickets: the hidden part of the scoreboard

Here is an arithmetic nobody repeated. The opening partnership broke at 133. India finished six down. So after 133, India scored 66 runs and lost five wickets. From 178 in ten overs, they needed 21 off 60 balls; the match ended 22 balls later. Those five wickets fell in a passage where nothing was at stake — which is why no one will remember them.

Had the same 66-for-five shape appeared with 4 balls left instead of 40, tomorrow's headlines would read 'collapse'. The pattern was identical; only the pressure was different. I learned this after the 36 at Adelaide — a collapse is not an event but a sequence, and the 36 at Adelaide became a pattern I could read backward. Here the sequence says India's batting rested on one innings, and after Abhishek left, the middle order spent five wickets to find 66 runs on a surface where the ball was coming on.

New Zealand's innings should be read the same way. Mitchell's unbeaten 89 looks handsome in the book, but on that pitch the hosts needed 220-plus. An anchor innings that carries a side to 199 and stops there is not a saving innings; it is a limiting one. India's death yorkers, and Prince Yadav's comeback, widened that gap.

Where the Kohli comparison slips

Eleven hundreds against Kohli's ten sells well, but that comparison is priced in two markets. Kohli's hundreds came in an era when 150-160 was a normal T20I total and a top-order batter was expected to bat twenty overs. Abhishek's are arriving in a batting economy where the powerplay price has reached 118 and 38 balls can define an entire innings. One word — 'hundred' — is stuck on two different products.

It is the same dual-pricing problem I keep meeting in auction data: one player, three mechanisms, three prices. Here the mechanisms are franchise cricket and international cricket. Some of Abhishek's eleven hundreds have come on smaller grounds, flatter pitches and against thinner attacks; weighing them equal to Kohli's ten is a margin-calculation error. That does not make Abhishek's innings cheap. It means the two numbers belong in separate accounts, and the day they get merged into an all-time list, the source and its date should travel with them.

Then there is Bhuvneshwar. With the new ball his impact is visibly thinning, and this was the third time in the series it showed. That is less a question of experience than of workload and pace profile — the same structural problem I look for in the calendar rather than in personal luck. If he still has no powerplay wicket across the next two matches, the debate becomes a selection one, when the real question is the preparation cycle.

Takeaway

The fourth T20I will test whether the 118-run powerplay was a design or an accident. Three signals are worth watching. If New Zealand use spin early in the powerplay, they have thrown away their match-up book. If India start slowly in the first six overs and still reach 170-plus, the depth is proven. And if Abhishek falls inside 30 balls and the total does not reach somewhere near 199, then Tuesday's innings was a shield more than a performance. That last part matters most — the part written on the scoreboard as 66 runs for five wickets, and never lit up.