118/0 in Six Overs, Then Six Wickets for 81: The Real Scorecard of the Third T20I Is Not in the Records List

On the evening of October 27, the scoreboard read 100 without loss at the end of the fifth over. At the end of the sixth it read 118/0 — 19.67 an over. New Zealand had made 199, and India chased it in 13.2 overs with 40 balls unused. The next morning, the expected document appeared: a long list of records — fastest T20I hundred by an Indian, most sixes in a calendar year, hundred inside five overs, and so on.

I read the list, then went back to the scorecard and got stuck there. The journey from 118/0 to 199/6 is six wickets for the last 81 runs. The match was won by six wickets. Losing six wickets for 81 runs on a surface where you did not lose a single one in the first six overs is not a record. It is a question about process.

Twenty-five years of habit has taught me one thing: whenever a match starts being remembered by its records, I return to the tape. This time I went looking for a verdict and came back with a question.

First, the story everyone heard

This was the third T20I of a five-match series, and India led 3-0 after it. The series was settled in three games with two still to play. A game that has already decided a series grants both sides permission to experiment, and experimentation widens variance in both directions — sometimes 118/0, sometimes six wickets for 81.

The figures logged in the Khel Now report are startling: Abhishek Sharma 113 off 38 balls at a strike rate near 297, with 11 sixes and a 35-ball hundred. Vaibhav Sooryavanshi, aged 15, 45 off 19. Between them a first-wicket stand of 133 off 43 balls, a rate of 18.13. Arshdeep Singh with 39 T20I wickets in the calendar year, equalling Josh Little's record.

Honesty is required here. The report does not name the venue, carries no pitch report, and gives no scorecard for New Zealand's innings beyond a target of 199 and the dismissal of Tim Seifert. No weather, no dew, no toss. Even the year is not clearly stated; only the date, October 27, is logged. Every one of these numbers needs verification before it is cited externally. What was left out is the biggest story of the match.

The core issue: 297 does not mean 297

I opened the numbers on Abhishek's innings. Thirty-eight balls, 113 runs, 11 sixes. An elite T20I opener generally strikes between 160 and 200. A rate of 297 is roughly one and a half to two times that. This is his ceiling, not his level — and treating a ceiling as a level is the oldest error in the book. One innings does not set a new baseline, especially an innings built on 11 sixes.

A six-dependent scoring model is seductive and unstable at the same time. Eleven sixes in 38 balls means a large share of the runs came from a small number of events. Such a profile has a fat right tail — the match-winning 70 off 30 — and an equally fat left tail when the boundary option is removed: two-paced surfaces, big grounds, quality death bowling.

The records list carries another item: 11 T20 centuries, past Virat Kohli's 10. But Kohli does not have 10 T20I hundreds. The figure therefore almost certainly aggregates all T20 cricket, franchise and international combined. Lumping T20 and T20I into one ledger is a category error, and it happens to be the most convenient error for making headlines. If the number is built on franchise volume, it is an artefact of a commercial ecosystem, not a measure of international dominance.

The 85 sixes in a calendar year, past Rohit Sharma's 80 from 2026, may well be accurate, but it speaks to volume more than skill. You do not hit 85 sixes in a year unless you are playing continuously across three calendars. That is a record, and it is also a workload warning. The report presents it purely as an achievement, when it is both things at once.

The 81 runs that made no list

118/0 became 199/6. The arithmetic is simple: six wickets for the last 81 runs. This does not mean the chase went wrong — 40 balls remained and the result was never in danger. It does mean that on a platform where you lost no wicket in six overs, six wickets falling afterwards points to a question of priority rather than technique, and priority errors get expensive on the next platform of the same kind.

With no venue or conditions logged, the strongest inference is a flat deck and/or short boundaries. If that holds, every batting record in this match needs a conditions discount. And if New Zealand rotated their attack after going 3-0 down — a detail absent from the report — the efficiency of the chase is artificially inflated.

The bigger technical limitation is that this match is useless as a test case. The chase finished in 13.2 overs. The middle-overs containment phase and the death overs were never contested. Yorker plans, pressure on a set batter, death-over economy — none of it is verified by this fixture. Arshdeep's 39 wickets are an incomplete story for the same reason: a calendar-year wicket tally is a schedule-volume metric, not a skill metric. The report gives no economy rate, no strike rate, no balls per wicket. And the headline says records were broken, when Arshdeep equalled a record rather than breaking it.

Sooryavanshi's 45 off 19 at 15 is a genuine talent signal and completely unquantified. No career data, no domestic benchmark, no split by bowling quality. And the 133 off 43 stand overstates his individual contribution: in a partnership running at 18.13, the junior partner's numbers are substantially a function of the senior partner's strike rate and boundary rate.

Where I could be wrong

Let me turn my own argument over. Suppose 297 is not an outlier but the new baseline. T20I scoring keeps climbing; the 118/0 powerplay that seemed impossible a decade ago was normalised when Australia made 113/1 against Scotland in 2026. If the modern T20 template is flat deck, short boundary and risk on every ball, then demanding a conditions discount is outdated thinking. And those six wickets? Possibly not a process failure at all but a comfort error — 40 balls in hand made risk rational. In that reading, my post-mortem looks needlessly cautious.

One thing does not move under that argument. This match contains no scorecard for India's bowling or New Zealand's batting. When half the match is unrecorded, conclusions drawn from the other half remain half-conclusions.

What to watch next

I publish the conditions alongside the prediction so that being right can be checked rather than claimed. The next time Abhishek Sharma plays five innings against a full-strength attack on a two-paced surface, his six-based model gets tested. For Sooryavanshi the question is workload, not performance — senior international cricket at 15 sits at the highest point on the growth-plate and stress-injury risk curve, and the report does not mention it. Arshdeep's 39 wickets will acquire meaning when his death-over economy surfaces next season.

And the accountability sentence, because naming the system is the easy exit. The decision to field a 15-year-old in the senior side belongs to the selectors and the BCCI workload desk. They had options. A competent version of that call gives talent a fast lane with an explicit cap on matches — and makes the cap public so it can be tracked.

The records list will be stale within a year. The six wickets for 81 will not. The question is whether, the next time someone plays six overs at 19.67 an over, the coach watches the scoreboard or the platform that has not yet cracked.