Wisden's New Quiz: Six Wickets for Under 20 Runs in Tests — 24 Instances, and One Unresolved Question

Wisden has published a new quiz on the history of Test cricket, and its subject is the six-wicket haul conceded for under 20 runs. According to the page, there have been 24 such instances in Test cricket since the Second World War. Five of them saw a bowler take six wickets for fewer than ten runs, while the remaining nineteen sit in the 10-to-19 band. But the shape of the page and several of its numbers raise questions that both cricket followers and data-driven reporters should understand. The first thing to note is that this looks like an article but is, at bottom, a quiz shell. Mapping its seventeen information points back to paragraphs, only three — the first, fourth and sixth — actually carry topic material: the question, the data, the hints. Three paragraphs are cross-links to sibling quizzes from the same publisher, one provides editorial colour, two are publisher promotion and calls to action, and two restate the title or offer a technical note. In other words, only about 27 per cent of the page carries information about its stated subject. The three cross-links are interleaved between the hint paragraphs rather than clustered at the end, which is deliberate: a reader who cannot answer still gets routed to another quiz before leaving. The page's most interesting tactic is the withholding of names. Of the 24 bowlers, 21 are entirely absent and only three are partially described. That is not an extraction failure but part of the product. Identity is signalled through role, nationality and venue — enough for a knowledgeable fan to retrieve from memory, not enough for a one-step search. Two clues are laid out in detail. The first is the record for the fewest runs: a West Indies fast bowler returned figures of 6-3 against Bangladesh in 2026. The second is the most recent instance: a South African spinner took six wickets in Cape Town, in a match the hosts won by 176 runs against Australia. The page effectively gives away two of its answers, the record and the most recent, which is standard quiz design — anchor the extremes of the distribution so solvers get a foothold — but it means the hints are worth more than the prose. Then comes the point that undermines the whole count. The title and the first point say six wickets. The fifth point says six or more wickets. These define different answer sets. If the criterion is six or more, every seven-, eight- and nine-wicket spell conceded for under 20 runs is included; if it is exactly six, they are excluded. The headline figure of 24 is only meaningful under one of the two definitions, and the page never resolves which one applies. That is the single largest determinant of whether 24 is correct. The second question is the date. The fifth point sets the window as running from the Second World War to 30 October 2026. There are two readings. Either it is the quiz's data cutoff, roughly equal to publication — normal, in which case the most recent hint refers to a match in late 2026 — or it is a template artifact, an auto-generated as-of date, or a misreading of the source, in which case the cutoff is unknown and the count of 24 is unanchored. The most recent instance described — the South African spinner, Cape Town, the 176-run margin — falls outside what can be independently confirmed here. The structure is internally coherent, but coherence is not confirmation. Source quality is also a fact worth recording. Fifteen of the seventeen points carry no source at all. The only three attributed points are Wisden describing itself. There are no scorecard links to any of the 24 matches, no citation of a stats database, no named author. For a quiz page this is acceptable — the answer set is the editorial asset and withholding sourcing is part of the format — but the page is not citable as a record of the underlying statistics. Anyone reusing the facts must re-derive them from a scorecard database. The arithmetic checks out. Of the 24, five are under ten runs — the 6-3 plus four others — leaving nineteen in the 10-to-19 band. No contradiction there. Under 20 runs is unambiguous for integer bowling figures, meaning 19 or fewer. Post-War is anchored at 2026 in the first point, which is safe for men's Tests since no men's Test was played in 2026, but good practice would be to state the year rather than rely on the phrase. One technical detail matters too. The note in the tenth point — refresh the page if the quiz does not load — reveals that the quiz is an embedded third-party widget, likely an iframe. The page's core content is not in the HTML. Crawlers see only the thin wrapper, and the page's value depends on a component the publisher does not fully control. Time sensitivity flows from two places. The count of 24 is invalidated by every new sub-20 six-for, and the most-recent claim goes stale with the next one. Both have a cheap fix: a dated sentence in the fourth paragraph would make the page self-consistent at no cost. For now it hides its cutoff inside the widget. For anyone who wants to verify the claims independently, the path is clear. First resolve exactly six versus six or more, because that decides whether 24 survives at all. Then re-derive the count from a scorecard database for the stated window — for instance a Statsguru filter for men's Tests, innings bowling, wickets six or more, runs under 20, from 2026. Then confirm the 2026 West Indies 6-3 against Bangladesh against the scorecard rather than by inference, and identify the four other sub-ten spells, checking none is duplicated. Finally, confirm the Cape Town match and its date, and whether it falls inside or outside the 24. Behind all of this, the page's purpose is plain. Calling it product promotion understates the mechanism. It is an engagement asset: session depth through three sibling quizzes, repeat visits through a new-quiz cadence, shareability, and a follow-and-subscribe conversion at the eleventh paragraph, monetised by ads around the widget. The 24 names, the date and that one definition — those three things are what the page is still missing.