Jansen's Two Crowns and the Missing Period in the Ranking Table

The third Test had not finished, and the table had already moved. Marco Jansen's name sat at the top of two ICC lists — Test bowlers and Test allrounders — on the back of 10 wickets in two Tests, a 5/33, and 85 runs batting at number eight. The series was still live. The update had been filed anyway.

That is the first discrepancy a reader should see. A ranking does not wait for a series to end; it runs on its own clock. A report written off the series clock and a table built on the rolling-period clock are two different documents, and closing the gap between them is the reporter's job, not the reader's.

I have been reading scorecards for 26 years, and nine of them have been spent writing the thing nobody else wants to write: the decision. Tribunals, DRS, playing conditions, eligibility, sanction ranges. They share one quality. The decision arrives loudly; the reasoning is buried in paragraph nine. An ICC ranking is a decision too, except the judge is a formula, and nobody has seen the formula's face.

It is easy to read this update as a list of who went up. The table is not measuring form. It is measuring a rolling average, in which the most recent two years of performance carry full weight and the two years before that carry half. Which means the table records not only what was played but what was not. A player out injured does not lose rating points to a bad shot; he loses them to the calendar.

In professional cricket that number is not decorative. Central contract tiers, selection arguments, league valuations — all three quote it. I am not claiming any board's contract structure is set by rankings; I have never found a document that says so. That is inference, not evidence, and the two must be kept apart. What I can say is that whenever a player's contract category has changed, the ranking was cited in the argument inside the room.

In 2026, live-blogging a PSL spot-fixing tribunal from the corridor outside in Karachi, I learned something the scorecard never teaches: one case runs on two clocks. The charge sheet's clock and the sanction's clock. The corridor has always told me more than the press conference did, because the corridor carries what the statement leaves out. Rankings work the same way. The series clock is visible; the period clock decides.

What the table is, and what the decision is

Start with the thing ranking roundups mention least and readers most need: rating and ranking are not the same object. A rating is a number — points earned divided by matches counted. A ranking is a queue position. Being number one does not establish a margin over number two; it establishes that the average is currently the highest. One innings or one spell can move the number quickly, but the queue only shifts when others move too.

The three formats sit in three separate rooms, each with its own window, minimum qualification and weighting. Batting and bowling tables exclude a player until a minimum number of innings or wickets is reached. The allrounder table is the least explained piece of the apparatus — it combines batting and bowling value, and it has never been documented in public with the care given to the batting table. A mechanism that is never properly explained is easy to skip in copy with a line about a ranking changing. That is exactly where reader trust is built or lost.

On the Karachi desk the Urdu wire and the English feed carried the same numbers, and both were missing the same thing: the period those rankings were built for. An update that does not state its date, or the matches counted, is not a record. It is weather. Weather can be reported, but it should not be presented as a file.

Jansen: two crowns and a small sample

Jansen is the cleanest case and the most misleading. Ten wickets in two Tests is excellent. It is not evidence of being the best bowler in the world; it is evidence of holding the highest rating this week. The formula weighs the price of wickets, not merely their count. A five-for at 13 an over moves an average harder than three wickets at 30, because points per wicket reward cheapness. Two bowlers in the same match can end up in different universes.

The ruling read clean until I compared it with the previous table. The update does not say how close the incumbent's number was to Jansen's. That is where readers are misled — number one gets read as best, when it means highest average this week. The top of the Test bowling list is crowded enough — Bumrah, Jadeja, Starc, Henry, Robinson all breathing in that band — that two good matches lift a bowler to the top and the next two put him fourth. The single opinion in the source material says exactly this, and it is the most honest line in the brief: the top two bowling spots can move quickly.

Jansen's allrounder crown should be read even more against the grain. It is less a statement about his greatness than about the scarcity of genuine Test allrounders. The population of players who bowl 135-plus and bat at eight is small enough that the list is short, and a short list moves violently on one innings and one spell. An 85 from number eight is not just 85 runs; on that table it is a large share of the index.

The sample question remains. Two Tests is not the unit on which a bowler's standing should rest. At the 2026 World Cup I timed every video review across 64 matches with a stopwatch, and learned something that applies directly here: when a decision has no stated window, you are not watching the decision, you are watching its first frame. Ten wickets in two Tests is a very good first frame. It is not the film, and presenting it as the film is the reporting error.

Abhishek Sharma and the power of absence

