← All blog posts

Cricket Run Rate: worked example step by step

WhiteUI · A plain-English guide to the Cricket Run Rate Calculator

The best way to learn the run rate is to work one innings through from start to finish. This guide uses the same example the Cricket Run Rate Calculator opens with, so you can check every step against the tool: a team has scored 180 runs in 30 overs, the target is 250, and 20 overs are left. From those four numbers we get three answers — the current rate, the required rate and the projected score — and each one takes a single division or multiplication.

Three boxes: current rate 6.00, required rate 3.50, projected score 300
180 in 30 overs chasing 250 with 20 left: current rate 6.00, required rate 3.50, projected score 300.

The match situation

Write down the four numbers before you start. Runs scored: 180. Overs played: 30. Target: 250. Overs remaining: 20. The target tells us the runs still needed: 250 − 180 = 70. Everything that follows comes from these numbers, and nothing else is needed — not the wickets, not the batsmen at the crease, not the state of the pitch. If any of the four numbers is wrong, the answers will be wrong, so read them off the scoreboard carefully before you begin.

Step 1: the current run rate

Divide the runs by the overs played:

Current run rate = 180 ÷ 30 = 6.00

The team is scoring six runs per over. That is a solid rate in a 50-over game, where a good first-innings total is often around 280 to 300, but it is only middling in a T20, where teams expect eight or more per over. The same number means different things in different formats, which is why the rate is always read beside the format and the overs left.

Step 2: the required run rate

Divide the runs still needed by the overs remaining:

Required run rate = (250 − 180) ÷ 20 = 70 ÷ 20 = 3.50

The chasing team needs 3.50 runs per over from here. That is well below the 6.00 they have been scoring at, so the chase is comfortable — as long as they do not lose a cluster of wickets. Notice what the required rate does not use: it does not use the runs already scored, except to work out how many are left. A team that has scored quickly can still face a steep required rate if the target is huge and the overs are nearly gone.

Step 3: the projected score

Assume the current rate continues for the overs left, and add it to the score:

Projected score = 180 + (6.00 × 20) = 180 + 120 = 300

If the team keeps scoring at 6.00 for the remaining 20 overs, it will finish on 300 — fifty past the target. The projection is a guide, not a promise: it ignores wickets in hand, the new ball, and the fact that teams often speed up or slow down at the end of an innings. Still, it turns a rate into a total you can compare directly with the target, which is why commentators quote it so often.

Check your answers

Three quick checks catch most errors. First, the required rate should fall when the team scores quickly and rise when it slows down — if yours moves the other way, you have divided the wrong way round. Second, the projected score should sit near the target when the game is close: 300 against a target of 250 says the batting side is ahead, which matches a required rate of 3.50 against a current rate of 6.00. Third, watch the overs format: if the innings had been 180 in 30.3 overs, the current rate would be 180 ÷ 30.5 = 5.90, not 6.00. One extra ball changes the answer, so count the balls.

Run rate or net run rate — not the same number

Run rate and net run rate sound alike and are often confused, but they measure different things and are never interchangeable. Run rate belongs to one innings: runs divided by overs, as in this guide — 180 runs in 30 overs is a run rate of 6.00. Net run rate, usually shortened to NRR, belongs to a whole tournament: it is a team’s runs scored per over across all its matches minus the runs it conceded per over across all its matches. A team can score at 6.00 in a single innings and still carry a negative NRR for the tournament if it conceded heavily in its other games — and a team can win a match while its NRR falls, because NRR counts every match, not just the one in front of you. So when a table asks for NRR, do not enter a single innings’ run rate, and when a chase asks for the rate needed now, do not reach for the tournament figure. The worked example in this guide is a run rate in one innings; NRR needs the full tournament record and a different calculation altogether.

A second innings to work through yourself

Work this one with a pencil before you check the answers — it uses the same three steps as the main example. A team has scored 150 in 25 overs, chasing 280, with 25 overs left. Step one, the current run rate: 150 ÷ 25 = 6.00 runs per over. Step two, the runs still needed: 280 − 150 = 130, and the required run rate is 130 ÷ 25 = 5.20 runs per over. Step three, the projected score: 150 + (6.00 × 25) = 150 + 150 = 300 — twenty runs past the target. Read the pair together: the required rate of 5.20 sits below the current rate of 6.00, so the chase is comfortable, and the projection agrees, finishing twenty past the target. If the required rate had come out above 6.00, the team would need to lift — and the projection would have fallen short of 280 instead. One habit from the main example is worth carrying over: count the balls. An innings of 25 overs and 3 balls is 25.5 overs, not 25.3, and that half-over difference moves every answer that follows.

Frequently asked questions

How do I work out the required run rate?

Subtract the runs scored from the target to get the runs needed, then divide by the overs remaining. Here that is (250 − 180) ÷ 20 = 3.50.

How is the projected score worked out?

Multiply the current run rate by the overs remaining and add it to the runs scored: 180 + (6.00 × 20) = 300.

Why is the required rate lower than the current rate here?

Because the team has scored faster than the chase demands. It needs 3.50 per over from here but has been scoring at 6.00.

Is the projected score a prediction?

No. It assumes the current rate continues unchanged, and it ignores wickets, pitch and match pressure. Treat it as a guide.

More guides on the Cricket Run Rate Calculator

Try it yourself

Try the Cricket Run Rate Calculator — free, in your browser.

Open the Cricket Run Rate Calculator