By Onkar Jadhav · 9 min read
Building a cricket points table that cannot be argued with.
The points schedule, the tiebreak sequence in the order it should be applied, and the three edge cases that decide local tournaments: abandoned matches, walkovers and teams on unequal match counts.
How does a cricket points table work?
A cricket points table awards 2 points for a win, 1 for a tie or no result and 0 for a loss, then orders teams on points. Teams level on points are separated by net run rate first, then head-to-head result, then number of wins. Publishing that tiebreak sequence before the tournament starts is what makes the final table defensible.
The points schedule
| Outcome | Points | Notes |
|---|---|---|
| Win | 2 | Including a win by super over after a tie, where stated in the playing conditions |
| Tie, no super over | 1 each | A tie is not a win for anyone |
| No result or abandoned | 1 each | Excluded from net run rate entirely |
| Loss | 0 | |
| Walkover awarded | 2 | Best practice is to exclude it from net run rate |
| Forfeit or withdrawal | 0 | Per the withdrawal rule published before the tournament |
Some leagues add a bonus point for winning by a large margin. It is defensible and needs its threshold published before the first match, because a bonus-point rule introduced mid-season changes the table retroactively for matches already played.
The tiebreak sequence
- Points. The primary ordering.
- Net run rate. Aggregated across the tournament, with the all-out rule applied.
- Head-to-head result. The outcome of the match between the tied teams. Only resolves a two-way tie cleanly.
- Number of wins. Separates teams whose points came partly from no-results.
- A stated last resort. Coin toss, bowl-out, or higher seed. Name it in advance.
Walkovers
Award the two points. Then decide, in advance, whether the walkover affects net run rate. The cleanest rule is that it does not: the walkover awards points and is excluded from net run rate entirely.
The alternative, awarding a notional margin, requires you to invent a scoreline. Whatever figure you choose will eventually decide a qualification place, and “we assumed a 30-run win” is not a defensible basis for eliminating a team that played all its matches.
Uneven match counts
When teams have played different numbers of matches, the table is genuinely ambiguous and no presentation fixes that. Two things help:
- Publish matches played as a column next to points, so readers can see the asymmetry rather than mis-reading the order.
- Resist reordering on points per match. It is honest as extra information and it is not the rule the tournament will be decided by, so using it as the ordering misleads about who is actually leading.
This is mostly a league problem. A weekend tournament completes rounds and the question does not arise.
A worked table
| Pos | Team | P | W | L | NR | Pts | NRR |
|---|---|---|---|---|---|---|---|
| 1 | Example Club A | 5 | 4 | 1 | 0 | 8 | +1.24 |
| 2 | Example Club B | 5 | 3 | 1 | 1 | 7 | +0.68 |
| 3 | Example Club C | 5 | 3 | 2 | 0 | 6 | +0.31 |
| 4 | Example Club D | 5 | 3 | 2 | 0 | 6 | −0.12 |
| 5 | Example Club E | 5 | 1 | 4 | 0 | 2 | −0.95 |
| 6 | Example Club F | 5 | 0 | 4 | 1 | 1 | −1.46 |
Clubs C and D are level on 6 points and separated on net run rate. B has fewer wins than C but more points, because a no-result awarded a point, which is exactly the case the “number of wins” tiebreak exists for further down. Team names here are illustrative.
Keeping it current
A points table that updates when the last ball is bowled is a different object from one rebuilt on Sunday evening. Spectators check it between rounds, teams plan their qualification arithmetic from it, and every hour it is stale is an hour someone is working from the wrong numbers.
It follows directly from scoring: points, net run rate and the tiebreaks are all derived, so a scored match is a current table. Build one from results you already have with the points table calculator.
Points table FAQ
How many points is a cricket win worth?
Two points for a win, one for a tie or an abandoned match with no result, and none for a loss. Some leagues add a bonus point for winning by a large margin, which is defensible but needs its threshold published, because a bonus-point rule introduced mid-season changes the table retroactively.
What is the correct tiebreak order?
Net run rate, then the result of the head-to-head match between the tied teams, then number of wins, then a coin toss or bowl-out if still level. The important part is not which order you choose but that you publish it before any team has a stake in it.
How are walkovers handled in a points table?
Award the two points, and decide in advance whether the walkover affects net run rate. The cleanest rule is that a walkover awards points but is excluded from net run rate entirely, because any notional margin you invent will later decide a qualification place.
What happens when teams have played different numbers of matches?
The table is genuinely ambiguous until the match counts even out. Publish matches played as a column next to points so readers can see it, and resist the temptation to reorder on points per match, because that is not the rule the tournament will actually be decided by.
Does a tie count as a win for anyone?
No. A tie is one point each. A tie broken by a super over gives the super-over winner the win and the full two points in most published playing conditions, but that has to be stated: a super over is a tiebreak for the match result, not for the points table.