How do you calculate required run rate?

Divide the runs needed by the overs remaining. To avoid notation errors, convert overs to balls first: runs needed ÷ balls left × 6 gives the required rate per over. For example, 61 needed from 40 balls is 9.15 an over.

What does 13.2 overs mean?

Thirteen completed overs and two balls of the fourteenth. As a decimal it is 13.33 overs, not 13.2. Treating the notation as a decimal is a common source of wrong run rate calculations.

Is a high required run rate always bad for the chasing side?

Not always. With many wickets in hand and the death overs to come, a rate of 9 or 10 can be reachable in T20. The same rate with few wickets left is much harder.

How does rain affect the required run rate?

When overs are lost, targets are usually revised using a resources method that accounts for overs and wickets. The new target and the remaining overs give a new required rate.

Can the required run rate predict who will win?

It helps describe the state of a chase, but it is not a prediction. Wickets, conditions and the players remaining all matter, and matches regularly turn in a few balls.

Guide

Required Run Rate Explained: The Maths of a Chase

Quick Summary

Required run rate is runs needed divided by overs remaining.
Overs like 13.2 mean 13 overs and 2 balls, not 13.2 decimal overs.
A manageable rate with few wickets left can be harder than a steep rate with many.

Last updated 7 November 2026 · PJOK official partner site · written by the pjok88.net team

18+ only
Official partner site
Checked 5 Nov 2026
Know your limit

Every chase in limited-overs cricket comes down to one number on the scoreboard: the required run rate. It tells you how fast the batting side must score from here to win. Commentators quote it constantly, and live betting prices move with it. Yet it is easy to miscalculate, especially because of the way overs are written. This post explains the formula, the notation trap that catches many people, a cleaner balls-based method, and why the run rate on its own never tells the full story.

The formula

Required run rate (RRR) = runs needed ÷ overs remaining. If a side needs 72 from 8 overs, the RRR is 9.0 an over. Compare it with the current run rate (CRR), which is runs scored ÷ overs bowled. If CRR is above RRR, the side is ahead of the rate; if below, it needs to accelerate.

Runs needed is the target minus the current score. The target is the first-innings total plus one. A side chasing 170 needs 171 to win, which is why scoreboards often show "need 61 from 40 balls" rather than raw totals.

The overs notation trap

Cricket writes overs as completed overs and balls. "13.2 overs" means 13 overs and 2 balls, which is 13 and one third overs, not 13.2. Treating it as a decimal gives the wrong answer. The safest method is to convert everything to balls.

Take a hypothetical chase. Target 171. After 13.2 overs, the score is 110 for 3. Balls bowled: 13 × 6 + 2 = 80. Balls left: 120 − 80 = 40. Runs needed: 61. RRR per ball is 61 ÷ 40 = 1.525, so per over it is 1.525 × 6 = 9.15. The current rate is 110 ÷ 80 × 6 = 8.25. Using 13.2 as a decimal would give a CRR of 8.33 and an RRR of 8.97, both wrong.

Step	Calculation	Result
Balls bowled	13 × 6 + 2	80
Balls left	120 − 80	40
Runs needed	171 − 110	61
Required rate per over	61 ÷ 40 × 6	9.15
Current rate per over	110 ÷ 80 × 6	8.25

Why wickets in hand change everything

Run rate measures pace, but resources matter as much. A side needing 9.15 an over with seven wickets in hand can attack freely. The same side needing the same rate with two wickets left must protect its last batters, and the rate becomes much harder to achieve. That is why live match odds can swing sharply on a single wicket even when the RRR barely moves.

Methods such as Duckworth-Lewis-Stern, used when rain shortens matches, are built on the same idea: they treat overs and wickets together as "resources". You do not need the tables to apply the principle. When you see an RRR, ask how many wickets remain and who is still to bat.

Rates in context

In T20 cricket, scoring typically speeds up in the final overs. A side needing 9 an over with 6 overs left and wickets in hand may be in decent shape, because the death overs often produce more than the average rate. A side needing 12 an over from the same position faces a much harder task. As a rough illustration, needing 30 from the last 2 overs (15 an over) usually requires several boundaries, while 15 from 2 overs (7.5 an over) can be done with singles and the odd boundary.

Ground size, pitch and the quality of the bowlers left matter too. Our par score post covers the first-innings side of this, and live cricket betting explains how prices react during a chase.

Using RRR without over-reading it

If you follow live markets, RRR is a useful sanity check on prices: a side well behind the rate with few wickets left should be priced long, and if it is not, the market may know something about the conditions. But it is not a prediction. Chases collapse and recover all the time. Keep stakes fixed, as our unit betting post explains, and avoid reacting to every over.

Three steps

How to work out a required run rate in 3 steps

1
Convert to balls
Turn overs bowled into balls (overs × 6 + extra balls) and subtract from the total balls in the innings.
2
Divide runs by balls
Divide runs needed by balls left, then multiply by 6 to get the rate per over.
3
Add wickets to the picture
Weigh the rate against wickets in hand and the batters still to come.