An Innings and 31 Runs, Three Percentages and India's Sum: What the WTC Table Leaves Out

Rain on the window of a Levenshulme flat, streetlight lying long across the glass. On the phone screen, three numbers: 75.00, 72.22, 66.67. All three are clean fractions; all three are somebody's fate. The match that produced them is nowhere in the frame.

St George's Park, Gqeberha. The wind comes in off Algoa Bay and runs down the pitch; the ball seams in the third session; the light goes low and slanted by evening. There, South Africa beat Australia by an innings and 31 runs.

That margin is not small. An innings and 31 runs means the hosts' first innings finished 31 runs past Australia's two innings combined. In Test cricket that outcome usually arrives by one of two roads: a first-innings lead north of two hundred, or a second-innings collapse. A dropped catch, a DRS call, one over of swing does not manufacture an innings margin.

What reached the reader was one sentence: Australia lost, so India's chances improved.

The World Test Championship's arithmetic is simple, and simple arithmetic is the most misread thing in sport. Across a two-year cycle, nine teams play each other in series. A win is 12 points, a tie 6, a draw 4, a defeat nothing. Points Percentage — PCT — is points earned divided by points available, multiplied by a hundred.

Now open the table. Australia 75.00: three wins in four matches, 36 of 48. New Zealand 72.22: thirteen wins in eighteen, 156 of 216. South Africa 66.67: two wins in three, 24 of 36.

Notice that all three are clean fractions, and all three reproduce only as win-loss ratios. There is a lesson buried there, and it is the most useful thing in this whole business: the PCT table does not measure a side; it measures a schedule.

To see why, look at the denominator. With eighteen matches underneath, even five defeats can leave a team near 72 percent — 156 of 216. With four matches underneath, one extra defeat drops 75 to 50. The price of a single loss is set by the fixture list, not by the opponent. A side playing more has more room to be wrong; a side playing less carries every result like a lifeboat, one puncture and it is over.

A worked example makes it plain. Give one team eighteen matches; it wins thirteen and loses five — 72.22. Give another four matches; it wins three and loses one — 75.00. The first has lost more and sits level. The second loses once more and falls to 50. Which side is better is a question neither number will ever answer.

Here the source arithmetic shows a seam. PCT is defined by points, not by wins. Those three percentages reproduce exactly only if none of the three sides has drawn or tied a match. No long cycle runs without draws. The piece showed no points breakdown, only the glossy face of a percentage, and so removed even the reader's chance to check the sum.

The cricket is equally incomplete. No scorecard, no first-innings total, no mention of the toss, no word on whether the follow-on was enforced. Yet with an innings margin, those details decide whether the result is signal or accident. The one fact the reader most needed is the one withheld: how those 31 runs actually happened.

I have watched Test cricket since covering the Wills Cup in Dhaka in 2026, and the same thing recurs — at coastal grounds, St George's Park above all, wind and seam movement together can halve an innings. There the home attack, a bowler of Kagiso Rabada's kind in hand, makes the ball talk in a way a neutral ground never does. The match belonged to a coast; the report belonged to a table. That distance is the largest thing in the piece.

So where does India stand? The question cannot be how many points South Africa took. The question is how many matches India have left, and where. India's ceiling is set by their own available points, not by a rival's harvest. A side controls its own denominator; it does not control a neighbour's sum.

This is where I object. Two things are true at once. One: Australia's defeat genuinely compresses the table — a side that has lost cannot raise its PCT, and that is unanswerable. Two: that is a table argument, not a cricket argument. The source served a claim about accounting as though it were a verdict about cricket. And an innings margin can just as easily be a toss-dependent, one-innings collapse; declaring a South African resurgence without knowing which is painting the shape of a cloud from the sound of rain.

One more thing. The analysis the source did not publish was published by supporters themselves — fan scorecards, WhatsApp point calculators, the small tables in independent newsletters. When the old gatekeepers slept, the terraces learned to publish themselves. I first understood that India's path runs through the fixture list from a post on an obscure forum, not from a headline.

I write to find the quiet truth hiding inside the roar. The roar here was 'Australia lost'. The quiet truth is that an innings margin says more than a table does, if anyone will listen.

When the Gqeberha wind dropped in the final session of the fourth day, the board held only a margin — an innings and 31. The stands were emptying; the seam marks were drying under the floodlights. Walking out, some were thinking about the table. I was thinking about the wind.

Test cricket is sometimes a poem that refuses to rhyme the same way twice. In the series ahead, India's fate will be decided in two places: a batting classroom, and a scheduler's file. Do not watch the table. Watch the fixture list. Because the number frightening you most is probably not your team's — it is your denominator.