Run rate is runs divided by overs, with the overs turned into a proper number first. 87 runs in 11.4 overs is 87 ÷ 11.667 = 7.46 runs an over, not 87 ÷ 11.4 = 7.63. At that rate a T20 innings would finish on about 149.
Choose what you want to work out above. The calculator handles the 6-ball over, counts the balls left in a chase, and shows each step.
Formulas
| Figure | Formula | Example |
|---|---|---|
| Current run rate | runs ÷ overs | 87 ÷ 11.667 = 7.46 |
| Required run rate | runs needed ÷ overs left | 89 ÷ 8.333 = 10.68 |
| Projected score | runs + rate × overs left | 87 + 7.46 × 8.333 = 149 |
| Batting strike rate | runs ÷ balls × 100 | 64 ÷ 41 × 100 = 156.10 |
| Bowling economy | runs conceded ÷ overs | 32 ÷ 4 = 8.00 |
| Bowling strike rate | balls bowled ÷ wickets | 24 ÷ 2 = 12.0 |
| Bowling average | runs conceded ÷ wickets | 32 ÷ 2 = 16.00 |
In every formula, turn overs into balls first: 11.4 overs is 11 × 6 + 4 = 70 balls, which is 70 ÷ 6 = 11.667 overs.
Required run rate in a chase
The target is the first innings total plus 1. Take away the score so far to get the runs needed. Count the balls left: in a T20, 120 minus the balls bowled.
Example: Pakistan need 176 to win. They are 87 after 11.4 overs.
- Runs needed: 176 − 87 = 89
- Balls left: 120 − 70 = 50 (8.2 overs)
- Required rate: 89 ÷ (50 ÷ 6) = 10.68 an over, or 1.78 a ball
- Current rate: 7.46, so they must score about 3.2 runs an over faster from here.
Commentators sometimes quote "runs needed off balls" rather than a rate, because it is easier to follow late in an innings. Both come from the same numbers.
Projected score
TV graphics show a projected total at the current rate and at a few faster rates. With 87 after 11.4 overs in a T20 and 8.2 overs left:
| Scoring rate from now | Projected total |
|---|---|
| 6 an over | 137 |
| Current 7.46 | 149 |
| 8 an over | 153 |
| 10 an over | 170 |
| 12 an over | 187 |
Projections ignore wickets. A side that has lost six wickets will rarely keep up its rate, so treat the figure as a guide.
Strike rate and economy
A batting strike rate is runs per 100 balls. 64 off 41 balls is a strike rate of 156.10. In T20 cricket a strike rate above 130 is usually thought quick, while in Test cricket 50 to 60 is normal.
A bowling economy rate is runs conceded per over. Figures of 4-0-32-2 (4 overs, no maidens, 32 runs, 2 wickets) give an economy of 8.00. The bowling strike rate is balls per wicket, here 24 ÷ 2 = 12. Lower is better for both. The bowling average is runs per wicket, 32 ÷ 2 = 16.00.
For a team's standing in a tournament table, use the net run rate calculator.
Run rate questions
How do you calculate run rate in cricket?
Divide the runs scored by the overs faced, after turning the overs into a true number. 120 runs in 15.3 overs: 15.3 overs is 93 balls, which is 15.5 overs, so the run rate is 120 ÷ 15.5 = 7.74 an over.
How do you calculate required run rate?
Divide the runs still needed by the overs left. Chasing 180 in a T20, at 100 for 3 after 12 overs, the side needs 80 off 8 overs, which is 10 an over. If overs have balls, such as 12.3 bowled, count balls left: 120 − 75 = 45 balls, or 7.5 overs.
How is strike rate calculated?
For a batter, divide runs by balls faced and multiply by 100. 45 off 30 balls is 150. For a bowler, strike rate means balls bowled per wicket: 36 balls for 3 wickets is a strike rate of 12.
Why is 11.4 overs not 11.4 in the formula?
An over has six balls, so the number after the point counts balls, not tenths. 11.4 overs is 11 overs and 4 balls, which is 11.667 overs. Dividing by 11.4 makes the run rate look higher than it is.
What is a good economy rate in T20?
Around 7 to 8 runs an over is usually thought good in T20 cricket, and under 7 is very good. In ODIs, 4.5 to 5.5 is good. These are rough guides; pitch, ground size and the phase of the innings all change what counts as good.
Last reviewed 30 September 2026. Results are estimates; official notices always take precedence.