Key points
- Required rate is runs needed divided by overs remaining.
- Compare it with the current rate to see how much the innings must change.
- Wickets, conditions and DLS are outside the calculation.
- A required rate is a threshold, not a probability.
In this guide
The commentary says the required rate is “climbing to almost nine an over”. Within a few minutes it is “over ten”. The number is doing a lot of work in the conversation, so it is worth knowing exactly what it measures.
The formula
A required run rate is the scoring rate a batting side needs, from this point, to reach its target.
Runs required = target − current score
Overs remaining = balls remaining ÷ 6
Required rate = runs required ÷ overs remaining
The target is the winning score. If the side batting first made 287, the target is 288, not 287.
A chase of 288: the batting side is 219 for 4 after 42 overs. Eight overs remain.
Runs required = 288 − 219 = 69
Overs remaining = 8.0
Required rate = 69 ÷ 8 = 8.63 runs per over
At 42 overs, the current rate is 219 ÷ 42 = 5.21. The gap is 3.42 runs per over. That is the size of the change the innings needs, expressed as a rate.
Compare, don’t forecast
The most useful part of the calculation is the comparison. A side scoring at 5.21 and needing 8.63 has to find roughly 3.4 extra runs every over. That could come from boundaries, from better strike rotation, or from the opposition’s death bowling being less effective than its new-ball spell.
It could also not come at all. The required rate does not know who is batting, how many wickets are left, how the pitch is behaving or who has overs remaining. It is a finish line, not a prediction of the runner.
A quick per-ball sanity check helps:
Runs per ball needed = required rate ÷ 6
At 8.63, that is about 1.44 runs per delivery. In a 48-ball chase, that is a useful way to describe the ask without pretending a six is guaranteed.
When the rate falls without a run being scored
A required rate can move without the score changing. Wides and no-balls add runs without using a ball, so they reduce the required rate. A revised target can change the ask entirely. A rain interruption can remove balls and make the equation harder or easier depending on the resources left.
The required run rate calculator updates the rate and the balls remaining together, which is the point: in a chase, time and runs move in opposite directions.
The parts the rate cannot see
Three limitations are worth keeping in mind:
- Wickets. Nine wickets in hand and one wicket in hand are different tasks at the same required rate.
- Conditions. Dew, a used pitch, a short boundary or a ball change can shift the realistic scoring rate without changing the arithmetic.
- Revised targets. Duckworth-Lewis-Stern targets are not a pro-rata run-rate calculation. Use the official target and the official overs.
The DLS warning
If rain interrupts a match, the target may be revised using the Duckworth-Lewis-Stern method. That method accounts for overs remaining and wickets lost as resources. A simple required-run-rate formula cannot reproduce it, and deriving a target from run rate is not a valid substitute.
Once officials publish a revised target and a revised number of overs, the arithmetic in this article applies to those numbers. Before then, there is nothing reliable to calculate.
A useful summary
The required rate is best read as a gap: the difference between the rate a side has managed and the rate the remaining task demands. That gap shrinks with boundaries and extras, and grows when dot balls accumulate.
It is one of the clearest numbers in the game. It is also one of the easiest to over-read.