Skip to content
Scoring5 min

Cricket Run Rate: How to Calculate Current, Required and Net Run Rates

Master cricket run rate calculations — current run rate, required run rate, net run rate formula, worked examples, and how run rates affect team strategy.

Written by GeoCric EditorialUpdated Jul 4, 2026
ShareShareWhatsAppFacebook

Run rates are the heartbeat of limited-overs cricket. The current run rate tells you how fast a team is scoring; the required run rate tells you how fast they need to. Understanding both — and how they interact — is essential for following any T20 or ODI match intelligently.

Current Run Rate (CRR)

Current Run Rate = total runs scored ÷ total overs bowled. A team that has scored 120 runs from 15 overs has a CRR of 8.0. The CRR shows how fast the team is currently scoring, extrapolated as a per-over figure.

Required Run Rate (RRR)

Required Run Rate = runs still needed ÷ overs remaining. A team chasing 180 who have scored 80 from 10 overs needs 100 from 10 remaining overs — an RRR of 10.0. The RRR constantly changes as runs are scored and overs pass.

When a wicket falls without runs being scored, the RRR does not change — it only changes when an over completes without matching the RRR, or when a boundary is hit (which reduces the runs needed and thus reduces the RRR).

The RRR vs CRR Gap

The gap between RRR and CRR is one of the most informative live statistics in cricket. When CRR exceeds RRR, the chasing team is ahead of the required pace — they can afford to lose a wicket. When RRR significantly exceeds CRR, the team is falling behind — each additional over increases the required rate further.

SituationAssessment
CRR > RRR by 1+Team comfortably ahead — conservative play is fine
CRR ≈ RRR (within 0.5)Race is on — steady pace required
RRR > CRR by 2+Team behind — acceleration required
RRR > CRR by 5+Extremely difficult — requires massive acceleration
RRR above 18 in T20sNear-impossible — would require virtually every ball to be a six

Worked Example: T20 Chase

Team chasing 165 in 20 overs. After 10 overs, they have scored 75 runs (CRR = 7.5). They need 90 from 10 overs (RRR = 9.0). The RRR-CRR gap is 1.5 — they are slightly behind. They need to accelerate but have not yet made the chase impossible. If they score 0 from the next over (dot-ball over), the situation becomes: 90 from 9 overs, RRR = 10.0 — now meaningfully harder.

Run Rate and the Batting Captain's Decisions

  • If RRR is manageable (<8 in T20s), the captain may instruct batsmen to play conservatively and build the innings
  • If RRR is climbing above 10, the captain signals that wickets are now less important than boundaries
  • A captain sending in a pinch-hitter is typically a response to an RRR that has climbed beyond normal attack levels
  • Death-over batting orders are decided based on what RRR has been reached at over 16

Frequently asked questions

How is run rate calculated in cricket?

Current run rate = total runs scored ÷ total overs bowled. If a team has scored 90 runs in 9.3 overs (9 complete overs and 3 balls = 9.5 overs in decimal), their CRR = 90 ÷ 9.5 = 9.47.

What is a required run rate of 6.0 in an ODI chase?

A required run rate of 6.0 in an ODI means the chasing team needs to score 6 runs per over from that point to win. In 50-over cricket, this is a modest rate — well within the capability of any professional batting side. It means the team is well-placed in the chase.

Does required run rate include the over in progress or only completed overs?

Required run rate calculations typically use the number of overs remaining including the current one if it has not been completed. A team needing 30 from 5 overs has an RRR of 6.0 — that 5 overs includes the remaining balls of any over in progress.

What is 'run rate' different from 'net run rate'?

Current and required run rates apply to a single match in progress. Net Run Rate (NRR) is a tournament statistic that accumulates across multiple matches and is used as a tiebreaker between teams equal on points in a group stage.