118 in Six Overs, 21/4 in the Last Twenty Balls: The Story Bigger Than Abhishek Sharma's 35-Ball Hundred

Six Overs That Settled the Match

On Tuesday night in Brisbane my desk had two screens. On the left, the feed of the third T20I. On the right, my powerplay sheet — the same sheet I have been filling since 2026, first for Queensland grade cricket, then for Rising Pune Supergiant's first full-time data desk, and now for a franchise and a broadcast desk. After the sixth over the sheet flashed two numbers: 118 and 0. India had been set 199 and had already burned 59.3 per cent of it inside the powerplay.

The headlines the next morning will be about the 35-ball hundred. Abhishek Sharma made 113 off 38, hit nine fours and eleven sixes, and became India's leading century-maker in men's T20 cricket — 11 hundreds, ahead of Virat Kohli's 10. All of that is true and all of it should be recorded.

But I have suffered from one habit for fifteen years: I read a match through its most decisive number, not its largest. And the decisive number here is 118, not 11. Because 118 is the figure that turned the remaining fourteen overs into a formality — and what happened in those fourteen overs says more about this Indian batting line than the hundred everyone will write about.

Context: A 199 Target, One Change, and a Spinner Who Arrived Late

Shreyas Iyer won the toss and chose to bowl — the reflexive modern choice, since the target is known in the second innings and the dew risk is lower. New Zealand lost Tim Seifert early, but Finn Allen and Daryl Mitchell counter-attacked to give the hosts a platform. Allen fell in the forties, Mitchell finished unbeaten on 89, and Bevon Jacobs contributed a useful knock.

India's bowling has shown a strange dual nature this series. Bhuvneshwar Kumar was once again ineffective — no wickets with the new ball, no pressure afterwards. But at the death India did what it has learned to do as a process over two years: Prince Yadav's comeback spell, and the yorkers of Arshdeep Singh and Nitish Kumar Reddy. The result was that New Zealand could not pass 200 and the target stopped at 199.

The first argument starts here. My desk's estimate was that the closing phase of the first innings was quick enough that 199 would be short — but that estimate is match-specific, and I will not convert it into a series-level rule. What I can say is this: when your opening pair can produce 118 in six overs, 199 stops being a target and becomes a deadline.

And India built that pair through a change that will be under-credited. Young Vaibhav Sooryavanshi was sent to open with Abhishek. It was an experiment, and an experiment succeeds only when its risk is defined in advance. The risk here was a teenager facing an international seam attack with the new ball. What happened was the reverse: Sooryavanshi supported Abhishek, the partnership reached 133, and New Zealand's powerplay blueprint tore in the first over.

Core: The Laser of 38 Balls, and the Crisis of 20

Boundary accounting: he did not reduce risk, he reduced dots

Break the innings down. 38 balls, 113 runs. Strike rate 297.4. Of those, 20 boundaries — nine fours (36 runs) and eleven sixes (66 runs) — meaning 102 runs came in boundaries alone, 90.3 per cent of the total.

Now look at the part nobody looks at. Off the remaining 18 balls he made 11 runs. That is roughly 0.61 runs per ball across those deliveries. If most of them were singles and dots, his dot-ball count across 38 balls was around eight — a dot rate near 21 per cent.

That is the real story. The conventional way to bat fast in T20 is to raise risk and accept wickets. Abhishek inverted it: he did not reduce risk, he reduced dot balls. A 21 per cent dot rate is an ordinary figure for an opener; attach it to a strike rate of 297 and you have an innings with no easy historical comparator, because normally the price of a higher strike rate is paid in dots. Here both improved together.

Which is why a 35-ball hundred is not merely a "fast hundred". It is a different species of innings. When I sat on Rising Pune's desk in 2026 and our model kept flagging Mumbai's death-bowling edge at under seven an over, that was the lesson — the one-run final taught me that a margin is a story with decimals. Here the margin is 297.4, and the number hiding inside it is 21 per cent.

What 118 actually means: not a record, a baseline

India made 118 without loss in the powerplay — the highest powerplay total by a Full Member nation in men's T20 internationals. It is a record, and it will be recorded.

