Wellington's 118/0: How Six Overs Rewrote the Arithmetic of a 199 Chase

The number glowing on the Wellington scoreboard after six overs was 118/0. Six overs, no wicket, 19.67 runs per over. The chasing side had 120 balls for 199 runs and finished the job in eighty. Forty balls went unused, six wickets stayed in hand, and the series closed 3-0.

The match report's conclusion writes itself: India won, India swept, the openers were brutal. Mine sits slightly elsewhere. I opened the ledger before sunrise; by noon the numbers had rewritten the story. The useful question is not how many runs were made. It is which forty deliveries of a 120-ball chase were saved, and in which over that saving was banked.

Abhishek Sharma made 113 off 38 balls. Strike rate 297.4 — roughly three runs every ball. One batter produced 56.8 per cent of the target at a speed that ensured the required rate never climbed past seven. Vaibhav Sooryavanshi, at the other end, made 45 off 18, a strike rate of 250. Together they put on 133 in 44 balls, 18.13 runs per over. The first wicket fell at 7.2 overs, at 133/1. From there, 66 runs were needed off 76 balls, which in the ledger's language is a settled chase. The rest of the order had only 24 balls to use because the work was already done.

The record that went into the book is the highest run rate for a 100-plus opening partnership in men's T20 internationals — not the highest partnership total. That distinction is not cosmetic. A partnership-total record tests how long two batters lasted. A run-rate record tests how quickly they converted survival into arithmetic. Wellington produced the second kind, and it should not be read as the first.

Method: what is verified and what is not

Let me put the incomplete part first. The match report I am working from carries no official scorecard link and no ball-by-ball feed. So 118/0, the 133-run stand, 113 off 38 and 199 in 80 balls are all numbers arriving by way of a media report, and I am holding them as verification-pending until they are checked against ESPNcricinfo or ICC official data. This is not ceremony. Of the record claims I have filed without a cross-check in the last eight years, three had to be corrected publicly. The error ledger is public, which is why it is better to flag it up front.

Second, separate what I counted from what I estimated. The 118/0 and the 19.67 are arithmetic: 118 divided by six. The 13.2 overs is 80 balls, and 199 in 80 balls is 14.93 an over. Also arithmetic. The estimate is anywhere I allow that something "may" have happened within the limits of three figures.

Third, the baseline. In my ledger, men's T20I powerplay averages across the last five seasons sit in the 45-to-60 band. The band is wide because conditions, pitches and opposition quality shift every series. When 118 turns up, even the top of that band looks short. Six overs for 118 is roughly double the baseline. That is worth reporting as an anomaly — not as a form story, as a plain gap.

Core: the arithmetic of six overs

For a chasing side the "turning point" is usually the eleventh over, where the run rate buckles, wickets fall and the model breaks. The model was built for football; cricket broke it by the eleventh over. Here cricket never needed the eleventh. The moment was the sixth over, at 118/0. That single figure fixed the shape of everything after it: the required rate dropped from 9.9 to about 3, and 81 runs were needed from 14.2 overs.

Compare it with the 2026 football blog where I built a shot-quality model. Spain completed 1,029 passes in Moscow and lost on penalties, because there was possession without penetration. Wellington ran the reverse — possession of the ball ended inside six overs, because the penetration went straight to the boundary. Cricket can carry an expected-runs-above measure, but I do not have the ball-by-ball feed for this innings, so I will not print a number I have only half counted. Dropping a conclusion without the sample contradicts the method.

One more figure reshapes the story. India finished the chase in 80 balls, which means 40 deliveries were never used. In bilateral T20 that matters twice: in net run rate, and in the opposition's bowling resource. Finishing inside 13.2 overs means the home side's middle- and death-over specialists never got the phase in which plans are revised — the slower ball swapped for the bumper, the yorker moved to third man. That revision is a process, and 80 balls is not enough time to complete it.

And Abhishek's 113 is a boundary marker more than a monument. 113 off 38 implies that nearly every twelfth delivery was one he did not have to play to a plan. A strike rate of 297 is built on a surface whose toss, pitch and boundary dimensions are known. None of those three details appears in the report I worked from.

Contrarian: the control group that 3-0 hides

Here is the question that is not fun. Was this an innings or a surface? I have a limited case — a series already decided after two matches, with the third played under different incentives. Dead rubbers sit in a separate column in my ledger because both teams' licence to experiment changes. That is the control-group argument: when a side is 2-0 up, the third match is measured on a different instrument. Keeping it apart from the record is essential, or we will mistake one experiment for a law.

Second, correlation against causation. The 118/0 and the win live inside the same innings, which makes it easy to call one the cause of the other. But 118/0 has two possible sources: batting intent and bowling execution. Without ball-by-ball data I cannot separate them, and I will not claim I can. The record sentence should therefore read "the openers scored off overs", not "the openers attacked the bowling". Which side the causation sits on is the next verification task.

Third, metric transplant. Pulling a trend out of this innings that travels across formats is risky. A 19.67 powerplay rate is a T20 instrument; applying it to ODI or Test cricket without shifting the window is the same error as lifting domestic numbers straight onto a World Cup surface. If the metric travels into a report, it should travel with its declaration: baseline — men's T20 internationals; window — last ten seasons; exclusions — innings played on artificial boundaries.

Fourth, and I write this with some reluctance: Sooryavanshi's 45 off 18. A teenager producing that tempo is technically good news. It is also a load question. My youth-development ledger has carried the same line for years — early-maturing players are asked for early-matured output while the body is still being built, and it gets folded into senior rhythms. This match is one more data point to be handled carefully.

Takeaway

Count first, question second, narrative last — that is the whole method. The cleanest signal out of the counting is not on the scorecard. It is the powerplay run rate. Watch this team's first-six-overs average in the next series, not the final totals. If 118/0 was a surface, it returns to the 50-60 band within three matches. If it was capability, the baseline itself shifts — and the eleventh-over model gets thrown out.

What I want right now is not an opinion but a feed. Three figures and four sentences can build a win story. They cannot build a record. The next time an opening pair posts a stand above 18 an over, ask first what the pitch was doing, and second how many deliveries did nothing a wicket would reward. The data did not change the game; it changed the way we watched it.