85 Runs, Six Wickets and a Number One: The Figure on the ICC's October Shortlist That Outweighs the Name

Gqeberha, St George's Park. The second Test. South Africa's all-rounder takes his sixth wicket and the Australian batter at the other end climbs the pavilion steps. At that moment I was not looking at the screen but at my notebook — which over the run-scoring stopped, which over the seam moved, which over the wicketkeeper stood up and a fourth slip was pulled in. The habit comes from Kalyani. In July 2026 I spent six mornings behind the nets at Bengal's pre-season camp and counted 240 deliveries from a 19-year-old quick — release height, wrist angle, how much the seam wobbled by the fourth spell. The desk wanted 400 words; I filed 1,100 and a scatter chart. I counted 240 deliveries before I understood the net. I have not filed a player profile since without a numbers column.

So when the ICC released its nominees for the October Player of the Month, I had one name to look at and three numbers to count: 85, six, and one. Eighty-five runs, six wickets, and a number one in the rankings.

The name leads the ICC release. For me the biggest story of this October is not the name but the pairing — the thing that touches both ends of a Test match on the same day. This report is the arithmetic of that pairing, and also an account of how far the arithmetic goes and where it stops.

Context: a series that went from 1-0 down to 2-1 up

The first thing to establish is that this was a three-match Test series, played under the ICC World Test Championship, and it finished 2-1 to South Africa. Reports describe it as a turnaround, meaning South Africa were behind early and reversed the momentum. The second Test was at Gqeberha, won by an innings and 31 runs.

An innings-and-31-run win means, plainly, that South Africa batted once, Australia batted twice, and Australia could not even draw level on first innings. That is not a close contest. It is the kind of result where process and outcome point the same way — the toss or a single DRS call does not bend it.

One thing must be recorded here, because it becomes the key to the whole argument later: every one of these performances came in South African home conditions. St George's Park at Gqeberha is counted among the grounds where seam bowlers get help and results arrive. When a Test ends by an innings and 31 runs, the first question is not who scored how many; the first question is who the pitch was helping. Eighty-five runs made on that ground carry a different market value from eighty-five made on a flat deck — and that difference does not show up in any ranking formula.

The third piece of context is that this series counted towards the WTC points table. The entire purpose of the World Test Championship is to convert bilateral series into a points currency, so that no single match is weighted only within its own series. Turning over Australia 2-1 at home is not a three-match change in the table; it is a result that bends the direction of a cycle.

And the fourth piece of context is the award's own architecture. The ICC Player of the Month is a monthly honour chosen through a defined process whose details do not appear in the public release. It is not a certificate for the sport's data; it is the output of a selection process in which numbers, impact and match significance all carry weight. Understanding that gap at the outset matters, because we habitually read a monthly award as a permanent status.

Core analysis: the real meaning of six wickets lies in the runs

1. One match, two ends, and the arithmetic of eleven

In Test cricket an all-rounder's value is clearest in the composition of eleven. If a player can bat in the top six and also bowl a genuine quota, the team can field one extra specialist — an extra batter, or an extra spinner, or a fourth seamer. That is selection freedom, and it becomes expensive on the day the wicket is a result wicket and you need depth on both sides.

The pairing of 85 runs and six wickets at Gqeberha is the cleanest expression of that arithmetic. The point here is not that one player had two good innings; it is that in a single match he touched the outcome in both innings — suppressing Australia with the ball in the first, converting that pressure into runs with the bat in the second. The rarity in Test cricket is partly structural: the match's timeline rarely allows both jobs at once. While you are bowling, your batting brain sits on a different shelf.

Six wickets in an innings is, by itself, a match-defining figure. Add 85 runs to it and the question shifts from 'how many' to 'into whose hands did control of this match pass'. That is exactly where the language of a monthly award and the language of the ground diverge. The award says: best performance of the month. The ground says: in that match, one player set the direction of both innings.

2. Innings and 31 runs — the pitch as evidence

Gqeberha's result tells us something else that never gets printed in the record books: the price of those 85 runs. In a match where 34 or 35 wickets fall inside two and a bit days, 85 runs is worth no less than 130 somewhere else. St George's Park's seam-friendly tendency is no new discovery; the wind, the proximity of the sea and the wear in the surface all push the same way.

Here an old habit resurfaces. At 3 a.m. in Christchurch during the 2026 Under-19 World Cup, sitting at a Kolkata desk on a seven-hour time difference and staring at a scorecard, at 3 a.m. in Christchurch the ground was still a question — whether what happened there was done by a person or arranged by the wind. That night I learned that a number's worth is set by its circumstances. The same rule applies to 85 at Gqeberha.

The reverse is equally true, and this is where honesty lives: if the pitch was helping bowlers that much, the credit for six wickets must be split in the same proportion — some to the bowler, some to the surface, some to the captain's selection. I read this six-for not as one man's mastery but as a settlement between a player and a ground. The settlement was this: the pitch would supply the seam, the bowler would not abandon his line.

3. The third Test — this is the real argument

If there is one figure in this whole story I hold heaviest, it is not the six-for at Gqeberha. It is the half-century and three wickets in the third Test.

The reason is simple. A single-match explosion can be an accident — a good pitch, a bad shot, one bowler's good day. Repetition inside a series cannot be an accident. When the same player contributes on both sides again at the decisive turn of the series, the status of his first performance shifts from 'a good day' to 'a state of form'. Two double-sided contributions in three Tests — a 67 per cent hit rate: that is the small number that pulls the whole shortlist beyond a single name.

