Wellington's 118/0: A 199 Chase in 13.2 Overs, and the Forty Balls the Ledger Never Recorded

The scoreboard at Wellington read 118 for 0 after six overs. The target was 199. India needed 81 runs from 84 balls with all ten wickets in hand. Before the first ball, the required rate was 9.95 an over; at the end of the powerplay it was 5.79. That is the first number I enter in fifty years of ledgers, because no side loses from a required rate of 5.79 — the number only tells you the over in which a contest became an exhibition.

The match ended in 13.2 overs. Forty balls went unused. In a format where the death overs decide more games than anything else, the final third of the innings never began. The scoreboard said 199 for 4. My ledger says forty balls were never bowled and nobody accounted for them.

This was the third T20I at Wellington. India won by six wickets and took the series 3-0. The figures I use here come from the Times of India match report, which carries no official scorecard link; I have therefore filed the record claim under pending verification. That is habit, not suspicion. In 2026 at Eden Gardens I bowled 42 overs for 3 for 94 and lost by an innings, and not one number from that match went into my copy without being reconciled with my spiral notebook. The ledger never lies; it only waits for the next reader.

What is clear: an opening stand of 133 at 18.13 an over; Abhishek Sharma 113 off 38 balls; Vaibhav Sooryavanshi 45 off 18; 118 for 0 in the powerplay; and a chase completed in 13.2 overs with 40 balls to spare.

What the record actually is matters. It is the highest run rate for a 100-plus opening partnership in men's T20Is — not the highest partnership, not the highest team total, not the fastest hundred. It is a rate record, and rate records have a shape. I will come back to that shape, because it is the most interesting thing about the innings.

T20 cricket is built in three phases. In the first six overs only two fielders can stand outside the circle, the ball is new, and the captain's only lever is who bowls. A score of 118 for 0 means the fielding side opened every drawer in the first phase and found nothing that worked. The middle and death phases never arrived, so nothing in this match tells us anything about either. Read that sentence twice: everything that follows stands inside that limit.

The report gives no pitch, toss, weather or dew information, so I will not claim the surface was made for batting. I will only say that a 199 chase finished in thirteen overs is never the product of one cause, and only one of those causes is on my page.

3.02 runs per ball — the geometry of the powerplay

133 runs, roughly 44 balls, 18.13 an over. Convert it: 3.02 runs per delivery. An over of six balls at that rate produces eighteen. Put yourself in the bowler's shoes. If he takes a wicket in that over he is at par; if he does not, he has lost more ground in six balls than he lost all season. Nobody took a wicket in that powerplay.

I read matches as geometry, not as weather. In that Eden Gardens game in 2026 I charted 318 deliveries on a hand-drawn field, marking where each ball was hit. Bombay's No. 4 made 71 of his 96 square of the wicket. In the second innings I moved the sweeper twelve yards finer and had him caught at deep point for 9. From that day my copy went to the desk with a field map attached, because a field is an argument, not decoration.

In the powerplay the captain has length, angle, change of pace and field. He has no sweeper. If the batter hits over the infield, the ball that was worth one becomes four and the ball that was worth four becomes six. A rate of 3.02 runs per ball means the men inside the ring were ornamental that evening.

The dot ball is the real currency of this format. Every bowling plan — who bowls the seventh over, when the spinner comes on, when the yorker is used — rests on a dot-ball percentage. In an innings where dots go to near zero, the whole structure becomes paper. The captain's sheet has no dot-ball column, so he sees the shortage on the grass and not on the page.

A hundred off 38 balls and the missing column

Abhishek Sharma: 113 off 38. That is 2.97 runs per ball, and 56 per cent of the target from one bat with eighteen overs still available.

Take that innings out of the books. The rest made 86 off 42 balls — 2.05 per ball, a rate of 12.3 an over. Still high, but not the same innings. Remove Sooryavanshi's 45 off 18 as well and the remaining four wickets produced 41 off 24 balls, 1.71 per ball. The shape of the innings is now visible: one man at 2.97, the rest at 2.05, the lower order at 1.71.

For any batter, a strike rate of 297 means he has decided, somewhere in his head, that a single is a failure. Every bowling plan is built on the assumption that the batter will have to play out a few balls. When that assumption breaks, the plan does not collapse; it becomes irrelevant.

2 April 2026, Wankhede. I spent that chase watching the dressing-room corridor rather than the ball. Dhoni walked out at 114 for 3 in the 22nd over, ahead of an in-form Yuvraj, and made 91 not out off 79. The promotion was not instinct; it was a pre-agreed response to Sri Lanka's two off-spinners turning the ball into the right-hander's pads. After that night I stopped writing that someone backed his instinct and started asking who decided, when, and against which bowler.

The same question applies here. Who decided the match would be finished inside the powerplay? Once India needed only 5.79 an over, taking risk was arithmetically pointless. So the stand broke at 133 and the target still fell in thirteen overs. A side that wins with forty balls unused took no risk in those forty balls. That is a credit in the ledger. It is also a hole in it.