The second story is more interesting because it includes a hero and an absentee. Abhishek Sharma returned to number one among T20I batters with 113 off 38 balls. According to the source material, Ishan Kishan had overtaken him in July and is now out injured. Three figures sit in sequence — 29, 27, 113 — and the sequence tells the whole story.

The T20I batting table is the ICC's most volatile list, and the reason is structural. In Tests, the window and the match count slow the weight down. In T20Is, each innings is a unit and recent innings move points fast. A 113 off 38 balls can turn an average in a night. That does not make the innings small; it is large in any format. It means the table is not praising the innings, it is dissolving it into an equation whose denominator is innings, not time.

Now the part the roundup had no room for. Kishan leaving the top is not a performance event; it is an attendance event. An injured player cannot defend a rating. As older innings age through the window, the average falls without a single false shot. This is the least understood and most decisive feature of the system: the calendar selects too.

I covered England's bio-secure tour from a Karachi bedroom at three in the morning in 2026, when the grounds were empty and everything ran on protocol. I built a habit then of attaching every claim to the document it came from. Rankings copy needs that habit more than any other beat, because two different things get merged constantly: a player's performance and a table's movement. With Abhishek, performance produced movement. With Kishan, absence did. Both landed in one headline, and that is the difficulty of the roundup.

Three formats, one column

The biggest structural problem in this update is not the material but where it stands. Test, ODI and T20I movements arrive one after another in a single report. Temba Bavuma's 179 is a Test figure; so are the climbs of Harry Brook, Scott Boland and Simon Harmer. Shaheen Shah Afridi and Azmatullah Omarzai rose on the back of an ODI tri-series in Pakistan and the UAE. A reader taking that in as one column builds one table in his head, and that table belongs to no format at all.

This is where the roundup should change shape. A good rankings report needs three datelines, not one. Bavuma's 179 and Omarzai's climb are not the same currency. The first moves an average built across a four-year window; the second moves one built inside an ODI window where the match count is small. Put two currencies in one sentence and the facts stay right while the meaning goes wrong.

One more thing sits in that list and nobody stops at it: geographic spread. Six countries appear in one update — South Africa, India, England, Australia, Pakistan, Afghanistan. That breadth is good news. It also reminds you that the table penalises teams that play less. No matches on the calendar means no fresh points. This is the quietest part of cricket politics: no controversy, no statement, just a team's name sliding slowly downward.

What the record does not say

Here is the part without which the story is incomplete. The update carries no publication date, no ranking period, no match count, and not one line on methodology. There is no mention of women's rankings. The performance figures — Jansen's 10 wickets and 85, Abhishek's 29, 27 and 113, Kishan's injury, Bavuma's 179 — look scorecard-derived, but the source does not cite them.

All of this is being written while I keep a private ledger. During the 2026 tribunal coverage I started a small file — case number, code article, sanction, appeal status — and after that I never wrote about a ban without naming the article breached. By the same logic, every rankings story should carry three fields: the period, the matches counted, and the version of the method applied. Without them the table is a photograph with no date printed on it.

The word 'back', and the calendar's penalty

This is where emotion and rule separate. The headline says Abhishek took the crown back. The word 'back' requires a history — that he was top, fell, returned. The source establishes only that Kishan went past him in July. That is not the history; it is one page of it. Not a large falsehood, just the small slack that sports journalism grants itself daily and never counts.

Read it the other way and the bigger point surfaces: a ranking is not a reward for heroics, it is a moving average that punishes scheduling as much as form. A player who does not play watches old points shrink through the window. A team without a series watches its players slide because others are playing. That is not a flaw; it is the design — an average stays current only by forgetting. But readers should be told, because a man three months out with injury did not lose his place at the crease. Calling that form is misreading the record.

Jansen's twin crowns hide the same trap. Top of two lists in one week looks monumental; in practice it is a coincidence of two different samples. The bowling table says ten wickets in two Tests is enough. The allrounder table says the queue is short. Neither statement means he is the best cricketer in the world, and adding them together to produce that sentence is the error made with numbers every day.

What comes next

The third Test is still running. The table this entire report rests on will move again at the next update, possibly not in the order this week's numbers suggest. In my view there is one place for improvement, and it is procedural rather than technical: every rankings release should print three lines — period, matches counted, method version. It would change no player's evaluation. It would let the reader know what he is reading.

And until the table states its own period, it is not a news story. It is weather — and weather should not be filed like a document.