Test Hundreds From No.9 Or Below: Cricket's Rarest Innings, and the Lie of the Batting Order

Trent Bridge, July 10, 2026. Australia were 117 for 9 in the first Ashes Test, and out walked a nineteen-year-old left-arm spinner at No.11 — Ashton Agar. He made 98. Home Tests in England start at 11 a.m. BST, which is exactly 3:30 on a Chennai clock. I spent that afternoon with the scorecard open on a laptop, unable to square one thing: his name was printed at the bottom of the card, and his score was the highest of the day.

Ninety-eight. Two runs short of a hundred. Those two runs are the most honest part of this story, because cricket's memory slowly rounds 98 up to a century. People say Agar scored a hundred on debut. He did not.

A Wisden quiz doing the rounds asks the question properly: which batters have made a Test hundred from No.9 or below? A five-minute timer, an embedded widget, four links to sibling quizzes. I went looking for tactics and found a taxonomy wearing a quiz.

Context

The question can only exist in Test cricket, and the reason sits inside the Laws. An innings runs until ten wickets fall, which leaves the eleventh batter unbeaten — and nothing in the book says the man at No.11 has to be a bowler. — Root: ten wickets.

In T20, a No.9 has sixty to seventy balls at the absolute outside and needs a strike rate above 140 to make them count; that combination is essentially unobserved. ODI sits between the two, and its lower-order hundreds belong mostly to No.7 and No.8. A hundred from No.9 or below needs 150-plus balls, which means the format with no clock on it.

The quiz's five-minute limit is itself a data point: the answer set is compact. Low tens of names across a century and a half of men's Test cricket, plausibly. And because the quiz includes No.10 and No.11, it is asking for the rarest category in the sport. The highest score by a No.11 remains Agar's 98 — a near-miss that gets misremembered as the thing it missed.

Four more quizzes sit on the same page: most Test runs for Sri Lanka, highest innings score for every team, the first hundred of the Border-Gavaskar Trophy, youngest wicket-taker for each team. Plus a technical line — refresh the page if it doesn't load. The page's job is not to report; it is to route traffic inward. A five-minute timer, a third-party widget, four outbound links: this is the layer of publishing nobody writes features about and everything runs on. Wisden has printed the Almanack since 1864, and that masthead is doing the sourcing work here.

Core

What the quiz actually supplies is a classification. Hundreds from No.9 or below come in three kinds, and their predictive value is not the same.

The first is the genuine tail-ender: a single career spike that never repeats. Agar is the cleanest case. Ninety-eight on debut, then five Tests and 130 runs in total. The innings told us nothing about what came after it.

The second is a real all-rounder batting a slot or two too low. Here the hundred is evidence of a selection error rather than a spike in form, and this is the only category with predictive content, because promotion up the order is a live possibility.

The third is a specialist dropped down the card by injury or illness. Here the hundred measures the batting order, not the player. Jason Gillespie made 201 in Chittagong in 2026 — at No.3, as a nightwatchman. A fast bowler whose position on the card said nothing about what he was.

That is where the answer key starts to shake. What does No.9 or below mean — position in that innings, or the player's career-typical slot? Where does a batter who came in at 9 in the first innings and 6 in the second sit? What about a nightwatchman, or a man who walked out after a retired-hurt? A list published without stated criteria is open to legitimate dispute, and the dispute is editorial, not cricketing.

The bigger problem is arithmetic. A dataset of No.9 hundreds is a dataset of outliers by construction. The benchmark nobody publishes is the denominator: the tens of thousands of innings in which Nos. 9, 10 and 11 were back in the pavilion for single figures. Drawing a conclusion about lower-order batting quality without that denominator is a base-rate error in plain sight. One hundred is lifted out of a hundred failed innings, and we never see the ninety-nine.

Then there is exposure. Test-playing nations differ by an order of magnitude in matches played; England and Australia have the longest and densest histories. A rare event shows up more often where there are more attempts. That is exposure, not skill. The interesting version of the question runs the other way: a short-history nation with an unusual concentration of these innings would be telling us something real about squad construction — a long tail with genuine all-rounders, or a top order that collapses often enough to need rescuing. The quiz cannot ask that.

The batting order is cricket's meta, not its patch notes — a convention everyone has agreed to treat as a rule. Nothing in the Laws requires a specialist at No.1. Which is why batting position is soft data: it records a captain's or coach's decision on the day, not a rule-defined role. Any model that uses position as an input should treat it as endogenous.

And the labour reading. A No.9 is a man whose price is set by his bowling, not his batting — the domestic cricketer on a match fee, outside the contract list. His hundred is the most shared innings he will ever play and the least paid. When it is 98 instead, the memory is just as sharp and the ledger does not move at all.

Contrarian

Let the Wisden case stand at full height first. This is cheap content that never expires and holds readers across several countries at once. It also functions as a rules-literacy door: a reader ends up asking why the eleventh man is left unbeaten, why ten wickets end an innings. That is real, if modest, educational value.

The failure is that no methodology travels with the quiz — no source list, no update date. The answer key is therefore editorial curation rather than a database query, and omission error is a live risk. The framing has a problem too: the piece calls the all-XI-can-bat rule an oddity of cricket. It is not an oddity. It is a design feature that we stopped noticing because the convention stacked on top of it became so rigid that the rule itself went invisible.

Takeaway

Next time a No.9 walks out in the 41st over, read the second column of the scorecard — position, career average, and the decision that put him there that morning. The question is not who made the hundreds. It is why we keep that list and not the thousands of single-figure innings around it. Ask Wisden for the criteria behind the answer key. The rest of the counting we can do ourselves; 3:30 is already a habit.