What is the Current Run Rate (CRR) formula?

CRR = Total runs scored ÷ Overs faced. Overs are converted to a decimal first: an over count of 12.4 (12 overs, 4 balls) equals 12 + 4/6 = 12.667 overs. So a team scoring 150 in 12.4 overs has CRR = 150 ÷ 12.667 = 11.84 runs per over.

What is the Required Run Rate (RRR) formula?

RRR = Runs still needed ÷ Overs remaining. Runs still needed = Target − Runs scored so far. Overs remaining = Total overs − Overs bowled so far (converted to decimal). A team chasing 200, having scored 100 in 10 overs of a 20-over match, needs RRR = (200 − 100) ÷ (20 − 10) = 100 ÷ 10 = 10.00 RPO.

Why does 18.3 overs mean 18 overs and 3 balls, not 18.3 decimal overs?

In cricket, an over contains 6 balls, not 10. The notation "18.3" means 18 complete overs plus 3 additional balls, which is 18 + 3/6 = 18.5 decimal overs. The calculator handles this conversion automatically — just type the score as displayed on any scoreboard.

What is a good required run rate in T20 cricket?

In T20 cricket, anything below 8 RPO is comfortable, 8–10 RPO is a fair chase, 10–12 RPO is difficult but achievable, and above 12 RPO is considered very hard. The world record highest successful T20 chase required a run rate of around 13+ in the final stages. ODI chases are generally measured against lower benchmarks because the innings is longer and the required rate builds more gradually.

How does the Net Run Rate (NRR) differ from CRR or RRR?

Net Run Rate is a tournament tiebreaker statistic, not an in-game metric. NRR = (Total runs scored ÷ Total overs faced across all matches) − (Total runs conceded ÷ Total overs bowled across all matches). It accumulates across multiple games. CRR and RRR, by contrast, are calculated within a single innings and tell you the current pace and the target pace of a chase.

Does the Duckworth-Lewis-Stern (DLS) method affect run rate?

DLS sets a revised target when a match is interrupted by rain or bad light. The DLS target effectively changes the "runs needed" figure. Enter the revised DLS target into the RRR calculator and it will compute the new required run rate for the remaining overs. The underlying RRR formula is unchanged — DLS only modifies the input target.

Cricket Run Rate Calculator

Cricket run rates are the single most-watched numbers during a limited-overs chase. Every boundary shifts them; every dot ball tightens the squeeze. This calculator gives you the Current Run Rate (CRR) — how fast a team is scoring right now — and the Required Run Rate (RRR) — how fast they need to score from this point to win. Both figures update instantly as you change the inputs, so you can model any match situation in seconds.

How it works

Current Run Rate

The CRR answers the question: “At what pace has this batting side been scoring?”

CRR = Runs scored ÷ Overs faced

The only subtlety is the over conversion. Cricket scoreboards show partial overs in “overs.balls” notation — 14.3 means 14 complete overs and 3 extra balls. Since an over is 6 balls, not 10, that is actually 14 + 3/6 = 14.5 decimal overs. The calculator converts automatically so you can type the scoreboard figure directly.

Required Run Rate

The RRR answers: “What scoring rate does the batting side need to reach the target?”

RRR = Runs still needed ÷ Overs remaining

Where:

Runs still needed = Target − Runs scored so far
Overs remaining = Total overs − Overs bowled (both converted to decimal)

Both quantities are computed from real balls bowled and real balls remaining, so the result is exact rather than rounded.

Worked example — T20 match

Match situation: Team B is chasing 187 in 20 overs. After 14.3 overs they are 118/4.

Variable	Value
Target	187
Runs scored	118
Overs bowled	14.3 (= 14 + 3/6 = 14.5 decimal)
Total overs	20

Step 1 — CRR:

118 ÷ 14.5 = 8.14 runs per over

Step 2 — runs needed:

187 − 118 = 69 runs

Step 3 — overs remaining:

20 − 14.5 = 5.5 overs (= 33 balls)

Step 4 — RRR:

69 ÷ 5.5 = 12.55 runs per over

Team B need to more than treble their scoring rate from 8.14 to 12.55 RPO — a very steep ask with 33 balls remaining. A couple of boundaries and the picture shifts; type any new score and overs into the calculator to see the live update.

Formula note

The conversion between “overs.balls” notation and decimal overs is the most common source of confusion in manual run-rate calculations. The rule is simple: the digit(s) after the decimal point represent balls, not tenths of an over, so divide them by 6.

Scoreboard	Balls faced	Decimal overs
6.0	36	6.000
6.3	39	6.500
19.5	119	19.833

All figures in this calculator follow the above conversion. There are no approximations — the required run rate and current run rate are computed from exact ball counts.