Cricket Run Rate for beginners
If you are new to cricket, the scoreboard can look like a code. One of the first numbers to learn is the run rate, because it is quoted in almost every over of commentary and it tells you, in a single figure, how fast a team is scoring. This guide explains it from scratch: what an over is, what the rate means, and what counts as fast or slow. You need no maths beyond one division, and the Cricket Run Rate Calculator will do the sum for you once you know the two numbers it needs.
What is a run rate?
Run rate is the average number of runs a team scores per over. If a team scores 54 runs in 6 overs, its run rate is 54 ÷ 6 = 9.00, or nine runs per over. The rate lets you compare innings of different lengths: a team that makes 250 in 50 overs is scoring at 5.00, while a team that makes 160 in 20 overs is scoring at 8.00. The second team scored faster, even though its total is smaller. Without the rate, the two totals cannot be compared at all.
What is an over?
An over is a set of six legal balls bowled by one bowler from one end. After six balls, a different bowler bowls the next over from the other end. Wides and no-balls do not count as one of the six, so an over can contain more than six deliveries, but it always contains six legal balls. This is why cricket writes overs with a point: 10.4 means 10 overs and 4 balls have been bowled, not ten point four overs. The digit after the point is a count of balls, from 0 to 5.
A first example
Take a small innings: a team scores 54 runs in 6 overs. Divide the runs by the overs: 54 ÷ 6 = 9.00. That is a fast rate — nine runs every over, or one and a half runs per ball on average. Now take a slower one: 137 runs in 20 overs is 137 ÷ 20 = 6.85. The maths is the same both times, and it is the same maths the calculator does. The only thing that changes is the numbers you feed it.
Reading the scoreboard
A scoreboard usually shows the score as runs, then wickets, then overs: 137/4 in 20 overs means 137 runs, 4 wickets lost, 20 overs bowled. For the run rate you need only the first and third figures: 137 ÷ 20 = 6.85. The wickets do not enter the sum. The scoreboard may also show the rate itself, often labelled RR, and the required rate for the chasing team, labelled RRR. When you see 137/4 (20 ov) RR 6.85, the 6.85 is just 137 divided by 20. Some scoreboards also show the projected score — the total the team would reach if it kept scoring at its current rate — which is the current rate multiplied by the overs left, added to the runs already scored.
What is a good run rate?
It depends on the format. In a Test match, where teams bat for days, 3.00 to 3.50 is normal and anything above 4.00 is brisk. In a 50-over game, 5.00 to 6.00 is a par score and 6.50 or more is strong. In a T20, where each side faces only 20 overs, 8.00 is around par and 9.00 or more is a big total: 160 in 20 overs is 8.00, and 180 in 20 overs is 9.00. The same rate can be good in one format and poor in another, so always read it with the format in mind.
Run rate or required run rate — which number are you looking at?
The scoreboard shows two rates during a chase, and they answer different questions. Run rate is what the batting team has done so far: runs divided by overs faced. Required run rate is what it still has to do: runs still needed divided by overs left. A team at 120 for 2 after 15 overs is scoring at 120 ÷ 15 = 8.00, but if it still needs 78 runs from 10 overs, its required rate is 78 ÷ 10 = 7.80 — ahead of the asking rate, but only just.
The comparison is what matters. If the required rate is below the current rate, the chase is under control; if it climbs above it, the batting side has to score faster than it has managed so far. Watch the two numbers side by side for an over or two and you will see the match turn before the commentators say so.
Mistakes beginners make with the numbers
The most common mistake is reading 10.4 overs as ten point four. It is 10 overs and 4 balls — 64 balls, or 10.67 overs. A team with 96 runs in 12.4 overs is scoring at 96 ÷ 12.67 = 7.58, not 96 ÷ 12.4 = 7.74. The second mistake is forgetting extras: wides and no-balls add runs without adding balls, so they lift the rate without the batsmen doing anything.
The third is judging a rate without the format. A rate of 8.00 wins T20 games and loses Test matches slowly — 160 in 20 overs is par in a T20, while 160 in 50 overs is 3.20 and a long way short. Always ask which format you are watching before you decide whether a rate is good.
Frequently asked questions
What is run rate in simple words?
The average runs a team scores per over. Divide the runs by the overs: 54 runs in 6 overs is a rate of 9.00.
How many balls are in an over?
Six legal balls. Wides and no-balls do not count towards the six, so an over can have more than six deliveries.
What does 137/4 in 20 overs mean?
137 runs scored, 4 wickets lost, 20 overs bowled. The run rate is 137 ÷ 20 = 6.85.
What is a good run rate in a T20?
Around 8.00 is par, so 160 in 20 overs. Above 9.00 is a strong total, and below 7.00 leaves the bowlers with work to do.
More guides on the Cricket Run Rate Calculator
- How to calculate cricket run rate
- Cricket Run Rate formula explained simply
- Cricket Run Rate: worked example step by step
- Common mistakes when calculating cricket run rate
- Cricket Run Rate vs net run rate: what's the difference
- How to use a cricket run rate calculator
- Cricket Run Rate quick reference table
- Cricket Run Rate in real life: everyday examples
- Cricket Run Rate practice questions with answers
Try the Cricket Run Rate Calculator — free, in your browser.