Abhishek Sharma's 113 off 38 Is Real; the '11 Hundreds' Record Is Not

The third T20I finished in 13.2 overs. A chase completed in 80 balls, six wickets in hand, 40 deliveries unused — the death overs were never reached. The brightest line in the scorebook reads: 113 runs, 38 balls, strike rate 297.4, century off 35 balls.

And immediately after that line, the scorebook goes quiet. No pitch character. No toss. No shape of New Zealand's attack. No boundary dimensions. No T20I career average for Abhishek Sharma. In 2026 at the Wankhede I hand-coded all 546 runs of a Ranji Trophy match between Mumbai and Tamil Nadu, because the file could not explain itself. Today the situation is inverted — the text is telling us a great deal, and the file is withholding more.

Context: match three of five, and one tweet

This was the third fixture of a five-match bilateral T20I series, after which India held an unassailable 3-0 lead. Two matches remain and neither can change the result. Which means the analytical value of matches four and five sits in rotation, workload and experimentation, not in outcomes.

The evidential core of the reporting is two things: a cluster of scoreline numbers and one social-media post from Yuvraj Singh. Yuvraj wrote that Abhishek had "taken his singles too", and added that he himself could not make a hundred off 30 or 34 balls. That joke is factually accurate — Yuvraj's T20I career contains no century; his signature T20I innings remain a 12-ball fifty and a 30-ball seventy at the 2026 World T20. That is self-awareness, not false modesty.

What the copy omits is worth listing: no venue, no pitch report, no toss, no DLS intervention, no New Zealand bowler named other than Kyle Jamieson, no T20I career average or strike rate for Abhishek, no home-away split. Without that list, every conclusion is a claim, not evidence. I will not print the claim as evidence.

Core: what the counting actually says

The most important number in this innings is not 113. It is 90.3 per cent. Twenty of the 38 balls faced produced a boundary — nine fours, eleven sixes, 52.6 per cent of deliveries. Of the 113 runs, 102 came in fours and sixes. The other 18 balls produced 11 runs, a strike rate of roughly 61.

That is why Yuvraj's joke is a data statement rather than a punchline. Strike rotation carried no functional value in this innings; singles were part of the innings, not the method behind it. A batter whose output is 90 per cent boundary-derived will carry a high-variance score distribution by construction: spectacular hundreds and cheap dismissals in near-equal measure. His dismissal is the signature of that risk — caught by Glenn Phillips at deep mid-wicket off Jamieson, the standard failure mode of a lofted hit toward the longer boundary.

Now the number that needs an audit. The report states that Abhishek moved past Virat Kohli as India's leading centurion in men's T20 cricket, the tally reaching 11. There is a classification error here, and it is not small. Kohli's T20I century count is 1. A figure of 11 cannot be a T20I count; it can only be an all-T20 aggregate — T20I plus IPL plus domestic T20. The T20I versus all-T20 distinction is a hard boundary, and both ICC and board record conventions keep those books separate. I found the number in the dataset. I could not find the person who made it.

The sample-size verdict is unambiguous: one innings proves a ceiling, not a mean. Thirty-eight balls establish that this level exists. They say nothing about how often it will arrive. Abhishek's T20I career average, his home-away split, his strike rate against pace and against spin — not one of those figures is available. So the sentence "he has arrived" is a projection right now, not an analysis.

One more thing remains unresolved at team level. Of the 113 runs in the chase, one batter made his share off 38 balls — 47.5 per cent of the innings' 80 deliveries. The rest of the target was scored by someone else, but New Zealand's total is not given in the copy, so there is no way to decide whether this was an innings won by a team or by one man. Both readings sit comfortably inside the available text. Without the full scorecard, that argument does not close.

New Zealand's "no answers" framing deserves the same scrutiny. The report asserts bowling helplessness without naming the attack, the spinners used or the plans attempted. New Zealand's T20I edge is seam movement and change of pace in helpful conditions. On a true Asian surface with short square boundaries, that edge is structurally neutralised. This is a condition effect wearing the costume of a quality gap — and reading conditions as talent is the most common error in match reporting. A metric that cannot be translated is a metric that cannot be used.

Contrarian: the weight of praise, and its motive

Yuvraj's reaction is the heaviest signal in the entire story, which is exactly why it needs the largest discount. He has a documented mentor relationship with the player and he is a public commentator. The praise is sincere; the neutrality is not established. A mentor-disciple relationship is presented as a heartwarming detail when it is, structurally, a conflict of interest. Discount it for motive, not for sincerity.

The singles line is doing more narrative work than it appears. It humanises an inhuman innings and positions the batter as complete — when the innings said the opposite: 90.3 per cent boundary runs, and a strike rate near 61 on the 18 non-boundary balls. An innings that did not run on strike rotation is being remembered for strike rotation.

The least-analysed tactical fact in the coverage is Sanju Samson dropping to number three. A senior opener batting out of position pays a real statistical cost: fewer balls faced, different entry conditions. Yuvraj dressed it as praise — "complete team man" — but for me it is the most under-read strategic signal of the match.

And the honesty of the sample. This series is being played at home, on batting-friendly surfaces, against a seam-reliant attack. That is the most favourable environment a power-hitting Indian top order can be handed. The result is real; the inference that India have solved away batting is not. This series cannot discriminate between the two.

Read matches four and five carefully. With the series settled, New Zealand's motivation and selection will both drop. Any large Abhishek score there will look larger than it is, and any low score will be punished harder than it deserves. Both are noise.

Takeaway: thresholds before the next series

We published the forecast before the first match so the season could grade us — same method here. If Abhishek's strike rate falls below 130 on the next away assignment, or if he repeats the same dismissal pattern to wide yorkers and off-spin turning in, the "arrived" framework collapses. That collapse will not be evidence of his weakness; it will be evidence of our impatience. And the day the 11 — all formats — replaces his T20I record in the copy, the question returns: who wrote that number down?

How this was counted: 113/38 = 297.4 strike rate; 9 fours + 11 sixes = 20 boundary balls (52.6%); 102/113 = 90.3% of runs from boundaries; 11 runs off 18 non-boundary balls (SR ≈ 61.1); chase completed in 80 balls with 40 unused. Every calculation here is derived from figures in the source text, not from an independent ball-by-ball log, because no such log was available to me. Pitch, toss, bowling composition and career base rates are all missing, so every conclusion in this piece is conditional on that absence.