Cricket Run Rate Calculator
Calculate the current run rate (CRR) and required run rate (RRR) for any T20, ODI, or Test run chase — just like the number you see on the scoreboard.
Run Chase Worm Graph
Overs on the bottom, cumulative runs up the side — the same style of chart broadcasters use to show whether a chase is ahead of, or behind, the pace it needs.
Target: 181 runs · Blue dot = current position in the chase
CRR vs RRR
The chasing team needs to score 1.34 runs per over faster than their current rate to reach the target — roughly one run every 0.61 balls from here.
Step-by-Step CRR & RRR Calculation
Here's exactly how this answer was calculated, one step at a time.
Given: Target = 181.00, Runs Scored = 96.00, Total Overs = 20.00, Overs Played = 11.2
Step 1: Convert overs played into balls
Cricket overs are written as overs.balls (e.g. 11.2 = 11 overs and 2 balls), so the digit after the decimal is converted separately rather than treated as a fraction.
Balls faced = 11 overs × 6 + 2 balls = 68 ballsStep 2: Calculate the Current Run Rate (CRR)
CRR = Runs Scored ÷ Overs Faced = 96.00 ÷ 11.33 = 8.47 runs/overStep 3: Work out runs still needed and balls left
Runs Needed = 181.00 − 96.00 = 85 | Balls Remaining = (20.00 × 6) − 68 = 52Step 4: Calculate the Required Run Rate (RRR)
Multiplying by 6 converts the per-ball rate back into the familiar runs-per-over figure shown on scoreboards.
RRR = (Runs Needed ÷ Balls Remaining) × 6 = (85 ÷ 52) × 6 = 9.81 runs/over
The required run rate is:
9.81 runs/over
Free Cricket Run Rate Calculator (CRR & RRR)
This cricket run rate calculator works out the current run rate (CRR) and required run rate (RRR) for any run chase — IPL, international T20s, ODIs, or Test cricket sessions. Enter the target score, runs scored so far, total match overs, and overs played, and get an instant, scoreboard-accurate result along with a full worked solution.
Beyond the basic numbers, it plots a worm graph comparing the chasing team's actual scoring pace against the pace needed to win, and gives a plain-language read on how tough the chase is based on the run-rate gap and wickets in hand. It's built for fans following a live match, fantasy cricket players tracking a game, scorers, and commentators who need a fast, reliable read on a run chase.
How Run Rate Is Calculated
Current Run Rate (CRR) = Total Runs Scored ÷ Total Overs Faced. It measures how quickly a team has been scoring so far, expressed in runs per over, exactly as shown on TV broadcasts and scoreboards.
Required Run Rate (RRR) = Runs Still Needed ÷ Overs Remaining. It measures how quickly the chasing team must score from this point onward to reach the target before the innings ends. Because cricket overs are written in overs.balls notation (like 14.3 for 14 overs and 3 balls), this calculator converts everything into balls first so the maths stays accurate down to the last delivery.
Why Run Rate Matters in a Chase
Run rate is one of the most-watched numbers during IPL, T20 World Cup, and ODI World Cup run chases. The gap between CRR and RRR tells a story on its own: a small or negative gap means the batting side is coasting, while a rapidly widening gap signals mounting pressure and a need to take risks against the bowling.
Commentators, analysts, and fans use this gap to judge momentum shifts after boundaries, dot-ball pressure, and the impact of a wicket falling at a key moment — all things this calculator's worm graph is designed to visualise at a glance.
Reading the Worm Graph
The worm graph plots three lines against the number of overs bowled. The grey dotted line is the 'par pace' — a straight-line average of what run rate is needed across the whole innings if the required rate never changed. The solid blue line is the team's actual scoring so far, and the dashed red line projects the pace still needed to reach the target from the current position onward.
When the blue line sits above the grey par line, the team is ahead of a flat, average chase; when it dips below, the red required-pace line steepens to compensate. A blue dot marks exactly where the chase currently stands.
T20 vs ODI vs Test Run Rates: What's 'Good'?
What counts as a strong run rate depends heavily on the format. In T20 cricket, a current run rate above 8-9 runs per over is generally considered strong on a good batting pitch, while anything below 6 usually means the asking rate will climb sharply later in the innings.
In ODIs, a run rate of 5-6 per over through the middle overs is typical, with the final 10 overs often pushing well past 8-9 as teams look to maximise their final total or complete a chase. Test cricket rarely focuses on required run rate in the same way, since matches are rarely run chases against the clock — except on the final day, when a declaration sets a target and overs, turning it into a chase just like limited-overs cricket.
Wickets in Hand and Chase Difficulty
Run rate alone doesn't tell the whole story — a side chasing a steep required rate with nine wickets in hand is in a very different position from one needing the same rate with only two wickets left. This calculator's difficulty read combines the run-rate gap with wickets lost to give an intuitive verdict, from 'Coasting' through to 'Improbable'.
This is a simplified, descriptive guide rather than a statistical win-probability model. Professional broadcasts and analysts often use the Duckworth-Lewis-Stern (DLS) method or ball-by-ball win-probability models, which factor in historical scoring data across thousands of matches — well beyond what a straightforward run-rate calculator can capture.
Worked Example: A Tight T20 Finish
Suppose a T20 team is chasing 181 and has scored 96 runs in 11.2 overs. First, overs played convert to balls: 11 overs × 6 + 2 balls = 68 balls faced, so CRR = 96 ÷ (68 ÷ 6) = 96 ÷ 11.33 ≈ 8.47 runs per over.
With 20 overs (120 balls) total, 52 balls remain and 85 runs are still needed, giving RRR = (85 ÷ 52) × 6 ≈ 9.81 runs per over. The gap of roughly 1.3 runs per over between CRR and RRR shows the required rate has to climb only modestly — a manageable but not trivial finish.
How Required Run Rate Changes Through an Innings
Required run rate rarely stays flat. Early wickets or a string of dot balls push it up quickly since overs run out at a constant pace regardless of scoring. Conversely, a flurry of boundaries can drop the required rate sharply, sometimes even below the current run rate, flipping the chase from behind to ahead of the game within a single over.
This is why the same target and score can feel completely different depending on how many overs are left — 60 needed off 60 balls looks calm on paper (a required rate of 6), but 60 needed off 12 balls (a required rate of 30) is close to impossible outside of an extraordinary final-over blitz.
Common Mistakes When Calculating Run Rate
A handful of errors come up repeatedly when people try to work out run rate by hand.
- Treating the overs.balls notation as a decimal fraction — 14.4 overs is not 14.4 overs mathematically, it's 14 overs and 4 balls (14.667 decimal overs).
- Forgetting that the target for the chasing side is the first team's total plus one run, not the exact total itself.
- Mixing up which side's overs are being measured — required run rate is always about the overs remaining in the chasing team's innings, not the match as a whole.
- Ignoring wickets in hand when judging how 'easy' a required rate looks — the same number can be routine with wickets to spare or a near-impossible ask with only a couple left.
- Rounding too early in manual calculations, which can shift the required run rate enough to misjudge a tight finish.
How to Use This Calculator
Pick a match format to auto-fill the total overs, or set a custom value for a rain-affected or reduced-overs match. Enter the target score, runs scored so far, overs played in X.Y cricket notation, and wickets lost, or tap one of the quick-fill example chases to see it in action instantly.
The result panel, worm graph, run-rate comparison, and full step-by-step working all update immediately as you type, making this a fast tool for checking a chase live, setting up a fantasy cricket scenario, or working through a stats homework question.
Frequently Asked Questions
How do you calculate required run rate in cricket?
Required run rate is calculated by dividing the runs still needed to win by the balls remaining in the innings, then multiplying by 6: RRR = (Runs Needed ÷ Balls Remaining) × 6.
What is a good current run rate in T20 cricket?
In T20 cricket, a current run rate above 8-9 runs per over is generally considered strong, though it depends heavily on the pitch, target, and match situation.
Does this cricket calculator work for ODI and Test matches too?
Yes. Select ODI to auto-fill 50 overs, or choose Custom to set any total, including a reduced or rain-affected match. For a Test match run chase on the final day, enter the declared target and the overs set for the chase.
Why do I need to enter overs as X.Y instead of a decimal?
Cricket overs are written as completed overs and balls into the next over (e.g. 11.2 = 11 overs, 2 balls), which is not the same as a true decimal fraction. The calculator converts this notation to balls internally so CRR and RRR stay accurate to the ball.
What does the target score mean if I'm chasing?
Enter the number of runs needed to win, which is the first team's total plus one, not the exact total they scored.
How does wickets lost affect the required run rate number?
Wickets don't change the RRR formula itself, which only depends on runs and balls. But this calculator uses wickets lost alongside the run-rate gap to give a difficulty read, since the same required rate is far riskier with fewer wickets in hand.
What is the worm graph showing?
It plots cumulative runs against overs bowled: a grey dotted par-pace line, a solid blue line for actual scoring so far, and a dashed red line for the pace still required from the current point to reach the target.
Is this the same as the Duckworth-Lewis-Stern (DLS) method?
No. DLS is a statistical method used to reset targets in rain-interrupted matches based on historical scoring resources. This calculator only computes the straightforward current and required run rate from the numbers you enter.
Can I use this for fantasy cricket or commentary prep?
Yes, it's commonly used by fantasy cricket players tracking a live run chase and by scorers or commentators who want a quick, accurate required run rate without doing the overs-to-balls conversion by hand.
What happens if the required run rate is lower than the current run rate?
It means the chasing team is ahead of the pace needed to win and can afford to slow down slightly and still reach the target — reflected here as a 'Coasting' difficulty read.