Cricket Run Rate Calculator
Calculate the current run rate, required run rate, and projected score for any cricket match. Supports ODI (50-over), T20, and custom formats. Includes chase difficulty assessment and balls remaining analysis.
How Cricket Run Rate Calculator Works
The cricket run rate calculator is a free, browser-based tool that works out current run rate, required run rate and projected score from runs, overs and target. It shows how the ask changes over by over in an ODI, T20 or Test chase. Everything runs on your device and nothing is sent to a server.
Understanding Cricket Run Rate
Run rate is the most fundamental statistical measure in limited-overs cricket. It tells you how many runs a batting team is scoring per over and, in a chase, how many they need per over to reach the target. Commentators, analysts, and fans constantly reference run rate to gauge the state of a match. Understanding run rate dynamics is essential for anyone following ODI (One Day International) or T20 cricket, as well as domestic leagues like the IPL, Big Bash, CPL, PSL, and The Hundred.
Run Rate Formulas
Current Run Rate (CRR) = Total Runs Scored / Overs Completed
Required Run Rate (RRR) = Runs Remaining / Overs Remaining
Projected Score = Current Run Rate × Total Overs
Balls Remaining = (Total Overs - Overs Completed) × 6
Why Run Rate Does Not Decide a Rain-Affected Chase
Once overs are lost to rain, the required run rate stops being the target the chasing side has to beat. Matches are resolved by the Duckworth-Lewis-Stern (DLS) method, which treats a team's remaining overs and remaining wickets together as its resources, and resets the target in proportion to the resources each side actually had (ICC playing conditions). This is why a side eight wickets down faces a harsher revised target than a side one down on the same score and overs, and why the par score on the scoreboard can move without a ball being bowled. Use the required rate here for an uninterrupted chase; in a rain-affected game, the DLS par score is the number that counts.
The Net Run Rate Rule Most Fans Get Wrong
The NRR formula above has one exception that decides qualification more often than any other detail: if a team is bowled out before using its full quota of overs, its overs faced are counted as the full quota, not the overs it actually batted. A side dismissed for 120 in 30 of a possible 50 overs is charged 50 overs, so its run rate contribution is 2.40, not 4.00. That is why captains protect a collapsing innings rather than chase quick runs, and why a heavy defeat can cost a team a semi-final place even when it finishes level on points.
Current Run Rate vs. Required Run Rate
Current run rate (CRR) simply divides total runs scored by overs bowled. If a team has scored 120 runs in 20 overs, their CRR is 6.00 runs per over. Required run rate (RRR) is calculated during a chase: it divides the remaining runs needed by the remaining overs. If a team needs 150 more runs in 25 remaining overs, the RRR is 6.00. The relationship between CRR and RRR is crucial: when RRR exceeds CRR, the batting team is falling behind the required scoring rate and needs to accelerate.
Run Rate in Different Formats
In ODI cricket (50 overs), a run rate of 5 to 6 is typical. Teams usually score slowly in the first powerplay (overs 1-10) at 4 to 5 an over, consolidate at 4 to 5 in the middle overs, and accelerate to 8 to 12 in the death overs (40-50). In T20 cricket (20 overs), the average run rate is higher, typically 7 to 9 per over, with teams scoring 10+ in the final overs. These baselines help assess whether a required run rate is achievable.
Chase Difficulty Assessment
The difficulty of a run rate depends on the format, the stage of the innings, and the wickets in hand. In ODI cricket, a required rate under 6.00 is generally comfortable, 6.00 to 8.00 is moderate, 8.00 to 10.00 is challenging, and above 10.00 is very difficult. In T20, these thresholds shift upward: under 8.00 is comfortable, 8.00 to 10.00 moderate, 10.00 to 12.00 challenging, and above 12.00 very difficult. Wickets in hand significantly affect these assessments, as having 8 wickets in hand makes even a high required rate more achievable than having only 3 wickets remaining.
Projected Score and Its Uses
The projected score extrapolates the current run rate to estimate the total score at the end of the innings. While simple, it assumes the batting team maintains their current scoring rate, which rarely happens due to wicket losses, powerplay rules, field restrictions, and bowling changes. More sophisticated projection models account for these factors, but the linear projection provides a useful baseline. If a team is 150 for 2 after 30 overs in an ODI, their projected score is 250. Actual scores tend to exceed this in modern cricket due to aggressive batting in the death overs.
Impact of Wickets on Run Rate
Wickets in hand are critical context for run rate analysis. A team chasing 300 at 6.5 required run rate with 8 wickets in hand has a much better chance than the same required rate with only 4 wickets left. With wickets in hand, batsmen can play aggressively knowing there are partners to follow. When wickets fall rapidly, the tail-end batsmen are less capable of maintaining high scoring rates, and the required rate can spiral out of control quickly.
Net Run Rate in Tournaments
In cricket tournaments, Net Run Rate (NRR) is used to separate teams on equal points. NRR is calculated as (total runs scored / total overs faced) minus (total runs conceded / total overs bowled) across all matches. A positive NRR means a team scores faster than they concede. Teams aware of NRR implications sometimes bat on aggressively even when victory is assured to boost their NRR, or bowl tightly even when the opposition has no chance of winning to improve their defensive NRR.
Historical Context
The highest successful run chases in ODI cricket demonstrate what elite teams can achieve. West Indies chased 438 against Australia in 2006, maintaining a run rate above 8.7 for the entire innings. In T20 internationals, required rates above 12 have been achieved regularly, with teams like Australia, India, and South Africa showing that with modern batting techniques, deep batting lineups, and the right conditions, virtually any target can be overhauled in the shorter format.
Updated 4 September 2026. DLS and net run rate rules checked against ICC playing conditions.
Frequently Asked Questions
Does the required run rate still apply if rain interrupts the match?
No. Once overs are lost, the game is decided by the Duckworth-Lewis-Stern method, which counts remaining overs and remaining wickets together as resources and resets the target accordingly. That is why a team eight wickets down gets a harder revised target than a team one wicket down on the same score. Use the required run rate for an uninterrupted chase and the DLS par score otherwise.
How does being bowled out affect net run rate?
If a team is bowled out before its overs run out, NRR charges it the full quota of overs anyway. A side dismissed for 120 in 30 of 50 overs is treated as having faced 50 overs, so it contributes 2.40 rather than 4.00. This is the detail that most often decides who qualifies on NRR, and the reason captains protect a collapsing innings instead of swinging for quick runs.
What is a good run rate in ODI cricket?
In modern ODI cricket, a run rate of 5.5 to 6.5 is typical. Top teams regularly score at 6+ throughout their innings. A run rate above 7 is aggressive, and above 8 is exceptional. In T20, run rates of 8-10 are standard.
How is required run rate calculated?
Required Run Rate = Runs Remaining / Overs Remaining. For example, if a team needs 120 runs from 20 overs, the required run rate is 6.00 per over. This changes with every ball bowled.
What required run rate is considered too high to chase?
In ODIs, a required rate above 10 is very difficult and rarely achieved over sustained periods. In T20, rates up to 12-13 have been chased successfully. Context matters: wickets in hand, batting depth, and ground size all affect feasibility.
What is Net Run Rate (NRR)?
NRR is the difference between runs scored per over and runs conceded per over across all matches in a tournament. It is used to separate teams on equal points. A positive NRR means a team scores faster than it concedes on average.
How does the projected score work?
The projected score multiplies the current run rate by total overs. It assumes the batting team maintains their current scoring pace, which is a simplification. In reality, scoring often accelerates in the death overs and decelerates after wickets fall.