Batting Average vs Strike Rate: Which Matters More?
The debate between batting average and strike rate as measurements of a batsman's value — why average captures survival better than impact, why T20 made strike rate more important, the combined Expected Runs metric, format-specific benchmarks, and why neither single stat is sufficient to evaluate a player.
What Each Statistic Measures
Batting average (runs divided by dismissals) measures how many runs a batsman scores before they are out — it captures the quality of survival and accumulation over a career or series. A high average indicates a batsman rarely gets out cheaply and scores substantial totals when they bat. Strike rate (runs scored per 100 balls) measures the pace of scoring — how efficiently a batsman converts their balls into runs. A high strike rate indicates a batsman scores more aggressively relative to the balls they face.
In Tests, average has historically been considered the primary measure of batting quality because the format rewards survival — a batsman who averages 50 is producing 50 runs per innings on average, which cumulatively builds large team totals. In T20 cricket, strike rate is the primary measure because an over has a fixed 6-ball allocation — a batsman who averages 35 but scores at 100 per 100 balls contributes less per over than one who averages 20 but scores at 180 per 100 balls.
The Format Shift
The rise of T20 cricket from 2007 onward exposed the average's limitations as a sole measure. Several Test cricketers who averaged 45+ in Tests scored at 115 per 100 balls in T20s — excellent by traditional averages but below the 130+ expected of an elite T20 opener. Conversely, some T20 specialists averaged only 18-20 (dismissed quickly without ever building a large innings) but scored at 160+ per 100 balls — contributing more runs per over than their average suggested.
ODI cricket sits between the two extremes: ODI average and strike rate are both tracked and both relevant. A batsman who averages 40 at 90 per 100 balls is considered a conservative middle-order player; one who averages 35 at 110 per 100 balls is considered an aggressive match-winner. The ODI 'ideal' — debated by analysts — is approximately average 38-42 with a strike rate of 95-105 for a number 3-5, or average 32-38 with a strike rate 115-125 for a specialist finisher.
Combined Metrics: Expected Runs
Analytics providers have developed combined metrics that attempt to capture both dimensions simultaneously. CricViz's 'Batter Impact' metric calculates a batsman's contribution to their team's expected margin of victory per innings. ESPNcricinfo's 'All-format batting index' weights average and strike rate by format importance. The simplest combined metric is 'expected runs' — the mathematical expected value of the runs a batsman produces per innings when both their average (frequency of scoring large) and strike rate (runs per ball) are combined into a single number.
Format-Specific Benchmarks
As rough benchmarks for elite performance: Test batting — average 40+ is solid international quality; 50+ is exceptional; 55+ is historically elite. Strike rate in Tests is secondary but Bazball-era England expects 55+ per 100 balls from the top 6. ODI batting — average 35+ and strike rate 90+ is solid; average 40+ and 100+ is elite for top 4. T20I batting — strike rate 130+ is minimum for a specialist T20 batter; 145+ is elite-level; average matters less but 20+ is preferable. A T20 batsman who averages 25 at 160 is typically more valuable than one who averages 40 at 120.
Frequently asked questions
Why is the batting average calculated on dismissals rather than innings?
Batting average divides total runs by dismissals (not innings) to avoid penalising batsmen for not-out innings. If a batsman scores 50 in 10 innings but 4 of those were not-out scores (no dismissal), their average is 50 runs / 6 dismissals = 8.33 — not 50/10 = 5.0. The not-out exclusion is particularly important for batsmen who often bat in match-winning situations (lower-order players who finish the innings undefeated) and inflates averages for players in winning teams who frequently bat out the final overs.
Can a batsman have a high strike rate and a low average simultaneously?
Yes — aggressive openers in T20 cricket often have this profile: they score quickly (high strike rate) but are frequently dismissed early (low average). The trade-off is acceptable in T20 because the runs scored at high strike rate during their brief innings contribute more per ball than a more cautious player's longer, lower-rate innings. In Test cricket, a high strike rate-low average combination typically indicates a tail-ender who occasionally hits aggressively before being dismissed — the profile is not considered elite.
What is the highest batting average in Test cricket history?
Don Bradman's 99.94 is the highest Test batting average in history — nearly double the average of the next best players (Adam Voges and Herbert Sutcliffe at approximately 56-57). Bradman's average is considered so statistically aberrant relative to other players (his average is approximately 40 runs per innings above the field) that statisticians have produced papers arguing it is the most extreme statistical outlier in professional sport across any measurable dimension.