118/0: Wellington's Powerplay Record, and the Price the Scorecard Doesn't Show

Read the Empty Balls First

Open the scorecard of the third T20I in Wellington and look, before any digit, at the absence: India finished a chase of 199 in 13.2 overs. Six wickets in hand. Forty balls unused.

That is a cancellation, not a chase. When a T20 side wins with 40 balls to spare, the final third of the match was never played. I have never trusted filled-in scorecards more than empty ones. In 2026, at Salt Lake Stadium in Kolkata, I had no chair in the main press box and charted a full match standing in the overflow tribune. The missing chair told me what the match was not showing. Forty unplayed balls speak the same language.

What happened before them: 118/0 in the powerplay, an opening stand of 133 runs at 18.13 per over, Abhishek Sharma 113 off 38, Vaibhav Sooryavanshi 45 off 18.

Now add those last two. 113 and 45 is 158. The reported partnership is 133. That contradiction is the most honest observation in this match, and I will return to it — a number that does not reconcile with itself has not yet earned the right to reconcile with anything else.

What the Report Does Not Carry

This is a mainstream newspaper match report with no named statistical source and no official scorecard link. Source quality is medium. Every record claim should sit in the pending-verification tray until it is matched against an official scorecard, because T20 records age faster than milk.

The shape is simple. Third T20I, Wellington, India won by six wickets, series sealed 3-0. The target was 199 off 120 balls, meaning the required rate on ball one was 15.11 an over — a rate most sides reserve for the last five overs. India asked for it from the first ball.

Three things the report does not give: the toss, the pitch and weather, the boundary dimensions. Without the toss we cannot know whether 199 was a defendable total or a par one. Without pitch detail we cannot separate batting from bowling execution. Without boundary size, 118/0 means different things.

What we can say without any of that: a powerplay at 19.67 an over is never purely a batting event. It is also a failed bowling plan and a broken captaincy decision cycle.

The Arithmetic of 118/0

Six overs, 118 runs. Divide: 19.67 per over. A good men's T20I powerplay sits between eight and nine. Ten is considered excellent. 19.67 is roughly double that — India scored in six overs what most teams score in ten.

The consequence is structural. At eight an over, a captain can process decisions sequentially: one bowler, one field, one plan, with the state of the game barely changing between balls. At 19.67, decisions must be processed in parallel and the field cannot be reset between deliveries. The captain does not lose the tactical argument so much as lose the time in which tactical arguments are conducted.

An honest caveat: I do not have the over-by-over breakdown. I do not know how many of those 118 came in which over, how many sixes, how many dots. 118/0 is a terminal number, not a curve.

The Record Is a Rate, Not a Total

This is the detail most readers will skim past. The record is not the highest opening partnership in men's T20Is. Bigger stands exist. The record is the highest run rate for a 100-plus opening partnership: 133 at 18.13 an over.

That distinction carries the whole story. A large partnership can be built slowly and then inflated by one over. 133 off 60 balls is not the same object as 133 off 44. A rate record tells you the bowling side had no correction window — no over in which a plan could be reset. It is a record about the opposition as much as about the batsmen.

The arithmetic: 133 at 18.13 implies roughly 44 balls, about 7.3 overs. Which would leave India needing a further 66 from about 36 balls after the stand broke — a slower middle phase the report leaves out because it is not exciting. That middle phase is where the information lives.

Three Numbers That Do Not Shake Hands

Report three figures: partnership 133; Abhishek 113 off 38; Sooryavanshi 45 off 18.

Believe all three and the maths breaks. The individual scores total 158. The balls faced total 56, or 9.2 overs — more than the 7.3 overs implied by 18.13.

Two readings survive. Either the stand was 133 at 18.13, meaning about 44 balls, of which Abhishek faced 38 and made 113 — leaving Sooryavanshi roughly six balls and twenty runs. Or the individual scores are right, the stand was 158, and the rate was 16.93, not 18.13.

Between those two readings sits 25 runs and 12 balls, and it changes who this innings belonged to. In one, Sooryavanshi is a supporting actor. In the other, he is a near-equal partner. Until an official scorecard settles it, every downstream claim about this match is provisional. That is not pedantry. It is the difference between the headline and the innings.

Abhishek Sharma: 38 Balls, 113 Runs

Strike rate 297.37. Nearly three runs per ball.

A good T20I opener runs at 140 to 150. This is double. It means that in a 38-ball innings he was scoring roughly 18 an over by himself.