In my notebook there is always a column headed 'repetition'. In 2026, when the BCCI cancelled the Ranji Trophy — the first cancellation since 2026-35 — I called 40 fringe Bengal players over eleven days and recorded their voice notes. Nine of those 40 had played fewer than five first-class matches. That series taught me something that still holds: the most reliable indicator in cricket is repetition, because in repetition a player is competing with his own past performance. What looks like repetition is often a slow conversation with failure.

4. Number one — external validation, with a question attached

Reaching number one in the ICC Test All-Rounder Rankings is a different kind of evidence. The ranking is a rolling calculation — not one match but an average of sustained performances, weighted for the strength of the opposition and the context of the match. Which means number one cannot be the prize for a single series; it can only be the sum of several.

That is the strongest part of this whole case: the data is vouched for by the ICC itself, and that voucher is not for October alone but for the months before it. This lowers the probability that the nomination is merely the promotion of one good series.

But a question rises here too, and it is the question my habit demands. The ranking's formula and its weighting are not fully transparent in public. We know a rolling rating slowly forgets old performances and favours new ones, but not how much gap it keeps between home and away returns. Until that gap is public, number one should be read as 'most points', not 'best'. I give the number its full respect and I write its limit just as plainly.

5. The domestic-structure question — the real question

I grew up in Australia watching the Sheffield Shield as a seasonal calendar of domestic grounds, then came to India and started keeping the Ranji Trophy's books. That background builds a habit — behind every big performance, ask what domestic structure made the player. South Africa has produced seam-bowling all-rounders continuously, and it is no magic; it is the output of a structure where four-day domestic cricket is played on seam-friendly pitches and a young player is given room to develop both batting and bowling.

Here I want to place the comparison not as a verdict but as a question, because that is how I am built. The question is: which structure produces a player who can take six wickets and make 85 in the same Test? In India the Ranji calendar and its domestic weight are so large that fewer fast all-rounders emerge whose bodies can carry the dual load of Test cricket. That is nobody's deficiency; it is the shape of a calendar. In Australia the Sheffield Shield's season and its mix of wickets forge a different player. South Africa's domestic structure looks better suited to this particular profile. I treat that as an open question rather than a finding, because the local record-keepers will answer it better than I can.

The contrarian angle: what the shortlist does not say

First — a monthly award is a traffic product

The ICC Player of the Month is a branding and engagement product. It generates traffic, lifts a player's profile on social media, and gives the month's debate a frame. There is no financial transaction in it, no points, no ranking change. To treat it as a certificate for the sport's data is the same error we make with heatmaps — a heatmap shows where a bowler lands the ball, not why he is landing it there. A monthly award shows that someone caught a panel's attention; it does not show how durable his path is.

The biggest weakness of this October shortlist is that it does not itself explain how the selection was made. The voting process, the panel's composition, the weighting of statistics — none of it is in the release. On transparency this is an open question, and I treat it as incomplete rather than sinister.

Second — all the numbers are home numbers

This is the most important point, which is why I saved it for last. Eighty-five runs, six wickets, a half-century, three wickets — all four in home conditions. The series was played in South Africa, Gqeberha is a home ground for them, and their team is habituated to seam-friendly pitches. Concluding from this that the player will do the same everywhere is the same mistake we make when we travel from 'four matches of good form' to 'great player'.

What is visible: at home, on seam-helping wickets, against Australia, an all-rounder turned a series. What is not visible: his shape on the flat pitches of the subcontinent, in English swing, or in a day-night Test. Away-tour numbers are not currently available, so my answer on that question is 'insufficient information', and I will not hide it.

Third — the physical price of a dual load

A bowling all-rounder's workload is the heaviest profile in cricket — the mental load of batting, the physical load of bowling, and the hours spent on the field. It shows most in Test cricket because a match runs five days and a man who bowls 20 overs in one innings also bats at six in the next. When such a player reaches number one in the rankings, his workload does not fall — it rises, because the team leans on him more. Add a franchise-league calendar and the annual clock runs fast. This concern comes not from the data but from the architecture of the profile currently being honoured.

Fourth — the politics of the milestone

I am against journalism that celebrates a hundred or a record without counting the conditions, the match situation and the opposition. The same hazard sits here. This shortlist again offers the chance to build a story around a name — and once built, the story grows larger than three Tests. The correct claim-limit for this player is: 'one of the best performances of the month'. Going beyond that to 'the best all-rounder in the world' means extracting a permanent verdict from a three-match sample. That verdict is not yet in my notebook.

What to watch next

The most moving thing about that Gqeberha afternoon was not the scoreboard. It was the old brass band outside the ground, the group that has stood at St George's Park for decades, playing the same tune for every wicket. I learned the rhythm of a crowd by listening to its gaps — the two or three seconds of silence just before the sixth wicket fell, which no scorecard records. The thing worth understanding is what that silence was waiting for: a player's sixth wicket, or the moment Australia's second spell was going to break. The answer is probably both, and probably that is why this all-rounder's real value is not in the wicket count but in the freedom he bought inside a team of eleven.

The truest audit of this October nomination will come the next time this player takes the ball on an away tour, when we fill the same column we filled at Gqeberha — which over the sixth wicket came in, and how many of those 85 runs were the price of that wicket. Until that day, this shortlist is a question, not a verdict. And keep the question in mind: if his next fifty overs slip away from him, will this October list still be read with the same confidence? The wind behind the wickets never gets recorded — but it is always there.