Marco Jansen's Double No. 1: Where the Ranking Ends, the Count Begins

One week, one player, two No. 1 tags. Marco Jansen has moved to the top of the Test bowling rankings and the Test all-rounder rankings in the same update. The headline calls it a double delight. The second story in the same report is Abhishek Sharma returning to No. 1 among T20I batters. I have a habit that has annoyed editors for years: before I trust a headline, I open the table. This table gives positions, not points. Where points are withheld, No. 1 becomes a title rather than a distance. You cannot tell from it how far ahead the leader actually sits. That is the first thing that bothers me here, and it is not a comment on any player. Jansen's double is genuine news. The question is what kind of news it is — form, durability, or calendar. Before I believe the story, I rebuild the ledger. This time it splits into three parts: the arithmetic of the rankings, the facts the report supplies, and the places where facts are missing. The third part matters most. There is no publication date, no ranking week, no points totals, and no independently sourced scorecard for any of the matches. A story that arrives without these is a snapshot, and a snapshot should be labelled as one. The ICC system runs on a weighted average. Each innings or spell earns points, those points are averaged with recent matches weighted more heavily, and a minimum-match threshold keeps a player on the table. That is why a ranking can jump inside one series and slide back inside the next. The three formats are calculated separately, and form in one does not transfer at the same rate to another. The all-rounder table is different: it combines batting and bowling performance points into a single index, which means one match lands in two columns at once. A strong spell lifts the bowling side, and any useful runs in the same game lift the batting side. The consequence is that a big jump in the all-rounder table is often the product of a single match, while from the outside it reads like two independent skills peaking together. This habit of mine dates to 2026, when a Bangalore digital cricket desk handed me RCB's home season and I logged every ball, tagging death overs as 16 to 20. The lesson then was that definitions come before results. Without a definition of a death over, an economy of 12.6 is an empty number. The same rule applies here: which matches counted, in which window, at what weight. Without that, No. 1 is an empty title too. The first half of the Jansen story is straightforward: a match-winning performance against Australia, then top spot in both lists. The report quotes Dale Steyn calling him the best cricketer in the world. It is a good quote and it colours the piece, but it is external opinion, not analysis, and its original source, date and context are not given. I treat it as colour, not evidence. The real knot is the all-rounder table. Ravindra Jadeja held that top spot for roughly four years. A four-year reign is information in itself: it tells you the index moves slowly, because it demands sustained output in both skills plus the minimum-match requirement. A rapid climb on such a table is rare, which is why it draws attention. That same climb also tells you that both columns moved at once — which is usually the double accounting of one performance, not proof of two independent skills. One more gap is visible here. The rankings count matches, not overs. The workload of a fast bowler playing all three formats, two fixtures in a week, travel between them, the practice sessions lost to it — none of that appears in the table. Watching fast-bowler workloads over the last few years, the risk sits less in any one spell than in the shape of the calendar. The ranking does not price that risk, so treating the top spot as a fitness certificate is a mistake. The second story: Abhishek Sharma, 113 off 38 balls against New Zealand with a 35-ball century, and a return to No. 1 among T20I batters. The report notes that Ishan Kishan took the spot from him in July, and that Travis Head features in the same conversation. The T20I batting table weights strike rate and recent impact heavily, because the format demands it. A 35-ball hundred is an extreme performance. But a ranking is a weighted average, not an innings. An innings moves an average; it does not define it. Here is an audit flag, and it is not a small one. July appears twice in the report: once for Kishan taking No. 1, and once for Abhishek first reaching the top in July 2026. Those two statements only reconcile with a publication date attached. Without it the timeline does not close, and the value of a rankings story depends entirely on its date. The rest is a roundup. Temba Bavuma's 179 and a series squared at 1-1; Harry Brook, Scott Boland and Simon Harmer moving up. Sanju Samson, Finn Allen, Mitchell Santner and Arshdeep Singh in T20I. Ben Duckett, Shaheen Afridi, Azmatullah Omarzai, Bernard Scholtz and Mohammad Nabi in the ODI tri-series involving Pakistan, England and Sri Lanka. This section is a table, not an analysis. The report does not say which match sits behind which movement, and without that the movement cannot be interpreted. The pairing of Bavuma's 179 with a 1-1 series is the most useful fact in the section: a big innings did not tilt the series, and the rankings award points to exactly such matches. Now the part most often misread. No. 1 is a statement about the calendar as much as about the player. Recent matches carry more weight, so one good series changes the position and one bad series changes it back. A rising ranking is evidence of recent form; it does not prove the same player will be there in two years. This is where I have to guard against my own habit. Contradicting every headline is easy, and once it becomes a reflex it stops being an audit and becomes a mood. So I will write it plainly: the arithmetic is right. In this window Jansen is top of both Test lists and Abhishek is top of the T20I batting list. My disagreement is not with the ranking but with the sentence attached to it — the best cricketer in the world. That sentence is not the ranking speaking; it is the quote speaking. My fix comes from the auction model. The rule there was that a price belongs to a contract, not to merit. The same is true of a rating: it belongs to a window, not to a career. Keep them in separate columns and state which question the table can answer and which it cannot. The empty-stadium season taught me the same discipline in another form — when the environment changes, separate the environment from the sample before you change the conclusion. The rankings do a version of this by weighting wickets for opposition and match situation. The difference is that they do not publish the working, and claims built on unpublished arithmetic should be hedged accordingly. The limits, stated in advance: no points, no publication date, no independent scorecard, no original context for the Steyn quote. I deliberately froze three adjustments — the double accounting in the all-rounder index, the recency weighting, and the timeline inconsistency. Venue, home conditions, opposition batting quality and calendar load remain acknowledged limits, not excuses to abstain. What survives them is modest: in this window these two names are on top, and behind each sits one identifiable performance. What does not survive: that this is a permanent shift, or that the gap at the top is large. When the next table lands, check three things. The points gap. Whether the minimum-match threshold is met. Whether the same performance has been counted in two columns or one. South Africa's next Test cycle will tell us whether Jansen's top spot is a series spike or a habit. India's next T20I assignment will tell us whether Abhishek's return is structural or the arithmetic of one innings. My forecast conditions are written down before the result: no call without a base rate, a sample and an error bar. The sample here is small; the claim built on it should not be large.