Jansen's Two Crowns and the Ranking Clause Nobody Reads

First innings, third day. Marco Jansen begins his run-up and turns a session inside out — 5/33. In the same series, batting at No. 8, he makes 85. Ten wickets across two Tests. In the latest ICC rankings update, one name sits at No. 1 in two places: Test bowling and Test all-rounder. In the same update, Abhishek Sharma returns to the No. 1 T20I batting spot on the back of 113 off 38 balls. One update, two crowns, and a table everyone reads and whose formula nobody reads.

Across 51 years of watching this sport, rankings have always been news and never a section. That distinction matters now. When a player reaches No. 1, the headlines credit the innings everyone saw. The actual cause usually sits three paragraphs deeper, inside the definition of a weighted average that nobody quotes.

I went back to the clause that ended Eden Gardens. In March 2026, aged 37 and the only woman in the host broadcaster's research truck, I reached for the playing conditions while the crowd changed the match. From that night my method has been fixed: read the result backwards from the law, never forwards from the emotion. A ranking is a playing condition too. It has its own clause, its own sub-clause, and its own place where the gray begins.

A ranking is not a vote. It is a weighted average. Every match gives a player points, those points are set against par for that position — a opener's 40 and a No. 8's 40 do not carry the same weight — and against the strength of the opposition. Recent matches carry more weight than old ones, and the rating is an average over a rolling period from which old innings slowly drop out. The direct consequence: the ranking does not measure talent; it measures talent multiplied by opportunity. The player with more matches, and stronger opponents, walks away with more points for the same performance. That gap is not evidence of a conspiracy, it is the plain grammar of the formula — and that grammar decides whose name goes in the headline.

Now the clause that built this update's biggest crown. The all-rounder ranking is not built by adding batting and bowling ratings. It is built by multiplying them — batting rating times bowling rating, divided by a thousand. That multiplication is the whole game. In addition, two weak numbers still produce a respectable number; in multiplication, one weak column brings the house down. So the all-rounder list rewards players whose two columns rise together and punishes those leaning on a single skill.

Follow the multiplier: every ranking has a hidden one. In Jansen's case it arrives from batting at No. 8. Par for No. 8 in Test cricket is low — which means 85 there carries the same points as 130 or 140 at the top of the order. And because the same player is taking 5/33 in the other innings, the multiplicative formula lifts both columns in the same week. A fast bowler who bats at eight will always move ahead of a fast bowler who bats at six in the all-rounder table, even when the batting averages say otherwise. Nobody did him a favour here; the arithmetic did its job.

Jansen's double No. 1 matters because it is structure, not accident. Ten wickets in two Tests is a small sample, and on a small sample a bowling rating climbs fast and can fall just as fast. Six weeks with the Laws taught me where the gray begins: exactly where the rule states the minimum number of matches required to be ranked, and declines to say who judges the quality of those matches. A player who takes a crown on three matches can lose it on three matches. I am not saying Jansen's crown is counterfeit — 5/33 and 85 at No. 8 are real in any formula. I am saying the crown's durability is decided by the width of its base, not the height of its peak.

The second crown is a different species. Abhishek Sharma's 113 came off 38 balls — the T20 format where a single innings can move an entire ranking, because the T20 rating period is short and the innings count is small. Here the weighted average shows its other face: where a Test session takes months to digest, a T20 evening is enough. Put his three scores in the series side by side — 29, 27 and 113 — and the picture clears. The average is 56.3; the variance is enormous. The ranking caught the evening, not the month.

And the context sentence nobody quotes: Ishan Kishan's injury. A top-order slot opened, Abhishek got the chance, and he settled the chance in 38 balls. Opportunity is never written into a cricket ranking table, but it stands behind every one of them. Whoever did not get the chance is not in the table — and that gap belongs to selection policy, not to the ranking.

The headline said Abhishek 'took back the crown.' The word is fine; the evidence is incomplete. The source material confirms that Ishan overtook him in July; it does not say how long Abhishek's previous stint lasted, how high it went, or which week it ended. Without that history, 'back' is a linguistic convenience, not a fact. That is the oldest disease of my trade — an unread clause replaced by a good idiom.

Look at the Test batting side. Temba Bavuma's 179 is the innings that set the direction of South Africa's series and pulled him up the table. Harry Brook, Scott Boland and Simon Harmer moving up shows that recent Test activity in England and Australia has reached the table. Boland and Harmer are names that get few headlines and plenty of rating, because their work is wickets, not narrative. The margin is not the scandal; the margin is the evidence.

On the ODI side, Shaheen Shah Afridi and Azmatullah Omarzai rising connects to the tri-series in Pakistan and the UAE. ODI rankings move slowest of the three formats, because matches are fewer and their weight sits in the period for longer. One unpleasant consequence: the ODI table often shows form as it was three months ago. That is the reader's trap — three tables printed together, looking identical, running on different clocks.

This is where reporting of this kind is genuinely weak — the format merge. One update carries a Test bowler, a T20 batter and an ODI all-rounder at once, and the reader silently compares them. What looked like chaos had a protocol underneath it; the protocol simply sat in three different rooms and nobody joined the doors.

Now the reversal. The accepted story is: performance happened, ranking moved, headline followed. That story is not wrong, it is being read backwards. A ranking is not a reward for performance, it is the ledger of performance — and a ledger is always written after the transactions. Jansen's crown did not come from that 5/33; it came from the sum of every match already recorded against his name in the period, and 5/33 was the last entry in the sum. The difference is that the reader sees the last entry and not the sum.

The second thing the accepted story omits: a ranking measures consistency, not peaks. A player who makes 45 every week will sit above one who makes 180 once and 12 ten times. Cricket's beauty lives in the peak; the ranking's arithmetic lives in the consistency. That is why the table often keeps names the crowd does not call great near the top, and names with one unforgettable innings lower down. That is definition, not anomaly.

And what is not yet known must be written down: the date of this update, the boundaries of the rating period, and the length of Abhishek's previous No. 1 stint are all absent from the source material. Match figures come from scorecards, but without a date they cannot be verified. If a new table arrives tomorrow with Jansen at No. 3, this piece ages itself — and that is the fate of all rankings reporting.

What is ahead? The third Test is ongoing and the top bowling spots could change within weeks — that projection belongs to the source material and should stay a projection. What I would add: print the formula next to the table. Two lines — how the weighted average is built, and why the all-rounder rating is multiplicative. The reader would then understand why 85 at No. 8 is not worth less than 130 at the top. A sport that learned to explain DRS in ninety seconds can explain its own rankings in two lines.