Cricket Run Rate, Economy Rate, and Strike Rate Explained: Formulas and What Good Values Look Like
Run rate, economy rate, and strike rate are three essential metrics for analysing batting and bowling performance in cricket. Run rate (runs per over for a team) measures scoring tempo; strike rate (runs per 100 balls for a batsman) measures individual scoring speed; economy rate (runs conceded per over for a bowler) measures a bowler's cost. Each metric has different benchmarks depending on the format — Test, ODI, or T20 — and understanding these thresholds is essential for analysing match situations, selecting players, and comparing performances across eras.
Three rate-based metrics dominate cricket statistical analysis: run rate (for a team's scoring tempo), batting strike rate (for an individual batter's scoring speed), and economy rate (for a bowler's cost per over). Each uses a simple formula, but the benchmarks for what constitutes a 'good' value differ substantially across Test cricket, ODI cricket, and T20 cricket — and have also shifted across eras as the game's pace has accelerated.
Run Rate and Required Run Rate
Run rate = total runs scored ÷ overs bowled. A team scoring 240 from 40 overs has a run rate of 6.00. Required run rate (RRR) is the run rate needed to win from a given point: (runs needed) ÷ (overs remaining). If a team needs 120 from 15 overs, the RRR is 8.00. In ODIs, a run rate of 5.0–5.5 is a reasonable first-innings platform; 6.0+ in 50-over cricket represents a fast innings. In T20 cricket, teams average 7.5–8.5 per over across a full innings; a required run rate above 12 per over is considered very difficult to achieve. Net Run Rate (NRR) for tournament standings is calculated as (total runs scored ÷ total overs faced) minus (total runs conceded ÷ total overs bowled across all group matches), providing a tie-breaker between teams with equal points.
Batting Strike Rate and Economy Rate
Batting strike rate = (runs scored ÷ balls faced) × 100. A batter who scores 60 from 80 balls has a strike rate of 75.0. In Test cricket, a strike rate of 50–60 is considered normal; 70+ is aggressive. In ODIs, 80–90 is solid for a middle-order batter; 100+ is excellent for top-order batters in the second half of the innings. In T20 cricket, a strike rate below 120 from a specialist batter is considered slow; 140–160 is the target for most positions. Economy rate for bowlers = runs conceded ÷ overs bowled. A bowler who concedes 35 from 7 overs has an economy rate of 5.00. In Tests, an economy rate below 3.00 is excellent (Muttiah Muralitharan career: 2.19); in ODIs, below 5.00 is elite; in T20 cricket, below 7.00 is considered economical, with sub-6.00 being outstanding.
Frequently asked questions
How do run rate, strike rate, and economy rate interact during a match analysis, and what do they reveal that raw totals alone do not?
Raw totals — a team's final score or a bowler's wicket count — conceal much of what actually happened in a cricket match. Rate-based metrics reveal the tempo, efficiency, and context of a performance in ways that final totals cannot. Consider a team that scores 280 in a 50-over ODI. If they reached 280 from 50 overs at a run rate of 5.60, that is a reasonable but not exceptional score. But if the first 25 overs were bowled at an economy rate of 4.0 (conservative field with attacking bowling restricting the batting side to 100 runs), and the last 25 overs were bowled at an economy rate of 7.2 (batting team accelerated against defensive bowling), the match has a very different story: the bowling side was dominant early, then the batting side recovered. A flat total of 280 says nothing about this narrative. From the batting perspective: a team that reaches 280 with two batters scoring 100 each at a strike rate of 60 (conservative, time-consuming) has played a completely different innings from a team reaching 280 with five batters scoring 50+ each at strike rates of 85–100 (aggressive, attacking, less dependent on any single partnership). The required run rate calculation is perhaps the most tactically important in-match metric. A team chasing 280 needs exactly 5.60 per over for 50 overs. If they score at 4.80 through the first 25 overs (having lost two wickets), they need 7.60 from the last 25 — a substantial increase that puts enormous pressure on the remaining batters. The required run rate clock tells both teams precisely how far ahead or behind the chase is at every point. Economy rate in T20 cricket is arguably more important than wickets in bowling evaluation. A bowler who takes 2 wickets for 45 from 4 overs (economy 11.25) has been far more damaging to his team than a bowler who takes 0 wickets for 20 from 4 overs (economy 5.00) — the wickets came too expensively. Modern T20 bowling analysis uses economy rate as the primary metric, with wickets as a secondary consideration that explains particularly valuable overs.