Run Rate Calculator
Measure scoring pace or work out the rate needed in a chase
A score tells you how many runs are on the board. Run rate tells you how quickly they arrived. Enter runs and overs below to find the pace in runs per over.
Current rate: enter total runs scored and overs already faced.
Required rate: use the same fields for runs still needed and overs remaining. Subtract the current score from the winning target first; this tool does not subtract scores or innings quotas for you.
Team total, including extras; or runs needed to win for a chase.
Overs faced; or overs remaining for a chase. Use 4.4 for 4 overs and 4 balls.
The result uses a rounded decimal-overs label, not scorecard notation. Rating labels are fixed pace bands, not format-specific benchmarks or predictions of a win.
For current run rate, enter the team total, including extras. For required run rate, first subtract the current score from the winning target, then enter those runs needed.
Use overs already faced for current rate, or overs still available for required rate. Enter cricket notation: 4.4 means four overs and four legal balls, not 4.4 decimal overs.
Select Calculate Run Rate. The result shows runs per over, runs per ball and a rounded decimal-overs conversion. Use Reset to clear the fields or Copy results to save the result text.
Formula: Runs ÷ Decimal Overs (faced for CRR; remaining for RRR)
Example: 287 runs in 45.4 overs = 6.28 runs per over
Start with legal balls, not decimal-looking overs
The point in a cricket score is easy to misread. At 45.4 overs, the batting side has faced 45 completed overs and four more legal balls: 45 × 6 + 4 = 274 balls. It has not faced 45.4 ordinary decimal overs. Six legal balls complete an over; wides and no-balls add runs without advancing that count.
For a team total of 287, the calculation is 287 × 6 ÷ 274 = 6.28 runs per over, rounded to two decimal places. Dividing by 45.4 instead would give 6.32, a small-looking error that can matter when comparing close scores. Use the scorecard’s overs notation in the input and let the calculator do the conversion.
Current run rate (CRR) = runs scored × 6 ÷ legal balls faced. Include all team extras, not just runs credited to batters. A wicket does not directly change this formula. It can change what the team is likely to score next, which is a different question.
If your scorebook gives balls rather than overs, use the overs and balls converter. Check the score and over count belong to the same delivery before comparing rates.
A chase worked from the scorecard
Suppose the opposition made 180 in a 20-over match. The winning target is 181. Your team is 126/4 after 15.2 overs. The current rate describes the innings so far; the required rate describes the task still ahead.
First find the runs needed: 181 − 126 = 55. Then count the balls: the innings allows 120, and 15.2 overs uses 92. That leaves 28 balls, or 4.4 overs. Subtracting 15.2 from 20 as ordinary decimal numbers would incorrectly suggest 4.8 overs.
| Calculation | Runs input | Overs input | Runs per over |
|---|---|---|---|
| Current rate | 126 | 15.2 | 8.22 |
| Required rate | 55 | 4.4 | 11.79 |
Required run rate (RRR) = runs still needed × 6 ÷ legal balls remaining. Here, 55 × 6 ÷ 28 = 11.79. The team needs to score considerably faster than it has so far. That is useful context, but it does not tell you whether the chase will succeed: wickets, batters, bowling and conditions are outside this calculation.
Keep “opposition score” and “winning target” separate. Entering 180 as the target would calculate the pace needed to draw level with the opposition, one run short of winning this example. For a revised chase, use the target announced by the officials.
Why the required rate moves after every ball
Imagine 19 runs are needed from the last two overs. The starting required rate is 9.50. The following fictional sequence shows why adding a run does not always reduce the required rate.
| Event | Runs needed | Balls left | Required rate |
|---|---|---|---|
| Before the over | 19 | 12 | 9.50 |
| Dot ball | 19 | 11 | 10.36 |
| Four off the bat | 15 | 10 | 9.00 |
| One wide, no other runs | 14 | 10 | 8.40 |
| Single from a legal ball | 13 | 9 | 8.67 |
The dot uses up a scoring opportunity. The four more than makes up for the pace needed on that ball. The wide reduces the target without using a legal delivery. After the single, the equation becomes harder again: one run was less than the scoring pace required.
To check the last row in the calculator, enter 13 runs and 1.3 overs, because nine balls means one over and three balls. Treat the rate as a snapshot. Two teams needing the same rate may have very different prospects if one has eight wickets left and the other has two.
Use the rate for a projection or a passage of play
A rate is also a useful starting point for a quick “what if”. At 96 after 12 overs, the current rate is 8.00. Continuing at exactly that pace would produce 160 after 20 overs. The word “exactly” matters: wickets and changes in intent can make the next eight overs look very different.
| Rate in the last 8 overs | Additional runs | Projected total |
|---|---|---|
| 6 per over | 48 | 144 |
| 8 per over | 64 | 160 |
| 10 per over | 80 | 176 |
These are arithmetic scenarios, not predicted scores. Calculate them as current runs + assumed future rate × overs remaining. The calculator above returns a rate; it does not automatically produce a final-score forecast.
You can also isolate a phase. Suppose the score moves from 44 after 6 overs to 91 after 12.3. That passage added 47 runs in 39 legal balls: enter 47 and 6.3 to get 7.23. The full innings rate at 91 after 12.3 is 7.28. Subtract runs and legal-ball counts first so the phase rate describes only the period you intended to measure.
For several innings together, divide total runs by total overs converted from legal balls. Do not simply average the displayed rates: a two-over burst and a full innings should not have equal weight.
Rain targets and net run rate need separate care
After an interruption, take the official revised winning target and the revised innings limit. For example, a target of 141 in 17 overs with the batting side at 104 after 13.1 leaves 37 runs from 23 balls. Enter 37 and 3.5 to get a required rate of 9.65. The current rate still uses the actual 104 runs and 13.1 overs already faced.
This calculator cannot generate a Duckworth–Lewis–Stern target. DLS accounts for batting resources, including overs and wickets, rather than applying a simple run-rate ratio. Read the ICC’s DLS explanation; our DLS target tool is an educational estimate, not an official match calculation.
Net run rate (NRR) is a tournament statistic. It compares a team’s aggregate scoring rate with the aggregate rate conceded across eligible matches. It is neither the difference between CRR and RRR in a chase nor a simple average of individual match rates.
Competition rules determine the adjustments. Under the cited ICC conditions, an all-out innings uses its full allocated quota for NRR; Super Overs are excluded, and DLS results require specific treatment. A match ending early under DLS and a completed chase after a revised target do not use identical adjustments. Check the governing competition rules before calculating a table position. See the net run rate guide for the separate calculation.
Run rate questions from the scorebook
Why does 45.4 overs become 45.7 in the result?
The input uses cricket notation: 45 overs and 4 balls. That equals 45.666… decimal overs, displayed as 45.7 after rounding to one decimal place. The calculation uses the unrounded conversion, so 287 runs gives 6.28 runs per over. Do not copy 45.7 back into the overs input.
Can I enter zero runs or zero overs?
Zero runs is valid when at least one legal ball has been completed; the rate is 0.00. Zero overs cannot be used as the divisor. Before the first legal ball, a current run rate is undefined even if wides or no-balls have already added runs.
What do I enter when six balls have been completed?
Enter 1 or 1.0 for one completed over, not 0.6. The digit after the point must be between 0 and 5. For example, 17 balls is 2.5 overs. Wides and no-balls do not advance this legal-ball count.
Does the rating tell me whether a chase is realistic?
No. The labels use fixed bands: below 4.5 is Slow; 4.5 to below 6 is Moderate; 6 to below 8 is Good; 8 to below 10 is Brisk; and 10 or more is Explosive. They do not account for wickets, conditions or match format. For a required rate, read the number as the scoring pace needed, not a verdict on the batting side.
What happens when the target is reached or no balls remain?
Once the winning target is reached, no further scoring rate is needed. Do not enter a negative runs-needed value after a winning boundary. If balls are exhausted while runs are still needed, there is no finite required rate to calculate; check the match result and any applicable tie rules.
Should an all-out innings use the full overs quota?
For the actual innings run rate, use the overs the team faced. The full allocated quota is an adjustment used for net run rate under the relevant competition rules. It does not change the scoring pace that occurred during that innings.
Is team run rate the same as bowling economy?
Both are expressed as runs per over, but they count different things. Team run rate includes every run in the innings, including byes and leg-byes. Bowling economy uses runs charged to one bowler and that bowler’s overs, so it cannot be read directly from the team run rate.
Can I use this for Test cricket or other ball-count formats?
You can calculate the scoring rate of a Test innings using its runs and overs. Required rate needs an assumed number of balls still available; a Test match does not have the same fixed innings quota as a T20 or ODI. This tool assumes six-ball overs and is not designed for five-ball sets or historical eight-ball overs.
Method, sources and corrections
Prepared by CricketCals. The examples on this page are fictional and chosen to show the arithmetic; they are not claims about particular matches or players. Calculations assume six-ball overs, retain the unrounded over conversion and display run rate to two decimal places. Runs per ball is shown to three decimal places.
The scoring basis follows the MCC Laws of Cricket, especially Law 17 (the over), Law 21 (no-ball) and Law 22 (wide). For tournament adjustments, see clause 16.10.7 of the ICC Men’s T20 World Cup 2026 playing conditions. Those conditions are a specific competition reference; your league may apply different regulations.
The calculator performs its arithmetic in your browser. For site advertising and other data practices, read the privacy policy. If a result looks wrong, send the runs, overs and expected calculation through our contact page so the example can be checked.