Cricket Required Run Rate Explained: Chase Targets, Asking Rate and Winning Scenarios
required run rateasking raterun chaselimited-overs cricketlive match analysis

Cricket Required Run Rate Explained: Chase Targets, Asking Rate and Winning Scenarios

CCricFizz Editorial Desk
2026-11-18
7 min read

Learn how to calculate cricket’s required run rate and assess a chase using runs needed, balls, wickets, scoring pace and revised targets.

Required run rate tells you how quickly a batting team must score to reach a target, but the number is most useful when read alongside balls remaining, wickets in hand, current scoring rate and match conditions. This practical checklist explains how to calculate the asking rate during a chase, interpret winning scenarios and avoid common scorecard mistakes.

Overview

The required run rate, also called the asking rate, is the average number of runs a team needs to score per over to reach its target from the current position. It changes after almost every delivery, so a live cricket score is only the starting point. A meaningful assessment also requires the revised target, runs already scored, wickets lost and legal balls remaining.

The basic equation is:

Required run rate = runs needed ÷ overs remaining

For example, if a team needs 120 runs from 15 overs, its asking rate is 8.00 runs per over. If it scores 18 runs in the next two overs, it needs 102 from 13 overs, making the new required rate approximately 7.85. The calculation should be repeated after a significant partnership, wicket, boundary, change of bowler or interruption.

Use the target rather than the opponent’s score alone. In a standard chase, the target is generally one more run than the first innings total. If the match has been shortened or a revised target has been issued, use the official target shown in the match centre or scorecard. Do not continue calculating from the original total after an interruption has changed the equation.

Remember that cricket overs are groups of six legal balls. Five overs and three balls means 33 legal balls, not 5.3 overs in a mathematical sense. When calculating from balls, use:

Required run rate = runs needed × 6 ÷ legal balls remaining

Thus, 45 runs from 33 balls requires 45 × 6 ÷ 33, or approximately 8.18 runs per over. This method is safer than treating 5.3 overs as 5.3 decimal overs.

Checklist by scenario

1. A normal limited-overs chase

  1. Confirm the official target and innings format.
  2. Record the batting team’s current score.
  3. Subtract the current score from the target to find runs needed.
  4. Convert the remaining overs into legal balls if the display includes partial overs.
  5. Calculate the required run rate.
  6. Compare it with the team’s current scoring rate and recent scoring pace.
  7. Check how many wickets remain and which recognised batters are at the crease.

Example: Team A needs 176 to win and is 92 for 3 after 14 overs. It needs 84 runs from 36 balls. The asking rate is 14.00 per over. That is a demanding equation, but the number alone does not decide the result. A set batter, a short boundary or a favourable matchup may change the practical outlook.

2. The chasing team is ahead of its required pace

Compare the current scoring rate with the rate needed from the start of the innings. If a team has scored 80 runs in 10 overs, its current rate is 8.00. If the target is 160, it needs 80 from the remaining 10 overs, also an asking rate of 8.00. The chase is mathematically on schedule, but wickets and batting resources still matter.

A projected total can provide a simple reference:

Projected total = current score + (current scoring rate × overs remaining)

This projection assumes the current scoring rate continues. It is not a prediction and becomes less reliable when wickets fall, the pitch slows, the required matchups change or the batting order runs out of depth.

3. The chasing team is behind pace

First identify the gap between the current scoring rate and the required rate. Then check whether the team has enough balls and wickets to recover. A low asking rate with two wickets remaining can still be uncomfortable, while a higher rate with seven wickets in hand may be manageable if established batters are set.

Look at the next phase of the innings rather than assuming the team must attack every ball. Powerplay restrictions, death overs, bowler availability and the quality of the incoming batters can all influence how quickly the equation can be closed. For a reminder of how fielding restrictions shape tactics, see Cricket Powerplay and Fielding Restrictions by Format.

4. A rain interruption or shortened chase

When overs are lost, use the revised target and the revised number of overs. A shortened match is not always a simple matter of dividing the original runs needed by the new overs. If an official revised target or par score applies, use that figure first. The DLS Method in Cricket guide explains why interruption calculations require more than a basic run-rate adjustment.

Once the official target is confirmed, repeat the ordinary workflow: revised target, current score, runs needed, legal balls remaining, required rate and wickets in hand.

MeasureWhat it tells youHow to use it
Required run rateRuns needed per over from nowCalculate using runs needed and overs remaining
Current scoring rateAverage rate already achievedCompare with the asking rate, but do not treat it as a guarantee
Projected totalPossible final score if the current rate continuesUse as a reference, not a forecast
Equation pressureHow quickly the chase must accelerateAssess with wickets, batters, bowlers and match conditions
Shortened-match scenarioThe effect of fewer overs or a revised targetUse the official revised figures before recalculating

What to double-check

  • Runs needed: Confirm whether the scorecard displays the target or only the opponent’s total. A chase normally requires one more than the first-innings score, unless a competition rule or revised target applies.
  • Legal deliveries: Wides and no-balls add runs but do not use up a legal ball. Use the official balls remaining figure where available.
  • Current rate: Calculate it from runs scored divided by completed overs, converting partial overs correctly. Thirty runs from four overs and three balls is 30 ÷ 4.5 mathematically, not 30 ÷ 4.3.
  • Wickets in hand: Treat wickets as a resource, not a guarantee. Two set batters may offer more immediate security than several lower-order wickets.
  • Target changes: After rain or another interruption, wait for the confirmed target and overs before judging the chase.
  • Match phase: The same asking rate may be easier in a final-over power surge than during a difficult middle-overs spell, depending on the format and conditions.

A detailed scorecard can help you verify the inputs. If you need a refresher on overs, strike rate and innings totals, read How to Read a Cricket Scorecard.

Common mistakes

Using the opponent’s score as runs needed: The chase is measured against the target, not simply the first-innings total.

Reading 17.4 overs as a decimal: In cricket notation, 17.4 means 17 overs and four legal balls. It is 106 legal balls, not 17.4 overs in ordinary decimal arithmetic.

Ignoring wickets: A required rate is a mathematical average. It does not show whether the best batters are still in, whether a collapse is possible or whether the bowling side has exhausted its strongest options.

Projecting from one over: A 20-run over can distort the current rate. Use recent overs as context, but avoid treating a short burst as the team’s sustainable level.

Calling a chase finished too early: A large asking rate can fall quickly through boundaries, extras and efficient running. Conversely, a modest rate can become difficult after consecutive wickets.

Using the original equation after a rain break: Always check the official match centre for revised overs and target information first.

When to revisit

Recalculate the asking rate whenever the score, legal balls remaining or target changes. In a live chase, useful checkpoints include the end of each over, after a wicket, after a partnership-breaking spell, following a review or interruption, and before the final five overs.

Competition rules and interruption procedures can vary by format and tournament. Before comparing chases across seasons, confirm the over limit, tie-break provisions and any target-revision process used by that competition. For broader format context, see Test, ODI and T20 Cricket Rules Compared.

For a quick match-centre routine, save these five questions:

  1. What is the official target?
  2. How many runs are needed?
  3. How many legal balls remain?
  4. What is the required run rate compared with the current rate?
  5. How many wickets and reliable scoring options remain?

Answer those questions from the latest scorecard, then reassess after the next meaningful event. That approach keeps the required run rate useful: not as a standalone prediction, but as a live measure of the chase’s changing demands.

Related Topics

#required run rate#asking rate#run chase#limited-overs cricket#live match analysis
C

CricFizz Editorial Desk

Cricket Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.