Here is where the wagon wheel would arrive and ruin everything. It would show where he hit. It would not show what the bowler planned, where the field was, and at which ball the plan broke. A wagon wheel is a map of outcomes, not of decisions — and at a strike rate of 297, decisions are the only subject worth discussing.

A batsman scoring 113 off 38 is not choosing shots. He is deleting the bowler's options. Once the rate crosses 18 an over, a bowler has no safe delivery left except the yorker, and the yorker is only safe if he can land it under pressure. It also renders the partner structurally inactive: at that rate, the other batsman's job collapses into rotating strike.

Sooryavanshi: 18 Balls and a Selection Risk

Eighteen balls at a strike rate of 250 proves nothing about a batsman. It is a sample size on which no serious analyst would rest a conclusion. Eighteen balls can contain a player's best cricket and the next eighteen can contain his ordinary cricket.

So let us talk about the structure that put him there instead. A teenager in India's top XI is not a match decision, it is a system statement — a choice to bet on the future rather than on experience. There is a risk and there is a cost. The risk is that international bowling is either the fastest education available or the most expensive. The cost is that every ball he faced in this series was a ball someone else did not.

Around young talent, Indian cricket has built a noise economy in which the loudest earners are the people who never bowl to them. Contracts, representation, auction speculation, pressure for the next series — the machinery converts an 18-ball innings into an 18-month guarantee. I have watched that pattern in football, where the agent's noise outruns the player's output. Cricket is on the same road with less time, because the auction comes every year.

The Shape Log

I keep a shape log — a timestamped notebook of every change. I do not have over-by-over data here, so this is a framework, not a report. It is the container the real numbers go into.

Moment one: score around 40, rate past ten. Three options — bring spin on and preserve it for the middle, change the pace bowler, push the field back. All three are constrained by powerplay fielding restrictions.

Moment two: score around 70, powerplay not yet done. The objective flips from taking wickets to stopping runs. At 18 an over, stopping runs is also impossible. This is where the captaincy structure fails — when defensive and attacking options are both empty.

Moment three: end of the sixth, 118/0. Eighty-one needed off 81. Required rate 6.0. There is no pressure left because the pressure has already been spent.

Cricket measures the bowler's economy and the batsman's strike rate. It has no equivalent number for the captain. That measurement gap is real.

The Chase Arithmetic

Start: 199 off 120, required rate 15.11. After six overs: 81 off 81, required rate 6.0. The required rate fell by two-thirds in six overs. That collapse is the match. Everything else — six wickets, 13.2 overs, 40 balls — is an expansion of that one sentence.

India did not chase 199. India played the first third of a chase and the last two-thirds were never played. When the required rate is 6.0 with ten wickets in hand, the result is decided even if the scorecard has not caught up.

The Forty Balls India Never Got

India's middle order did not bat. No fourth-wicket crisis, no spinning ball to negotiate, no asking how to make 90 off 70 under lights.

A 3-0 sweep is a clean-looking result that produces almost no decision-relevant data. The conventional reading — India's batting depth is extraordinary — is fair, and the evidence supports it. But that reading fails under one specific condition: a gripping surface where the powerplay rate compresses to eight or nine. We have no evidence about this XI in that condition, because this series never created it.

India won this series 3-0, and the most important thing about it is that India learned almost nothing from it. That is not sarcasm; it is an analytical complaint. You learn your limits from bad days. Scoring 118/0 in a 199 chase never introduces you to your limits.

Constraints Paragraph

Bowling load: New Zealand's bowlers absorbed the sharpest version of this — defending at 19.67 an over is mental fatigue, in a series already gone, ahead of a home block on different surfaces where these lessons will not transfer.

Legs: Abhishek faced 38 balls, Sooryavanshi 18. That is 56 balls of batting and 40 balls of standing. Forty saved balls rest the middle order's legs and not the openers'.

Squad age: this series established depth in the abstract and nothing about succession in the specific. The score is 3-0. The learning is 0-0.

Takeaway

Next time India bat, watch two things.

First, when the opening wicket falls and who walks in. If it is the man who sat unused in Wellington, watch how he plays at 30/2. That is the piece of information a 13.2-over win could not deliver.

Second, the powerplay rate on a turning pitch. If it compresses to eight or nine and India still chase 199, this entire doubt collapses and I will write happily that I was wrong.

The diagram is not the truth, but it is the first honest question. Forty balls were never bowled in Wellington, and the reason is that nobody on the fielding side had the time to decide what to do with them.