Test Hundreds From No.9 Or Below: Broad, Abul Hasan, and the Clause the Scorecard Never Prints

10 July 2026, Trent Bridge. Ashton Agar walked out at No.11 on debut and made 98 before he was dismissed. In the thirteen years since, that innings has been called a hundred at least as often as it has been called what it was. The highest Test score by a No.11 remains 98. Not a century. The new Wisden Cricket Quiz question is built inside that fog: which batters have made Test hundreds from No.9 or below?

The first thing that catches the eye is not the question but its timer — five minutes. A five-minute timer is not decoration; it is a signal that the answer set is compact. Across a century and a half of Test cricket, this population sits in the tens, not the hundreds. Solving the quiz needs memory. Measuring the size of that memory needs a walk back to the scorecard.

Context: whose rulebook, whose authority

The first task is jurisdiction. Whose book is this number coming from? The structure of the sport comes from the MCC's Laws of Cricket — the 2026 Code, amended in 2026 and 2026. Law 1.1 states that a team consists of eleven players, and under Law 13 an innings closes when ten wickets have fallen. The eleventh batter is therefore always the man whose partners run out, not him. That structure is what creates the space in which a No.9, 10 or 11 can play a long innings.

And one point needs settling immediately: the batting order is convention, not law. No clause requires a specialist at No.1 or a bowler at No.11. Captain and coach decide who walks in when. 'No.9 or below' is therefore not a cricketing category; it is an administrative one — and that is the foundation the entire quiz stands on.

The second jurisdiction is editorial. Wisden Cricketers' Almanack has been published since 1864, and this quiz borrows its credibility from that masthead. But the page carries no methodology note, no source list, no update date. The answer key is editorially curated rather than query-generated, which means it is exposed to omission error.

Core: three kinds of hundred, and one bad sum

The real analysis starts here. Hundreds from No.9 or below come in three distinct kinds, and dropping all three into one bag is the central error.

First kind — the genuine tail-ender. A single career hundred that never returned. Stuart Broad's 169 at Lord's in 2026 belongs here: batting at No.9, with England 102 for 7, and no further Test hundred afterwards. The innings is evidence of Broad's ability; it is not evidence of anything predictive.

Second kind — the all-rounder batting a spot or two too low. Abul Hasan's 113 at Khulna on 21 November 2026 inverts the picture. He came in at No.10 on Test debut and made a hundred — the first player to score a century on Test debut from No.10 or lower. That was not a miracle from a tail-ender; it was a signal that the selection structure had him in the wrong slot. This is the only archetype with predictive content, because it often ends in promotion.

Third kind — the specialist dropped down by injury or illness. This is the most analytically important category, because it undermines the exercise. If a No.5 makes a hundred after a retired-hurt reshuffle pushed him to No.9, the scorecard records a No.9 hundred. It was not. The nightwatchman does the same thing in reverse: temporarily up, then back to his place. The gap between position-in-the-innings and career position moves the entire answer key.

When I work through a quiz like this, I use the method I use on a review: I go back to the scorecard to see what the compiler actually saw. Which innings, which position in that innings, and on what basis that position was assigned. Until that is stated, a list is a list — not data.

Then the largest structural problem: survivorship bias. A list of No.9 hundreds is, by construction, a list of outliers. Inferring anything about tail-end batting quality in general from it is a base-rate error. The correct benchmark is the denominator nobody counted — the tens of thousands of No.9, 10 and 11 innings that ended in single figures. Broad's 169 and Agar's 98 are both extraordinary. Being extraordinary is their entire identity.

The format gate matters too. This question is Test-exclusive, because only Test cricket reliably gives a No.9 one hundred and fifty-plus balls. A T20 No.9 gets sixty to seventy balls at most and must hold a strike rate above 140 throughout — a combination the game has never produced. ODI sits between the two, but lower-order hundreds there are conventionally a No.7-8 phenomenon, not No.9-11.

The third structural point is about supply. Test-playing nations differ by up to an order of magnitude in matches played — England and Australia hold the longest and densest histories, newer nations far fewer. Since No.9 hundreds are a rare-event category, their expected distribution tilts heavily toward the longest-established nations. That is exposure, not skill. If such hundreds clustered unusually in a short-history nation's record, that would be the genuinely interesting question — and the one the quiz format cannot answer.

One last thing the quiz does not ask: why the line at No.8 and No.9? Jason Holder's 202 not out at Bridgetown in January 2026 came at No.8 — one slot above, and therefore outside the question. A machine did not draw that line. An editor did.

Contrarian: this is not an oddity, it is a design feature

In Wisden's framing this is one of cricket's oddities. Editorially that is fine; analytically it is wrong. Nothing odd is happening. The rule that lets every player bat is a design feature with no analogue in football, rugby or basketball, where substitutions and fixed positions apply. In cricket all eleven of the XI are inside the game, and being on the field is itself the batting right.

The consequence is that every statistic keyed to batting position is soft data. It is not produced by a rule but by a captain's decision on the day. Any model using batting position as a feature to measure tail-end ability must treat that variable as endogenous — set by team decisions, not by talent.

And if you look at the page in its real economic role, the picture sharpens. The five-minute timer, the instruction to refresh the page if the quiz does not load — this is not bespoke editorial software but a lightweight third-party embed. And four links to sibling quizzes inside the piece — Sri Lanka's leading Test run-scorer, the highest Test innings for every team, the first hundred of the Border-Gavaskar Trophy, the youngest wicket-taker for each team — are the actual work: internal traffic routing. The page's economic function is not to inform the reader but to deliver him to the next quiz.

No player is being valued here, so there is no sporting-value versus commercial-value conflict of the IPL kind. The real separation is different: this article's information value to a serious reader is close to zero, while its engagement value to the publisher is high. Who pays? The reader who treats the answer key as data and assumes a No.9 hundred is a measured category — when it is an editorial decision with no timestamp and no audit trail printed anywhere.

Takeaway

Before I judge the call, I want to know who trained the eye. The next time a list of 'highest for every team' or 'youngest ever' appears, ask one question: what were the criteria, and whose position in which innings was counted? The clause was on page nine, and it decided the season — here, page nine is the methodology note the answer key never got. If Wisden adds it, the quiz stops being a diversion and becomes a doorway into rules literacy: readers will ask why the eleventh man has the right to bat at all, and why an innings ends at ten wickets. Until then, Agar's 98 stays what it is. Not a hundred.