A teenage opener and the satellite pipeline

Sooryavanshi: 45 off 18, 2.5 runs per ball. A teenager opening in a T20I with a strike rate that leaves him unafraid of being left behind.

I do not read this as a talent being discovered. I read it as a development structure. Big clubs and big franchises have learned to bypass their own local base and lift ready-made talent from smaller units as assets. In cricket the translation is a change of conveyor belts: one belt produces batters who can hit from ball one, the other produced batters who could bat forty overs. The first product looks faster. The second product lasts.

The old ledger is not nostalgia; it is a stress test for new numbers. 2026 Ranji quarterfinal, Bengal versus Railways. I was coach, 45 years old, and by 1 a.m. I had charted Railways' left-arm spinner across three seasons: 240 deliveries, 62 per cent of them on a fourth-stump line to right-handers. Our No. 6 averaged 18 against that angle. At 1 a.m. I moved a nineteen-year-old to No. 3 and dropped the senior pro to six. The teenager made 64 off 121 and Bengal won by three wickets. I never explained it to the senior pro. A batting order revised at 1 a.m. is a theory with consequences, and the theory must argue with the scoreboard, not with the man.

That 240-delivery tape still teaches, but in reverse. In 2026 the fourth-stump line worked because the batter had to score off it; the dot ball was expensive. Today the dot ball is cheap for the bowler who bowls that line, because the batter is not obliged to play. He can wait, or use the angle and hit over cover. The angle has not died. The price of the dot ball has changed, and a map whose prices have changed is no longer the same map.

What the captain actually had

The report does not name the bowlers used in the powerplay, so I will not invent them. At the level of structure, one thing can be said.

A captain in the powerplay needs a wicket-taking ball. If his stock ball is not a wicket-taker, he must bowl a wicket-taking ball and accept the risk, and against a batter going at 2.97 per ball the punishment is immediate. The mathematics is simple: at that rate a bowler has about two balls of error per over. A plan that runs on four good balls and two bad ones was a losing plan that evening.

The only fielding route left is to push the ring back, concede the single, and change the strike. But changing the strike helps only if the other batter is under pressure. Here both ends were striking above 250. When both ends are open, strike rotation stops being the fielding side's tool and becomes its punishment.

Forty balls never bowled — the private ledger

I keep two ledgers: one for runs, one for reasons. The runs ledger says 199 for 4 in thirteen overs and two balls, series 3-0. The reasons ledger says something else.

Eighty balls were bowled in the innings. Abhishek faced 38, Sooryavanshi 18. The remaining 24 were shared among four wickets, and they produced 41 runs. India's middle order spent 24 balls in the middle in the entire match. Twenty-four balls is not a file, for any tournament.

Here is the second face of that innings, and my central point. Chasing a target in thirteen overs is a skill, and the same skill becomes your biggest risk the next time, because a knockout will not hand you 118 for 0 in the powerplay. On the day the top order is 30 for 2 in the tenth over, the man at No. 4 will be asked whether he can bat twenty overs, and the answer will come from a recent record that consists of 24 balls.

At 1 a.m. the batting order becomes a confession. Someone in the next selection meeting will have to name the No. 4, with 24 balls as evidence. That is not a failure of a team that keeps winning. It is the price of the method that keeps winning.

The shape of the record: rate records reward early dismissal

Back to the rate record. A run-rate record in cricket is an odd object, because it is partly built by the speed at which the partnership ends. When the stand broke at 133, its rate froze at its peak. Had the same pair batted to 180 with the same aggression, they would have logged a smaller number; had they broken at 110, a larger one. The record therefore measures, in part, when the partnership ended, not only how good it was.

None of that makes 133 in 44 balls small. Scoring three runs a ball is rare and should be called rare. It means, rather, that a more precise measure exists — runs per ball relative to match par, adjusted for phase — and that measure never becomes a headline. Headlines need records, and records do not carry their conditions with them.

Second, this was the third match of a series already decided. Rotation, intensity and experimentation all shift in such games. I am not shrinking the 118 for 0; I am saying it must be filed with its context, or it will be compared wrongly to a number from another series next month.

And for those who underrate the television box: the live tracer and the analyst in it can map a bowler's lengths within two overs, and I cannot. My chart is post-hoc, slower, and behind the box at pattern-calling. The only thing my chart has that the box does not is its assumptions, written down. If they are disproved, I will turn them over myself.

What to check next match

One: does this pair meet spin inside the powerplay, and does it keep that rate? Hitting from ball one against a ball that hangs is a different trade.

Two: does the middle order get twenty overs. If the next three chases also finish in thirteen or fourteen overs, the No. 4 file stays empty, and the tournament will ask its question from that empty file.

Three: does the record survive the archive. I will re-check it against CricSultan's data indices, because in T20 cricket records age quickly and claims age faster.

Chasing 199 in thirteen overs is one skill. Defending 180 across twenty is another. This series displayed the first; the next one will demand the second, and the answer will have to come from the 24 balls nobody opened on this particular evening. The ledger never lies; it only waits for the next reader.