How this calculation works
Tournament net run rate uses aggregate scoring and conceding rates. Averaging a list of match NRR values can give the wrong result when innings use different numbers of balls. This page therefore totals the underlying runs and NRR ball counts first.
NRR = 6 × total runs for/total NRR balls faced − 6 × total runs against/total NRR balls bowled; all out uses allocated quotaA worked example
Scoring 160 in twenty overs gives eight runs per over. An opponent all out for 120 in eighteen overs of a twenty-over allocation uses twenty overs for this denominator, giving six. The example NRR is therefore plus two. Changing the opponent all-out flag to zero would use its actual eighteen overs and change the result, demonstrating why the innings status matters.
Good to know
Completed non-DLS equal-quota innings only; no adjusted targets, event-specific rules, live score service or official tournament table. Use the relevant tournament’s official conditions for exceptional matches. The page makes its restricted calculation convention explicit rather than guessing those adjustments.
Reference: ICC — conventional aggregate NRR and all-out rule (opens in a new tab) ↗
What this calculation answers
Tournament net run rate uses aggregate scoring and conceding rates. Averaging a list of match NRR values can give the wrong result when innings use different numbers of balls. This page therefore totals the underlying runs and NRR ball counts first.
An all-out innings uses its allocated quota for this conventional completed-match calculation. Being dismissed early does not improve the denominator by pretending the innings was an ordinary successful short chase.
The Cricket bowling average strike rate and economy calculator uses a bowler’s charged runs and credited wickets. Team NRR totals cannot be substituted for an individual’s scorebook figures.
Use the right input conventions
Enter overs in cricket notation. Three point four means three six-ball overs plus four legal deliveries, or twenty-two balls; it is not 3.4 decimal overs. The final digit can only be zero through five.
Each row requires one shared quota for its two innings and explicit zero/one all-out flags. Runs must be whole numbers. This model is restricted to completed matches without DLS or event-specific score adjustments.
Interpret the result
The table shows the ball counts actually used for NRR and each individual match’s rate difference for explanation. Those match differences are not the values averaged to produce the headline.
Leave abandoned, no-result and DLS-adjusted matches out of this supported calculation. A particular event can prescribe adjustments beyond the simple completed-match rule, and the page does not infer them from a scoreline.
Work through the example
Scoring 160 in twenty overs gives eight runs per over. An opponent all out for 120 in eighteen overs of a twenty-over allocation uses twenty overs for this denominator, giving six.
The example NRR is therefore plus two. Changing the opponent all-out flag to zero would use its actual eighteen overs and change the result, demonstrating why the innings status matters.
Where the model stops
Completed non-DLS equal-quota innings only; no adjusted targets, event-specific rules, live score service or official tournament table.
Use the relevant tournament’s official conditions for exceptional matches. The page makes its restricted calculation convention explicit rather than guessing those adjustments.
A few questions, answered
Is 19.5 the same as 19.5 decimal overs?
No. It means 119 legal balls, which is 19 and five-sixths overs.
Why not average the match NRR column?
Aggregate rates need total runs and total relevant balls, so unequal innings durations need proper weighting.