For me it is less a record than a baseline. 19.67 runs per over in the powerplay means India banked in six overs what many sides bank in ten. And it was not a lone explosion — the ten-over score reached 178, a sustained 17.8 runs per over. Between the sixth and tenth overs India added 60 more without losing rhythm.

Here is the point I repeat in every report: the powerplay is not a phase, it is an investment. A side that banks 118 in six overs can absorb damage across the other fourteen. That is the buffer models routinely underprice, because models read totals and not the risk tolerance the buffer converts into.

21/4 in the last twenty balls: the passage nobody watched

Now the passage I wrote this piece for.

After ten overs India were 178/0. The target was 199. They needed 21 runs off 60 balls. India completed the chase with 40 balls remaining, i.e. in 80 balls. The arithmetic is blunt: after the tenth over India scored 21 runs in 20 balls and lost four wickets — a rate near 6.3 runs per over.

Read that again. First six overs: 19.67 runs per over, no wickets. Last twenty balls: 6.3 runs per over, four wickets. In the same innings, on the same pitch, against the same attack.

Abhishek was caught at deep mid-wicket by Glenn Phillips off Kyle Jamieson, and Matthew Fisher took his maiden T20I wicket by dismissing Sooryavanshi. Jamieson and Mitchell Santner picked up wickets in that same stretch. The scorecard will say India won by six wickets, which is true. But the scorecard will not say that the final third of that win was a four-wicket erosion executed under zero pressure.

For me that is the most informative event of the match. A target of 199, 60 balls left, ten wickets in hand is the lowest-pressure scenario T20 offers. And precisely there India's middle order collapsed to 6.3 an over and lost four wickets. When pressure is zero and output still falls, the cause is not pressure — the cause is technique or selection.

Santner's hold-back: hindsight or a decision cost?

New Zealand's biggest tactical error is being read as holding Mitchell Santner back against two left-handed openers. By the time he bowled, the contest was decided.

The argument is superficially right. But I want to push it one step further, because the problem was not Santner's selection — it was the sequencing of his use.

A match-up bowler is worth most when the required rate is low and the batter must take risk. In the sixth over India needed 13.67 an over with no pressure at all; a left-arm spinner then would have forced Abhishek to take risk, because singles do not close a chase. In the eleventh over, with 21 needed off 60, Santner's over could have been expensive or cheap and the match would not have moved.

This is where I apply my hardest condition: a match-up bowler is an instrument, not a phase. Wickets taken in an over after the target is effectively achieved are consolation, not strategy. Santner took wickets late — and that is exactly the evidence hindsight criticism uses for its own case. But wickets at 6.3 an over do not buy matches.

Eleven hundreds: not a ranking, a ledger

Now the number that will make tomorrow's headlines. Abhishek now has 11 T20 hundreds — past Kohli's 10 for India. Globally, Chris Gayle leads with 22, Babar Azam is second with 13, then Abhishek on 11, then Quinton de Kock, Kohli and David Warner on 10 each.

I read that list as a ledger, not a ranking. A hundred in T20 is a rare event, and the count of rare events is set by three things: balls available at the top, the team's scoring environment, and selection frequency in the format.

Gayle's 22 came across two decades of franchise cricket at lower run rates. Babar's 13 came as an anchor inside a heavy bilateral calendar. Abhishek's 11 have come inside a very short window and from innings like this one, where the hundred arrived in 35 balls.

Those are three different instruments being counted in one unit. A 60-ball hundred and a 35-ball hundred are not the same event, and the list treats them as identical. So the right question is not "how many" but "how fast" — and if you ask that, the order changes.

My desk no longer records a T20 hundred as a milestone. It records how many balls it took and how far the innings sat above the powerplay baseline. It is a duller unit, which is precisely why it is more honest. The model is not the truth; it is the argument we can test.

India's second string: a selection bind, not a talent shortage

The match showed the thing I have been writing about for eight years. India changed its opening pair, fielded a teenager, and produced the highest powerplay score in Full Member history. That is not coincidence, and it is not explained by the lazy phrase "depth of talent".

