Cricket Run Rate Calculator
Calculate current run rate, required run rate, and target scores for cricket matches
Cricket Run Rate Calculator
Calculate current run rate, required run rate, and target scores for cricket matches
What is a Run Rate Calculator?
Run rate is one of the most important live numbers in cricket. It shows exactly how fast a team is scoring — and during a chase, how fast they need to score. Whether you're watching a tense T20 final or a long ODI chase, run rate is what every commentator and fan keeps an eye on.
Current Run Rate (CRR) is simple: total runs scored, divided by overs completed. A team on 120 after 15 overs has a CRR of 8.0. Required Run Rate (RRR) is more telling — it shows how many runs per over the batting team needs for the rest of the innings to win.
Worked example: chasing 180, a team is 90/3 after 12 overs. CRR = 90 ÷ 12 = 7.5. They need 90 more runs from the remaining 8 overs, so RRR = 90 ÷ 8 = 11.25 — meaning they need to lift their scoring by almost 4 runs an over from where they currently stand, which usually means taking more risks against the bowling.
How to Use This Calculator
Understanding Required Run Rates
- • Below 6: Comfortable — easy target
- • 6 – 8: Achievable with good batting
- • 8 – 10: Challenging — aggressive play needed
- • 10 – 12: Very difficult — near impossible
- • Above 12: Exceptional hitting required
Why Run Rate Matters in Cricket
Run rate is the number that tells you how tense a chase really is, faster than watching the scoreboard alone. A required run rate climbing past 10-12 in the last few overs is exactly the moment a match becomes a nail-biter, and it's why commentators repeat the number constantly in the closing overs.
It also shapes real decisions on the field. A batting side well ahead of the required rate can afford to play safe and protect wickets. A side falling behind has to take more risks, which is often when captains bring on part-time bowlers or set unusual fields, expecting the batting team to attack more.
For bowling captains, run rate is a planning tool too. Knowing the required rate helps decide which overs to save their best bowler for — usually the overs where the batting side is under the most pressure to accelerate.
?Frequently Asked Questions
Below 6 is comfortable. 6-8 is manageable with good batting. Above 10 is difficult, and above 12 is extremely tough, even for a strong T20 batting lineup. In the IPL, teams have chased down RRRs above 15 a few times, but that's rare.
CRR (Current Run Rate) shows how fast the team has already scored so far. RRR (Required Run Rate) looks forward — it shows how many runs per over they still need to win from this point on. CRR tells you how the innings has gone; RRR tells you how hard the rest of the chase is.
Required Run Rate = (Target Runs − Runs Scored) ÷ Overs Remaining. If 80 runs are needed from 8 overs, RRR is 10.0. This calculator also handles part overs — 7 overs and 3 balls remaining is treated as 7.5 overs in the maths.
Yes. Just enter 50 as the total overs for an ODI, or the target and overs left for a Test match chase. The formula stays the same for every format — only what counts as a "good" number changes.
RRR only looks at the overs that are actually left. A quiet over with few runs shrinks the number of overs remaining without cutting the target down much, so RRR can jump quickly. This is why a chase can look easy with 8 overs to go and suddenly look tense with 5 overs to go, even though the target barely changed.
There's no single number, since it depends on the ground and pitch, but batting at a run rate that would put your team 15-20 runs above a typical par score for that venue is usually seen as a safe cushion. On a small ground or a flat pitch, that cushion often needs to be bigger.
Yes, whenever the batting team scores faster than the current RRR itself. Every run scored beyond what was needed for that over brings the RRR down slightly for the remaining overs. This is why a big over — say 18 runs — can visibly drop the RRR on the scoreboard right after it happens.