75.00, 72.22, 66.67 — The Numbers That Don't Add Up in India's WTC Equation
**মূল উত্তর:** দক্ষিণ আফ্রিকার কাছে অস্ট্রেলিয়ার পরাজয় ভারতের ডাব্লুটিসি ফাইনালের পথ গাণিতিকভাবে প্রশস্ত করেছে, কারণ অস্ট্রেলিয়ার পিসিটি আর বাড়তে পারবে না। তবে ভারতের যোগ্যতা নির্ভর করে নিজের বাকি টেস্টের ফল, ড্রয়ের সংখ্যা ও ওভার-রেট কাটার ওপর; প্রতিপক্ষের একক ফল দিয়ে কিছুই নিশ্চিত হয় না। **মূল তথ্য:** - উৎস প্রতিবেদন অনুযায়ী টেবিলে শীর্ষ তিনটি পিসিটি: অস্ট্রেলিয়া ৭৫.০০, নিউজিল্যান্ড ৭২.২২, দক্ষিণ আফ্রিকা ৬৬.৬৭। - ডাব্লুটিসিতে প্রতি টেস্টে সর্বোচ্চ ১২ পয়েন্ট; জয়ে ১২, টাইয়ে ৬, ড্রয়ে ৪, হারে ০। - জয়ের ব্যবধান পয়েন্টে কোনো প্রভাব ফেলে না; Innings ও ৩১ রানে জয় এবং এক রানে জয় — দুটিই ১২ পয়েন্ট। - দক্ষিণ আফ্রিকার জয়টি এসেছে সেন্ট জর্জেস পার্ক, গকেবেরহায়, যা উপকূলীয় ও সিম-সহায়ক ভেন্যু। - পিসিটি ম্যাচসংখ্যা সমান করে, প্রতিপক্ষের শক্তি সমান করে না। **উৎস:** "India's WTC Final chances: What South Africa's win over Australia means" শীর্ষক বিশ্লেষণ প্রতিবেদন; প্রকাশের সুনির্দিষ্ট তারিখ উৎসে উল্লেখ নেই, তথ্য পুনঃযাচাই ১২ ফেব্রুয়ারি, ২০২৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: অস্ট্রেলিয়ার হার কি ভারতের ফাইনাল নিশ্চিত করেছে? উত্তর: না, এটি কেবল টেবিলের তুলনামূলক Position বদলেছে; ভারতকে নিজের বাকি টেস্ট জিততেই হবে। প্রশ্ন: ডাব্লুটিসিতে বড় ব্যবধানের জয়ের কি বাড়তি পয়েন্ট আছে? উত্তর: নেই; নিয়ম অনুযায়ী সব জয়ের মূল্য ১২ পয়েন্ট, ব্যবধান নির্বিশেষে। প্রশ্ন: ভারতের পিসিটি কোন কারণে সবচেয়ে বেশি ক্ষতিগ্রস্ত হতে পারে? উত্তর: ড্র ও ধীর ওভার-রেটের পয়েন্ট কাটা, কারণ ড্র মাত্র ৪ পয়েন্ট দেয় এবং কাটা পয়েন্ট আলাদা দেখানো হয় না।
At half past eleven at night on a Dhaka balcony, the laptop screen shows the World Test Championship points table. Three numbers sit at the top: 75.00, 72.22, 66.67. A friend messages asking whether South Africa's win over Australia has improved India's chances of reaching the final. I scroll and scroll, and the honest answer is that the table cannot tell us that on its own.

I started The Split Times because the numbers never told the whole story. I learned the lesson at the 2026 World Championships in London, watching the men's 400m final: Wayde van Niekerk's 43.98 was not simply a time, it was a 200m split and a final-100m decay hidden inside a single number. The same is true of this table.

