Not the 311*, the 21 All Out Is the Real Story: A Spreadsheet Audit of Delhi School Cricket's Triple Century

Two numbers sit next to each other in my spreadsheet: 311 and 21. The first belongs to Aaryan Sharma — 311 not out off 93 balls, 27 fours, 30 sixes, a strike rate of 334.4. The second belongs to another innings in the same school knockout tournament, where a side was bowled out for 21 in 6.2 overs. A day before Aaryan's innings, in the same competition, Tanmay Chaudhary made 278 not out off 77 and his team finished on 413/0 in 20 overs.

I am 61, I host a cricket podcast from Delhi, and I have been getting up and sitting down with scorecards since the 1980s. I do not find the 311 implausible. I find it entirely credible, and that is the problem. A true thing can still mislead you if you refuse to read the scorecard around it.

Context: what was said, and what was left out

Wisden published a report on 26 October 2026 with "ultra rare 20-over triple hundred" in the headline. The entire structure of the piece rests on two embedded tweets and one image credit. The most granular figures — the 334 strike rate, the fours-and-sixes split — come from a fan account, and the scorecard image is credited to CricHeroes, a grassroots scoring app. No organiser, coach or selector is quoted anywhere in it.

The mainstream reading is simple: a 16-year-old, a Delhi school tournament, three hundred in 20 overs. It looks impossible, therefore it is news. A historical anchor was attached to that reading — Mohit Ahlawat's 300 in a Delhi local T20 game in February 2026, making this feat the first of its kind in "nine years". I had called that 2026 innings the first signal of the coming decade on my podcast. I was wrong on that call for eleven months, which is exactly why I do not read this number the same way now.

I should state my position plainly: I am not attached to any board, franchise or academy, and I built my own table before forming a view. The first column of that table is always the one absent from the report — who was bowling.

Core: five things the scorecard tells us, and one it does not

First, the part that genuinely favours Aaryan. The arithmetic holds. 27 fours is 108, 30 sixes is 180, so 288 runs in boundaries. Subtract that from 311 and you get 23 runs off 36 non-boundary balls. The numbers reconcile; this is not a garbled viral figure. Scoring 92.6% of your runs in boundaries, hitting 57 of 93 deliveries to the rope, is evidence of a real hitting ceiling and, at 16, of unusual physical maturity.

Now the part the report did not write. The team total was 389/2. The opening stand produced 219 in 12.3 overs, with Rijak Kohli contributing 43 off 25. The third-wicket stand added 166 in the last seven overs, during which Sahib Singh scored 2. None of that is a criticism; in a mismatch it is the rational way to bat. But it has a consequence: the innings contains no evidence of partnership batting, of strike rotation under pressure, or of turning ones into twos. On non-boundary deliveries his rate was 0.64 runs per ball — a number produced by the same innings that produced 30 sixes.

Third, and this is the spine of the whole piece: scoring in this tournament was not normal, it was systemic. Within 24 hours of the same knockout stage came 311 not out, 278 not out and a 413/0 team total, while a parallel fixture ended with a side bowled out for 21 in 6.2 overs — a 392-run margin. When winning margins in one competition reach 392, the margin carries no information at all. It only tells you how widely the bowling and fielding standards are dispersed.

There is a small arithmetic proof nobody picked up. In that 413/0 innings, Tanmay Chaudhary faced 77 balls for 278 not out and Shivesh Kapoor faced 47 for 102 not out — 124 deliveries in an innings that contains only 120 legal balls. That is impossible without wides and no-balls. The same inference applies to Aaryan's match: 311 plus 43 plus 2 is 356, leaving roughly 33 runs in a 389 total to be accounted for by the dismissed batter and extras. The most plausible source is loose bowling — wides and no-balls. The attack was not disciplined.

Fourth, the phase profile. In professional T20, scoring rate drops through overs 7 to 15 as fields spread and spin arrives. Here the rate barely moved: 219 in the first 12.3 overs, 166 in the last seven. There is no middle-overs brake. Put simply, there was no bowling good enough to apply one — and if no brake was applied, you cannot claim he broke a plan. You can only claim no plan existed.

Fifth, the most important comparison in the story: the same batter, one level up. Aaryan is a Delhi U19 squad member who has played the Vinoo Mankad Trophy — 124 runs in three innings, best 77 not out, batting in the middle order. At school he opens; at representative level he bats in the middle. That is the pair any evaluation should look at first, and it was absent from the Wisden report entirely. 311 not out is not a measurement, it is an event. The measurement is what happens when bowling quality rises two or three tiers. The current answer: competent, not exceptional.

And sixth, a verification point rather than a cricket point. The report carries two different names for one competition — "Schools Total T20 League" in the text, "Delhi Schools T20 League" in the quoted tweet. That is minor, but it signals the piece was assembled from secondary material rather than an official fixture list. No central body maintains authoritative records for Indian school cricket, so the "ultra rare record" claim rests on an app's scorecard and social amplification. It is not false. It is incomplete, and it will stay incomplete until age and enrolment documentation are publicly verified.

The most interesting commercial fact here is that the significant institution is not the tournament but CricHeroes. A ball-by-ball digital scorecard is what carried a Delhi school knockout innings into a global cricket publication within days. That is a genuinely large structural shift for Indian grassroots cricket, and its scouting value is far greater than the innings itself. Meanwhile, the final paragraph of the Wisden piece explains why it exists — a follow call-to-action listing live scores, stats, quizzes and match odds. That is aggregation, not reporting, and its business model is volume. More records, more shares.

Contrarian: where I could be wrong

My table cannot measure what is in a 16-year-old's wrists. Hitting 57 of 93 deliveries to the boundary requires bat speed and hand-eye coordination that a model does not capture. I have watched plenty of innings from the stands that my numbers failed to explain, and this may be one of them. Even against weak bowling, 30 sixes require seeing the ball properly — and schoolboys usually cannot.

Second, I may be lumping an entire tournament into one explanation. It is possible that 389/2 and 413/0 came about for different reasons, and assuming a small ground without having seen the ground is a decision made on no data. The report gives no pitch, no boundary dimensions, no ground size. My data here is blank and I should say so.

Third, and most importantly: I may be repeating the Ahlawat error in reverse. Then I endorsed too quickly; now I am dismissing too quickly. Both are haste. The difference is only that dismissal looks like wisdom.

Takeaway: two predictions, on the record

This story will return within months — when Aaryan is profiled, the lead fact will be the 311, not the 124 Vinoo Mankad runs. Prediction one: if he gets 8 or more innings in BCCI age-group cricket over the next 18 months, his boundary share of runs will fall below 65% from 92.6%, while his non-boundary scoring rate rises above 0.64. Prediction two: no board or organiser will formally ratify this innings; it will live in an app's scorecard, not a record book. If either fails, I will print the miss in this same column. The question is not whether a 16-year-old can make 311. It is what we will see on the day he faces a real attack, not one that gets bowled out for 21. This scorecard does not answer that.