Cricket Run Rate Calculator

How run rate is calculated

The current run rate (CRR) is simply runs scored ÷ overs faced — but the overs figure is where almost everyone slips. A scoreboard reading 15.3 does not mean fifteen-point-three overs: it means 15 complete overs and 3 balls of the sixteenth. An over is six balls, so those 3 balls are 3 ÷ 6 = 0.5 of an over, and 15.3 on the board is really 15.5 in decimal. A side on 147 at 15.3 is scoring at 147 ÷ 15.5 = 9.48 runs per over — punch 147 ÷ 15.3 into an ordinary calculator and you get 9.61, wrong by an eighth of a run per over. That's exactly the mistake this calculator exists to prevent: overs and balls go in separately and the sixths are handled for you.

Required run rate in a chase

Chasing flips the question from "how fast are we scoring?" to "how fast must we score?". The required run rate (RRR) is (runs still needed ÷ balls remaining) × 6. Needing 33 from 27 balls means (33 ÷ 27) × 6 = 7.33 per over. Unlike the current rate, it moves with every single delivery: a dot ball spreads the same runs over fewer balls and nudges the rate up, while one boundary can drop it by half a run per over. That ball-by-ball drift is why a chase that looks comfortable at 7-an-over can become frantic after two quiet overs — and why comparing CRR against RRR, as the verdict above does, tells you instantly whether the batting side is ahead of or behind the game.

Why T20 rates run higher than ODI rates

Format changes what a "good" rate is. In a T20 innings there are only 120 balls and ten wickets, so wickets are cheap relative to balls — batters attack from the first over, fielding restrictions bite harder, and par first-innings scores of 160–180 work out at 8–9 per over. In an ODI the same ten wickets must be stretched across 300 balls, so preserving them is worth more than risk: typical rates sit around 5.5–6.5, climbing only at the death. Judge a rate against its format, not against cricket in general.

What about Net Run Rate (NRR)?

Net run rate is a tournament tie-breaker, not a match stat: it's a team's overall runs-per-over scored across the competition minus the runs-per-over conceded, used to separate sides level on points in league tables. Computing it needs both innings of every match (with special handling for sides bowled out). This tool computes the in-match rates — CRR and RRR — which are the building blocks NRR is made from.

Frequently asked questions

How do you calculate run rate in cricket?

Divide the runs scored by the overs faced, with the overs converted to a true decimal first. Balls are sixths of an over, so 15.3 on the scoreboard is 15 + 3/6 = 15.5 overs. A team on 147 after 15.3 overs has a current run rate of 147 ÷ 15.5 = 9.48 runs per over.

What does 15.3 overs mean?

15 complete overs plus 3 balls of the 16th over — the digit after the point counts balls (0 to 5), not tenths. Because an over is 6 balls, 15.3 equals 15.5 in decimal overs. Treating it as the plain decimal 15.3 is the most common run-rate mistake.

How is required run rate worked out?

Required run rate = (runs still needed ÷ balls remaining) × 6. Needing 33 from 27 balls gives (33 ÷ 27) × 6 = 7.33 runs per over. It shifts after every delivery: a dot ball nudges it up, a boundary pulls it down.

What is a good run rate in T20?

Around 8 runs per over is competitive — par first-innings T20 scores of 160–180 work out to 8–9 per over. Anything above 9 is a strong rate, and death-overs bursts often pass 12. ODI rates are lower, typically 5.5–6.5, because 50 overs reward keeping wickets in hand over constant risk.