Start with a clean two-match example
Imagine a team scores 160 in 20 overs in one match and reaches a target of 81 in 10 overs in another. Its combined batting rate is 241 runs divided by 30 overs: about 8.033. Averaging the separate rates of 8.0 and 8.1 gives 8.05 instead. The difference is small here, but the method is still wrong because the second innings involved half as many overs.
Now suppose its opponents made 150 in 20 overs and 80 in 20 overs. Their aggregate rate is 230 divided by 40, or 5.75. In this deliberately simple example, the team's net rate is about 2.283. These figures are illustrative, not a current tournament table.
Why an early successful chase changes the denominator
A team reaching a modest target quickly uses fewer overs. Those actual qualifying overs can make its scoring rate high even though it scores fewer total runs. That explains why winning quickly can matter to a tie-ranking measure. The calculation should use the event's treatment of each innings, not the scheduled duration of every match by default.
Do not interpret this as advice that every run or over has the same effect in every circumstance. Revised targets, no-results and dismissals can trigger specific adjustments. The event's playing conditions remain the controlling rule.
All out is a crucial exception
The ICC's explanation says an innings ending all out before its quota is charged the full entitled quota for net-run-rate purposes. Otherwise a side dismissed quickly for a low score could receive an artificially flattering runs-per-over figure.
If a 20-over side is all out for 100 in 15 overs, the simple raw scoring rate is 6.667, but the full-quota treatment uses 100 divided by 20, or 5.0, for this component. Check the actual event's quota and rules rather than assuming every innings is 20 overs.
A reliable checking workflow
Record runs and qualifying balls for each included innings, convert the balls to overs correctly, then aggregate before dividing. Keep a separate note for all-out quota adjustments and rain-rule treatment. Compare your result with the organizer's official table; do not publish a qualification claim from an informal calculator when the event has an unresolved adjustment.
Most importantly, confirm whether net run rate is actually the first relevant tiebreaker. It can be one criterion in an ordered list, not the answer to every equal-points situation. This article explains the arithmetic from ICC documentation; it is not a current standing, a service-access claim or a playback test.
Related questions
Can I average two displayed match net run rates?
That can misweight matches with different overs. Use the aggregate calculation and event-specific adjustments.
Why is an early all-out innings treated differently?
The cited ICC rule uses the full entitled quota so early dismissal does not artificially improve its rate.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- ICC result clause and netrunrate — Aggregate method and all-out full-quota treatment
- ICC current playing conditions — Edition-specific adjustments and tiebreaker source
