What is run rate in cricket?

Run rate (RR) is the average number of runs scored per over: RR = total runs ÷ overs faced. A run rate of 5 means 5 runs are being scored, on average, for every 6-ball over.

How do I calculate run rate?

Divide total runs by the number of overs faced, converting any part-overs to a decimal of six balls first. For example, 156 runs in 28 overs and 3 balls (28.5 decimal overs) gives a run rate of 156 ÷ 28.5, about 5.47.

What is a good run rate?

It depends heavily on format: in Test cricket, 3.0 to 3.5 is typical; in ODIs, 5.0 or higher is solid; in T20, 8.0 or higher is common for a competitive total. Pitch conditions and match situation matter more than a fixed benchmark.

What is the difference between run rate and required run rate?

Run rate describes pace already achieved so far in an innings. Required run rate is the pace still needed, with overs remaining, to reach a target when chasing — a separate, forward-looking calculation.

Can run rate be negative?

No. Runs only accumulate, so run rate is always zero or positive. It can drop very low during a defensive passage of play, but never below zero — unlike net run rate, which compares two run rates and can go negative.

What is powerplay run rate?

It is the run rate specifically during the powerplay overs, the first 6 overs in ODIs and T20s, when fielding restrictions are in effect. Because fewer fielders are allowed outside the inner circle, powerplay run rates typically run higher than the innings average.

Can I project a final score from the current run rate?

Yes, as a rough estimate: multiply the current run rate by the total overs in the format (50 for ODI, 20 for T20). This assumes the rate stays constant, which is rarely exactly true, since teams typically accelerate in the closing overs — treat it as a baseline, not a firm prediction.

Sports & Fitness

Cricket Run Rate Calculator

Calculate run rate with an instant pace verdict and projected totals for ODI and T20.

ℹ️ Looking for a specific chase or points-table stat instead? Use the Required Run Rate Calculator for a live chase, or the Net Run Rate Calculator for tournament standings.

Runs Scored

Overs Faced

Overs use standard cricket notation — "28.3" means 28 overs and 3 balls (converted automatically to 28.5 decimal overs).

Run Rate

—

runs per over

Projected ODI (50 ov)

—

runs

Projected T20 (20 ov)

—

runs

Per Ball

—

runs/ball avg

—

How Run Rate Is Calculated

Run Rate = Total Runs ÷ Overs Faced Projected total = Run Rate × Format overs (50 for ODI, 20 for T20 — assumes rate stays constant)

Run rate is the foundation metric for limited-overs cricket: everything from powerplay analysis to required run rate builds on this same runs-per-over idea.

Run Rate Benchmarks by Format

Format	Conservative	Good	Excellent
Test cricket	Under 2.5	2.5 – 3.5	3.5+
ODI	Under 4	4 – 5.5	5.5+
T20	Under 6.5	6.5 – 9	9+

Real Example: An Outlier Innings

Most innings sit well within the benchmark ranges above, but occasionally a team blows past them entirely. England's world-record ODI total of 498/4 against the Netherlands in 2022 was scored at a run rate above 9.9 — nearly double what's considered "excellent" for the format. It's a useful reminder that these benchmarks describe typical ranges, not hard ceilings.

Common Mistakes to Avoid

Treating overs notation as literal decimal: "28.3" overs is 28 overs and 3 balls (28.5 decimal), not 28.3.
Confusing run rate with required run rate: run rate reflects pace already achieved; required run rate is a separate, forward-looking figure.
Treating a projection as guaranteed: a projected total assumes the current rate holds for the rest of the innings — real innings usually accelerate late.

Frequently Asked Questions

Run rate (RR) is the average number of runs scored per over: RR = total runs ÷ overs faced. A run rate of 5 means 5 runs are being scored, on average, for every 6-ball over.
Divide total runs by the number of overs faced, converting any part-overs to a decimal of six balls first. For example, 156 runs in 28 overs and 3 balls (28.5 decimal overs) gives a run rate of 156 ÷ 28.5, about 5.47.
It depends heavily on format: in Test cricket, 3.0 to 3.5 is typical; in ODIs, 5.0 or higher is solid; in T20, 8.0 or higher is common for a competitive total. Pitch conditions and match situation matter more than a fixed benchmark.
Run rate describes pace already achieved so far in an innings. Required run rate is the pace still needed, with overs remaining, to reach a target when chasing — a separate, forward-looking calculation.
No. Runs only accumulate, so run rate is always zero or positive. It can drop very low during a defensive passage of play, but never below zero — unlike net run rate, which compares two run rates and can go negative.
It is the run rate specifically during the powerplay overs, the first 6 overs in ODIs and T20s, when fielding restrictions are in effect. Because fewer fielders are allowed outside the inner circle, powerplay run rates typically run higher than the innings average.
Yes, as a rough estimate: multiply the current run rate by the total overs in the format (50 for ODI, 20 for T20). This assumes the rate stays constant, which is rarely exactly true, since teams typically accelerate in the closing overs — treat it as a baseline, not a firm prediction.
Several teams have posted innings run rates above 8 in very high-scoring matches — for context, England's world-record ODI total of 498/4 against the Netherlands in 2022 was scored at a run rate above 9.9. These are extreme outliers; a "good" run rate for planning purposes should reference the format benchmarks above, not record-breaking innings.