What PCT actually measures
The mechanism is simple. Each Test in a two-year cycle carries a maximum of 12 points — 12 for a win, 6 for a tie, 4 for a draw, 0 for a loss. Points earned are divided by points available. The design exists because teams do not play the same number of matches, so raw points would favour the busier side. PCT normalises for the number of games.
It does not normalise for the quality of opposition. Two teams can win four of six Tests, sit on identical percentages, and yet one has done so against bowling attacks averaging 32 and the other against attacks averaging 24. The table tells you how well a side converted; it does not tell you how hard the conversion was.
The first gap: an innings win is worth nothing extra
South Africa beat Australia by an innings and 31 runs. In the table, that is 12 points. A one-wicket win on the final evening is also 12 points. Margin carries no weight at all. Broadcast language and table language diverge completely here.
An innings-and-31-run victory is a structural margin, not a marginal one. It normally requires a first-innings lead north of 200 or a second-innings collapse; a single dropped catch rarely produces it. So the result probably carries real signal about the two sides. The problem is that the source report never identifies the mechanism. St George's Park in Gqeberha is a coastal, seam-friendly ground with a cross-wind — conditions that structurally favour a home pace attack. That is my observation, not the report's. The toss, the weather, the session-by-session shape of the match: all absent. The reader is asked to accept the significance of the result on faith.
India's real arithmetic
Australia losing means Australia's percentage cannot rise, and that compresses the field. That is a table claim, not a cricket claim. India's path depends on three things none of which Australia controls: how many Tests India have left and how many are at home; the length of the remaining series, since a two-match series leaves little room to absorb a defeat; and how many draws India pick up, because a draw is worth only four points and two draws in a seven-Test cycle can push a team into a position that requires a full series sweep to escape.
Suppose India have eight Tests left, a base of 96 points. Six wins, one draw, one loss gives 76.00. Four wins, two draws, two losses gives 58.33. Between those scenarios sits a huge gap, and in both India have lost only one or two matches.

Then there is over-rate. Points deducted for slow play are invisible in the table and can equal half a draw. Rain is the third silent variable: a washed-out Test is four points while a rival simultaneously banks 12, an eight-point swing no individual performance can offset.
One cross-sport comparison
In track and field, a 100m time is never read alone. 9.80 into a −2.0 headwind means something entirely different from 9.80 with a +1.5 tailwind, which is why a wind reading is mandatory beside every legal mark. PCT has no wind reading. Beside 72.22 there is no note of how many of those Tests were at home, how many were away, how strong the opposition bowling was.
The arithmetic is coherent but not reproducible
75.00 is 36 from 48 — three wins, one loss in four Tests. 72.22 is 52 from 72 — four wins, one draw, one loss in six. 66.67 is 24 from 36 — two wins, one loss in three. All three are clean fractions. But the report never states matches played, points earned, or points available, so no reader can reproduce the table. A report about a points table that omits the points is not a table report; it is a report about the idea of a table.
The contrarian angle
Table journalism tells readers where teams stand, never why. It creates the impression that the table is the real game and the cricket on the field is merely its input. The reverse is true. The table is an incomplete translation of the game, where every fraction hides a dropped catch, a wasted review, a damp pitch.
There is a second inversion. We assume India's problem is a rival's result. In practice the biggest variable has been fast-bowling workload and central contracts. Three Tests in four weeks with the lead seamer playing all three costs pace in the fourth. Demanding that a returning player prove himself on his comeback match adds psychological load, and that load raises re-injury risk. Cricket has no transfer window, but contract renewals and workload management are a silent market of their own.
The stadium closed, the backyard opened
In 2026 I covered World Athletics' Ultimate Garden Clash from Dhaka — Duplantis 36 points, Lavillenie 35, Kendricks 33 — while stadiums were shut. When the stadiums closed, the backyard became the arena. Home advantage in this cycle is not only about familiar pitches. It is about less travel, family nearby, control of training infrastructure. In countries where domestic first-class facility standards vary widely, that advantage never appears in PCT.
Dhaka gave me the outsider's eye, and through it this table looks like a picture of an unequal contest.
Forward
The most honest answer about India's WTC final chances is that it remains arithmetic, not event. South Africa's win moved a number. Whether India's road got easier depends on Tests played over the next six months, draws, over-rate deductions, and whether the frontline quicks survive the schedule. The first of those answers arrives when the toss happens on day one of the next series.
We update the points table every year. We never write beside it how hard each team's road has been. If we did, would we still be so quick to comment on whether India's chances have improved?
