Cricket Run Rate Calculator
Calculate current run rate (CRR), projected score, and required run rate (RRR) for a chase. Use cricket over format like 17.3 (17 overs and 3 balls).
What is run rate in cricket?
Run rate is the average number of runs scored per over. It helps players, coaches, and fans quickly judge batting pace in real time. In limited-overs cricket (ODIs and T20s), run rate is one of the most important live metrics because it directly affects chase pressure and match strategy.
Basic formula
Run Rate = Total Runs Scored ÷ Overs Faced
Example: if a team scores 90 runs in 15 overs, the run rate is 90 ÷ 15 = 6.00 runs per over.
How to read overs correctly (very important)
Cricket overs are not decimal in the normal math sense. One over has 6 balls:
- 10.1 = 10 overs and 1 ball
- 10.4 = 10 overs and 4 balls
- 10.5 = 10 overs and 5 balls
There is no such thing as 10.6 as an over notation in a live score context, because 10.6 becomes 11.0.
Current run rate vs required run rate
Current Run Rate (CRR)
CRR tells you how fast the batting side is currently scoring.
Required Run Rate (RRR)
RRR tells you how fast the chasing side must score from this point onward to reach the target in the overs remaining.
Required Run Rate = Runs Needed ÷ Overs Remaining
Why this calculator is useful
- Instantly check if the batting side is ahead or behind the chase pace.
- Estimate final score from current momentum.
- Support mid-innings decision-making (aggression, strike rotation, bowling changes).
- Avoid common errors when converting overs and balls.
Quick strategy insights from run rate
For batting teams
- If CRR is below RRR, boundaries or high-value overs become necessary.
- If CRR is above RRR, preserving wickets can be smarter than forcing risky shots.
- Use matchup overs (weaker bowler overs) to lift scoring pace safely.
For bowling teams
- Keep dot-ball pressure high when RRR climbs.
- Use best death bowlers when required run rate is near manageable range.
- Protect boundary options when the chase needs 10+ per over.
Common mistakes people make
- Treating 17.3 overs as 17.30 in decimal math instead of 17 overs + 3 balls.
- Forgetting that in many scorecards, the target already includes the winning run (e.g., target 181 means 181 to win).
- Ignoring match context like wickets in hand and batting depth.
FAQ
Can I use this for T20 and ODI?
Yes. Enter total overs as 20 for T20 or 50 for ODI, and the calculator will handle the rest.
Does this calculate net run rate (NRR)?
No. NRR is a tournament metric based on runs scored and conceded across multiple matches. This tool focuses on live match run rate calculations.
What if no target is entered?
You will still get current run rate and projected score (if total overs are entered).
Use this page as a quick in-match companion when tracking live cricket scores, planning chase tempo, or reviewing innings pacing after the game.