Why a Batting Average Matters More Than Century Count
A high batting average (runs divided by dismissals) is more meaningful than a high century count because it measures consistent contribution across all innings — not just peak performances. This guide explains what batting average tells you, what it misses, and how analysts use context (format, era, conditions) to compare across generations.
Batting average = total runs scored ÷ total times dismissed. A batsman who scores 50, 80, 70, and 0 has a batting average of 50.00 — the same as someone who scores 200 and 0, 0, 0. The century count (3 vs 1 in this example) favours the 200-run scorer, but the batting average correctly identifies them as equivalent in contribution. This is why analysts prefer batting average to century count as a primary career metric — it measures the sum of all contributions, not the number of peak performances.
What Batting Average Misses
Batting average has important blind spots: it does not account for not-out innings (a batsman with many not-outs — number 10 or 11 in the order — can inflate their average by never batting long enough to get out); it does not account for conditions (averaging 50 on subcontinental pitches vs English green-tops reflect very different skills); it does not account for era (batting averages in the 1950s were lower across the board because pitching conditions were less protective of batsmen than in the 2010s); and it does not differentiate between innings of different value (a 50 in a run chase of 51 is more valuable than a 50 when the team needs 400).
Context-Adjusted Comparisons
Analysts use several adjustments for era and conditions: comparing to the average of all batsmen in the same period (a player averaging 55 in a period where the average is 40 is performing 37.5% above average — more impressive than averaging 55 when the average is 52); home vs away splits (many batsmen have drastically higher home averages than away); and format-specific benchmarks (a T20 batting average of 35 is elite, while an ODI average of 35 is respectable but not exceptional, and a Test average of 35 is considered ordinary for a specialist batsman). The context matters more than the raw number.
Century Count as a Supplement
Century count is most useful as a supplement to batting average rather than a replacement: a player with average 45 and 20 centuries is performing differently from a player with average 45 and 5 centuries — the first player is winning matches at higher frequencies (centuries typically correlate with team wins in Tests) while the second is contributing more steadily. The ideal combination: high average AND high century conversion rate (the % of 50s converted into 100s). Elite batsmen typically convert 40-50% of fifties into hundreds — they do not just stop at 50 but continue to match-defining contributions.
Frequently asked questions
What is a good batting average in cricket?
In Test cricket, 50+ is considered elite (only ~15 players in history have achieved it over a long career); 45-50 is very good; 40-45 is solid for a specialist batsman; below 35 is considered below standard for a recognised Test batsman. In ODIs: 45+ is elite; 35-45 is good; below 30 is considered poor for a specialist. In T20Is: 30+ is elite; 25-30 is good; below 20 is below average. The threshold differs because T20 has more not-outs and lower typical scores — the format's stats require different benchmarks than longer formats.
Who has the highest batting average in Test cricket history?
Don Bradman (Australia) holds the all-time Test batting average record at 99.94 across 52 Tests and 80 innings (6,996 runs). This is considered the greatest statistical outlier in any professional sport — the second-highest career average (Graeme Pollock, 60.97) is nearly 39 runs per innings lower. To put Bradman's average in perspective: if he had scored a duck in his final Test innings (he needed 4 runs to average 100.00), his average would still be 99.94 — he made 0 from 2 balls. Bradman is so far ahead of all other batsmen that his average is used as cricket's benchmark for perfection.
What is the difference between batting average and strike rate?
Batting average (runs ÷ dismissals) measures how many runs a batsman contributes per innings — it rewards consistency and longevity. Strike rate (runs ÷ balls × 100) measures how quickly a batsman scores — it rewards efficiency and tempo. In Test cricket, average is the primary metric (time is less constrained, contribution per innings matters most). In T20 cricket, strike rate is equally or more important than average (scoring quickly creates wins; a slow 50 can be less valuable than a fast 30). The ideal batsman maximises both — elite T20 batsmen (Suryakumar Yadav, 150+ strike rate at a reasonable average) and elite Test batsmen (Steve Smith, 58+ average with consistent contribution).