Officials
Points Table Builder
Enter a group's results and get the full standings, with net run rate worked out the way the official table works it out.
Add every result in the group. The all out boxes change the overs counted for net run rate.
Enter the figures to see the answer.
Beyond the calculator
Umpires and scorers using Crickslab get the revised target, the par score and the over rate on screen, signed off and shared in seconds.
- Rain rules applied as the match runs
- Results and points posted automatically
- Live streaming with the score on the picture
How the number is worked out
The formula
Ordered by points, then by net run rate- points
- Awarded per result according to your competition's scheme.
- net run rate
- Season runs per over scored minus runs per over conceded, with the all out rule applied to the overs.
Many competitions insert head to head result, or number of wins, ahead of net run rate. Check your regulations before treating this order as final.
A worked example: a three team group
Alpha beat Beta, Gamma beat Beta, and Alpha and Gamma tied. Two points for a win, one for a tie.
Beta was bowled out in one of its matches, which is where the table starts to diverge from a naive one.
- 1Alphaone win and one tie = 3 points
- 2Gammaone win and one tie = 3 points
- 3Betatwo defeats = 0 points
- 4Separating Alpha and Gammalevel on points, so net run rate decides
- 5The all out ruleBeta bowled out in 45 of 50 overs is charged the full 50
Alpha and Gamma finish level on three points and are separated on net run rate. Ignoring the all out rule would put them in the other order, which is precisely the sort of error that gets noticed at the end of a season.
Rules and edge cases
The situations that change the answer, and the ones most calculators get wrong.
The all out rule decides more tables than people realise
A side bowled out inside its quota is charged the full quota of overs. Skip it and every net run rate in the table is wrong in the same direction, which is usually enough to reorder teams that are level on points.
Net run rate is a season total, not an average of matches
Add every run and every over across the group, then divide once. Averaging each match's net run rate gives a different answer whenever the matches differ in length, which is nearly always.
A no result is not the same as a tie
A tie is a completed match with level scores and usually earns each side half the win points. A no result is an abandoned match, and it is excluded from net run rate entirely. Treating them the same corrupts both the points and the rate.
The tie break order is set by your competition, not by convention
Points then net run rate is common but far from universal. Many leagues put head to head result first, some use quotient, and some count wins before anything else. This table orders on points then net run rate, so check yours before publishing it.
Bonus points change the shape of a table
Where a competition awards bonus points, the points column is not simply two per win. Work those out first and enter the totals, or use the bonus point calculator alongside this one.
Frequently asked questions
Usually by points first and then by net run rate. Many competitions insert head to head result or number of wins before net run rate, so check your regulations.
For league officials
A table that updates itself as results come in
Crickslab maintains the standings, the net run rate and your competition's tie breaks automatically, so nobody rebuilds a spreadsheet after every round.
See tournament managementLast reviewed 17 August 2026. Playing conditions change, so if your competition uses a different rule, its regulations take precedence over anything here.