It is structural. The hardest team in world sport to make is India's second XI, because even that second XI runs the same powerplay model as the first. When your bench can break a record your first choice never broke, your problem is selection, not production.

The real cost of the IPL era was never that Test cricket weakened — that argument is old and tired. The real cost was that domestic cricket's media footprint shrank, so there is no public, auditable record of that second string's output. We only see it when it produces 118 on an international night.

Contrarian: Did the Powerplay Win This Match? An Honest Answer at n=1

Now the part where I have to argue against myself.

I wrote above that 118 settled the match. That sentence is true and incomplete. The value of 118 depends on the target. Against 199, 118 is 59.3 per cent of the chase inside six overs. Against 240, the same 118 in the same innings is 49.2 per cent and the chase is still alive. The record we are calling match-winning is target-relative, and the smallness of the target came from New Zealand's death bowling, not from Abhishek's batting.

Second, and more important: this is one match. I have a sample of one powerplay for this opening pair. A powerplay record in a single game is an event, not a trend. I learned that expensively in 2026, when a sample of 60 crowdless matches in the UAE showed me that what we call home advantage was mostly toss and dew. I stopped writing that grounds are fortresses then. The same discipline has to apply here.

Third, Santner. I called it a decision cost, but I have to concede that the counterfactual is unavailable. We do not know what happens if Santner bowls the third over. Abhishek may have been out to him and the match may have turned. What we know is that in the sequence New Zealand chose, his wickets could not change the result. That is a conclusion, not a principle.

Fourth, and least comfortable: the manner of Abhishek's dismissal. Caught at deep mid-wicket — his risk profile is still airborne. A 52.6 per cent boundary rate and a 21 per cent dot rate is a very narrow equilibrium. On slower, lower surfaces — and the next T20 World Cup is in India and Sri Lanka — that method will be priced differently. My model cannot yet say at what price. So I am filing it as a hypothesis, not a verdict.

Fifth, the 21/4. I called it the most informative event. A fair objection: those four wickets fell while batters were taking deliberate risk, because at 6.3 an over there was no rush to make 21 and they wanted to finish early. So the erosion was pressure-free but also intent-driven. That weakens my argument and I will not hide it. What survives: that risk appetite is a signal, and the next time the target is 240 rather than 199, the same appetite will be expensive.

My Own Audit

Before the series my desk's model rated New Zealand's death bowling above India's. In the third match New Zealand could not pass 200 at the death and India controlled three overs there with the yorker. My estimate was directionally wrong in this match. The cause is clear: I assessed New Zealand's death bowling largely on the previous series' numbers, and those numbers carried dew and surface effects I had not separated out. I am recording the correction now, because my credibility is the asset being managed.

A full-time data desk turns pressure into a repeatable process — but only if it runs its own mistakes through the same process.

Methods Footnote

Every figure here comes from the source report or from arithmetic performed directly on it. Abhishek's strike rate (297.4), boundary share of runs (90.3 per cent), run rate on non-boundary balls (0.61), the dot-ball estimate (about eight), and the post-powerplay split (21/4 in 20 balls) are all derived from the scorecard. Sample: one match. Comparison to a powerplay baseline is my desk's estimate, not official data, and should be read with error bars. No counterfactual sample exists for Santner, so that claim is inference. Era adjustment has not been applied to the historical hundred list; that is the next instalment.

Takeaway: What to Watch Next

The series is 3-0, so the remaining two matches are for information, not results. Three things are worth watching in them.

First: does New Zealand open with spin in the powerplay? If yes, they learned from the Santner error — and the real examination of the Abhishek-Sooryavanshi pairing begins, because spin with the new ball against two left-handers is a different genus of risk.

Second: does India rest Abhishek? If it does, we get to see whether this powerplay model belongs to a person or a system. That is the most valuable question for 2026.

Third: the 21/4. If India's middle order contracts again in a dead contest across the next two matches, it will not be coincidence. And if it happens, my desk will record it more seriously than the hundred.

The auction room taught me that every bid is a hypothesis with a deadline. Batting is the same: every 118 is a hypothesis, and the next pitch is its test. A Data Monk trusts the ledger, but an ENTJ knows when to call the audible.