Run Rate Calculator

What the run rate calculator does

Run rate is the heartbeat of a limited overs innings, the number of runs a team is scoring for every over it faces. This tool works it out. You give it the runs scored and the overs faced, and it tells you the run rate, the runs per over, which is the figure you see ticking along on every scoreboard.

It is just as useful in a chase, where the same idea becomes the asking rate, the pace the batting side now needs to keep up to win. More on that below, because that is where run rate gets tense.

How to use it

1. Enter the total runs scored. The team's score.
2. Enter the total overs faced. How many overs it took to score them. If the innings ended mid-over, enter the overs as a proper decimal, which is explained a little further down because it catches people out.

Press Calculate for the run rate, or Reset to clear the boxes.

How run rate is worked out

It is a single division, runs over overs:

Run rate = total runs ÷ total overs

So 150 runs in 30 overs is a run rate of 5.0, meaning the team is averaging five runs an over. That is all the scoreboard figure is. The interesting part is not the sum, it is what you do with it.

The required run rate in a chase

Here is where this tool earns its keep on a match night. When a team is chasing, the question is not how fast they have scored, it is how fast they now need to. That is the required run rate, or asking rate, and it is the same calculation pointed at what is left:

Required run rate = runs still needed ÷ overs remaining

Need 80 to win off the last 8 overs? Enter 80 runs and 8 overs, and the asking rate comes out at 10 an over. As the chase goes on, you can keep re-checking it, and that is the drama of a run chase in one number: every dot ball nudges the asking rate up, every boundary pulls it back down, and the whole crowd is watching it climb.

A word on overs, because they are not decimals

This is the one thing to get right. An over has six balls, so the part after the point in an over count is balls, not tenths. When a scoreboard says 15.3 overs, it means 15 overs and 3 balls, and 3 balls is half an over, so the true decimal is 15.5, not 15.3. If you type 15.3 into the calculator expecting it to mean 15 overs and 3 balls, the run rate will be slightly off.

The fix is easy: divide the balls by six and add them on. 3 balls is 3 divided by 6, which is 0.5, so 15.3 overs becomes 15.5. Four balls would be 0.67, two balls 0.33, and so on. Do that small conversion first and your run rate will be spot on.

An example with real numbers

Say a team posts 180 in their 20 overs of a T20 innings.

• Run rate = 180 ÷ 20 = 9.0 runs per over

That is a strong T20 total, scored at nine an over. Now flip it to the chase. If the side batting second needs those 181 to win and they are 100 for 2 after 12 overs, they need 81 more off 8 overs, which is an asking rate of about 10.1. Still gettable, but the pressure has just gone up a notch, and the run rate is what tells you so.

What counts as a good run rate

It depends entirely on the format, because each one is a different kind of race. In a T20, anything around 8 an over and up is a healthy rate, and the best innings push well past 10. In a 50 over one-day game, a rate of 6 an over sets up a big score, while 5 is steady. In Test cricket, run rate matters far less, since time, not overs, is the limit, and a rate of 3 to 4 an over is often plenty. So read your run rate against the game you are playing, not against some single magic number.

Questions people ask

How do you calculate run rate in cricket?

Divide the runs scored by the overs faced. A score of 150 in 30 overs is a run rate of 5.0, or five runs an over.

What is the required run rate?

It is the pace a chasing team needs to win, found by dividing the runs still needed by the overs remaining. Need 60 off 10 overs and the required run rate is 6 an over.

How do I enter overs like 15.3?

Convert the balls to a fraction of an over first. The 3 in 15.3 means 3 balls, which is 3 divided by 6, or 0.5, so enter 15.5. Treating it as a flat 15.3 gives a slightly wrong rate.

What is a good run rate?

It varies by format. Around 8 or more an over is good in a T20, about 6 in a one-day game, and 3 to 4 is normal in Tests, where overs are not the limiting factor.

References

1. ESPNcricinfo, Net Run Rate explained (definition of run rate and runs per over). https://www.espncricinfo.com/ci/content/page/429305.html