1. How the Table Is Ordered
Points decide the order first; net run rate breaks ties. Teams are ranked by points from wins and ties. When two or more teams finish level on points, the one with the higher net run rate is placed above. NRR here is the aggregate figure across every match the team has played — all runs and overs combined, then the formula applied once.
So NRR never overrides points — a team on 4 points always sits below a team on 6, whatever the run rates. NRR only matters within a group of teams tied on points, which is exactly where qualification is usually decided.
2. A Worked Group Table
Four teams, two games each. Three finish level on 2 points, so NRR orders them.
| Team | Pts | Runs For | Runs Against | NRR |
|---|---|---|---|---|
| Bengaluru Blasters | 2 | 325 in 38.4 | 300 in 40.0 | +0.905 |
| Mumbai Strikers | 2 | 340 in 40.0 | 310 in 40.0 | +0.750 |
| Chennai Kings XI | 2 | 295 in 40.0 | 330 in 39.2 | −1.015 |
| Delhi Daredevils XI | 0 | 280 in 40.0 | 300 in 40.0 | −0.500 |
Delhi are bottom on points, so their NRR is irrelevant to their position — they finish fourth regardless. The interesting battle is the three-way tie on 2 points, and that is where the numbers repay a closer look.
3. Why Fewer Runs Can Rank Higher
Look at the top two. Mumbai scored more runs — 340 to Bengaluru's 325 — yet Bengaluru rank above them. How?
Because NRR is a rate, and Bengaluru faced fewer overs for their runs:
- Bengaluru scored 325 in 38.4 overs (they chased and won early) = 8.41 per over
- Mumbai scored 340 in the full 40.0 overs = 8.50 per over
Their scoring rates are almost identical. The separation comes on what they conceded: Bengaluru gave up 300 in the full 40 overs (7.50), Mumbai gave up 310 (7.75). Bengaluru's tighter bowling, combined with reaching their runs in fewer overs, lifts their differential to +0.905 against Mumbai's +0.750.
The full mechanics of aggregating across matches, and the bowled-out rule that also feeds these numbers, are covered in the how to calculate net run rate guide.
4. Keeping the Table Current
Every result changes several teams' aggregate NRR at once, because a team's NRR moves whenever it plays. Maintaining this by hand across a full tournament means re-computing after every match and applying the bowled-out rule correctly each time — and one arithmetic slip changes who qualifies.
If you run a league, tournament management in the app recalculates the whole table automatically as matches are scored, ordering teams by points and then NRR — the same method as the IPL points table. You can also check any single scenario with the NRR calculator.