The World Test Championship points system, explained with the numbers

The short answer: a World Test Championship win is worth 12 points, a tie 6, a draw 4 and a defeat 0. Teams are ranked on the percentage of points they have won out of those available, not on the raw total, and over-rate offences can deduct points.

The World Test Championship gave Test cricket something it had never had in nearly a century and a half: a table, a cycle, and a final worth playing for. It also gave it a points system that almost nobody can explain correctly at first attempt, which is a shame, because the design is genuinely clever once you see what problem it was solving.

This is the whole thing, with the numbers.

The problem the championship was built to fix

Before 2019, a Test series existed only in relation to itself. India beating Australia in Australia mattered enormously to India and Australia and meant nothing at all to the standings, because there were no standings. A team could go five years without playing a meaningful match outside its own bilateral commitments and nobody could say with any authority who the best Test side actually was.

Rankings existed, but they were an algorithm nobody could follow and nothing was ever won. The championship replaced “we think this side is best” with “these two finished top, they play each other, the winner is champion”. That is a considerable improvement even if you dislike the specifics.

What each result is worth

Every Test match in the cycle carries the same value: 12 points are available per match, distributed by result.

Result	Points	Share of the 12
Win	12	100%
Tie	6	50%
Draw	4	33.3%
Loss	0	0%

A tie — both sides finishing on exactly the same score with the fourth innings complete — is worth half a win. It has happened twice in the entire history of Test cricket, so this row is close to decorative, but the system covers it.

The draw at four points is the more interesting number. It is deliberately set at a third of a win rather than a half. Under a half-value draw, a side could construct a respectable cycle by batting for safety everywhere and never risking defeat. At a third, that strategy produces a percentage in the mid-thirties and finishes nowhere near the final. The system is quietly insisting that you try to win.

Why the table is a percentage, not a total

Here is the part that trips people up. Series lengths in Test cricket are not equal and never have been. A team might play a two-match series against one opponent and a five-match series against another, because bilateral fixtures are negotiated between boards rather than set centrally.

If standings were ordered by raw points, the side with the fuller calendar would top the table by playing more cricket rather than by playing better. A team with twelve Tests would beat a team with six almost automatically.

So the table is ordered by percentage of points available:

PCT = (points earned ÷ points available) × 100

Worked example one

A team plays a two-match series and wins both:

• Points earned: 12 + 12 = 24
• Points available: 2 × 12 = 24
• PCT: 24 ÷ 24 × 100 = 100.00

Worked example two

A team plays five matches, winning three and drawing two:

• Points earned: (3 × 12) + (2 × 4) = 36 + 8 = 44
• Points available: 5 × 12 = 60
• PCT: 44 ÷ 60 × 100 = 73.33

The side with 24 points sits above the side with 44. That is not a bug — it is the entire design. The table measures how much of what was on offer you actually took, not how much cricket you were scheduled to play.

Why one bad result hurts more early

A subtlety worth understanding: because the denominator grows as you play, a defeat early in a cycle is proportionally more damaging than the same defeat late. Lose your second Test of the cycle and your percentage craters; lose your fifteenth and it barely moves. Teams that start a cycle badly rarely recover, which is why the first series of a new cycle carries far more weight than its profile suggests.

The over-rate penalty

Slow over rates cost points, and this is the sanction that genuinely changes behaviour. Teams are docked points for failing to bowl their required overs in the time allowed, after allowances are made for wickets, injuries, reviews and other stoppages.

Because a deduction comes off the numerator while the denominator stays fixed, a penalty hurts twice: you lose the points, and your percentage falls. A side docked points across a cycle can slide below a rival it beat on the field, and this has decided placings in practice rather than merely in theory.

It is why you now see captains visibly managing the clock in the final session — hurrying spinners through overs, keeping the field set between deliveries, using the part-time off-spinner for two overs before tea purely to bank time. Some of this is tedious to watch. It is also the only over-rate sanction in cricket history that teams have actually responded to, because fines were simply absorbed as a cost of doing business.

How the final works

The top two on percentage at the end of the cycle meet in a one-off final at a neutral venue. A reserve day is held in case weather costs playing time — it exists to make up lost overs, not to extend a match that has simply run long.

If the final is drawn or tied, the trophy is shared. That has struck plenty of people as an anticlimax, and it is a fair complaint. The alternative — a replay, or a longer final — collides with a calendar that is already past breaking point.

The neutral venue is the other frequent complaint. A final in England suits sides who bat well against the moving ball and disadvantages sides built around spin, which is a real asymmetry when qualification was earned across every kind of surface. Rotating the host would help; it also requires a country willing to stage a match with no guarantee its own team appears in it.

The honest criticisms

Three are worth taking seriously.

Fixture inequality. The percentage system corrects for series length but not for series difficulty. Fixture lists are negotiated bilaterally, so two teams can arrive at the same percentage having played opposition of very different quality. Nothing in the maths accounts for that.

One match to settle two years. The final places enormous weight on conditions at a single venue across five days. A side that was demonstrably the best over a two-year cycle can lose to a good toss and an overcast morning.

Nobody can explain it at the ground. A points table you have to compute with a calculator is a poor advertisement. “India need to win two of three to finish above Australia” is a sentence that requires a spreadsheet to verify, and that is a genuine cost in a sport competing for attention.

None of these is a reason to scrap it. Before the championship, a Test series between two mid-table sides in October meant nothing beyond itself. Now it means something, and a points table that makes people argue about scheduling is a table people are paying attention to.

Quick reference

• Win 12, tie 6, draw 4, loss 0
• Every match is worth 12 points regardless of series length
• Ranked by percentage of available points, not by raw total
• Over-rate breaches deduct points, and therefore percentage
• Early defeats damage percentage more than late ones
• Top two contest a one-off final at a neutral venue, with a reserve day
• A drawn or tied final means the title is shared

More in our cricket section.