Run Rate in a Chase: How Teams Calculate and Track Their Target
Chasing a target in limited-overs cricket involves constant run rate calculation — teams must know at each stage of the innings whether they are ahead of or behind the required run rate. This article explains run rate and required run rate, how teams track their chase position in real time, and the tactics that help chasing teams succeed.
Current Run Rate vs Required Run Rate
Two key metrics govern a chase: current run rate (CRR) — runs scored so far ÷ overs bowled so far; and required run rate (RRR) — runs still needed ÷ overs remaining. A team chasing 250 from 50 overs that has scored 100 from 20 overs has a CRR of 5.0 (100÷20) and needs 150 from 30 overs, giving an RRR of 5.0 (150÷30). When CRR equals RRR, the team is exactly on pace. When RRR exceeds CRR, the team is behind the chase; when CRR exceeds RRR, they are ahead. Both metrics are displayed continuously in stadium scoreboards, television graphics, and on mobile scoring apps — they are the primary real-time chase management tools for batsmen, team management, and tactical decision-making.
The Chase Management Approach
Successful chasing teams use a 'pace milestones' approach: at specific over milestones (10, 20, 30, 40 overs for a 50-over chase), the team checks whether their score matches their target score for that checkpoint. A team chasing 250 targeting 50 from the first 10 overs, 100 from 20, 160 from 30, 210 from 40, and 250 from 50 overs is executing a linear chase — matching the required run rate throughout. In practice, chases are rarely perfectly linear: the powerplay (overs 1-10) often produces above-average scoring (boundaries from the field restrictions), the middle overs (11-40) may be more contained, and the death overs (41-50) produce another scoring surge. Teams exploit powerplay field restrictions to build early momentum, then manage through the middle overs with rotation and targeted boundaries, before attacking in the death.
The Critical 10-Over Window
In most chases, the momentum shifts decisively in one specific 10-over window. In a 50-over chase: if the chasing team is within 10-15 runs of their linear target at the 30-over mark, the death-over specialists in their batting lineup can likely win the match. If they are 25+ behind at the 30-over mark, the required rate in the death overs becomes very high (10+ per over) and the fielding team sets defensive boundary-protection fields that make it even harder. The critical moment: recognising at what point in the innings a realistic target becomes unrealistic. Elite chasing teams maintain hope and tactical aggression until the required rate exceeds approximately 15 per over with less than 10 overs to go — at that point the mathematical probability of success drops below any reasonable threshold.
Frequently asked questions
What required run rate is considered 'very difficult' to achieve?
A required run rate of 10+ runs per over for more than 10 overs is considered very difficult even for elite T20-era batting lineups. Sustaining 10 runs per over means averaging a boundary every 2-3 balls, consistently — which requires above-average boundary frequency against a bowling attack also setting boundary-protection fields. A required rate of 12-13 per over for 10 overs (needing 120-130 from 60 deliveries) represents the upper boundary of realistic possibility in most match contexts. Beyond 15 per over, successful chases are exceptional and typically require dropped catches, wide balls, and no-balls that inflate the scoring rate beyond what the batting team generates through shot-making alone.
How does the DLS method affect run rate calculations in rain-affected chases?
When a chase is interrupted by rain and the Duckworth-Lewis-Stern (DLS) method is applied, the target score is recalculated based on the overs lost and the team's 'resources' (wickets and overs remaining) at the point of interruption. The new target replaces the original — so the run rate and required run rate calculations start fresh from the revised target and revised overs. A team that was comfortably on track before a rain break may find they are behind the new DLS target if the interruption reduces the total overs by a fixed number (the DLS target in a rain-reduced chase accounts for the resources removed from both teams). Conversely, if the match resumes with fewer overs but the same target, the required run rate increases significantly.
What is 'asking rate' and how does it differ from required run rate?
'Asking rate' and 'required run rate' are used interchangeably by most commentators and analysts — both mean the runs per over that the chasing team needs to score from the remaining overs to win. Some commentators use 'asking rate' more loosely to describe the early-chase requirement at the start of the innings (the target divided by total overs = initial asking rate of 250÷50 = 5.0) and 'required run rate' as the dynamic metric that updates each over. In practice, the distinction is rarely meaningful — both terms refer to the same calculation, and cricket broadcasts display it as a single number that updates after each over.