Batting Strike Rate vs Average — Which Matters More in Cricket?
When should you prioritise batting average and when does strike rate matter more? A format-by-format breakdown with benchmarks for Tests, ODIs, and T20Is.
Batting average (runs per dismissal) and strike rate (runs per 100 balls) are the two most cited batting statistics in cricket. The tension between them defines batting strategy across formats — in Test cricket, average is king; in T20 Internationals, strike rate can matter more than average for aggressive middle-order batters.
What Each Metric Tells You
- Batting average: measures how often and how many runs a batter scores before being dismissed. High average = hard to get out, consistently scores large innings.
- Strike rate: measures how fast a batter scores. High strike rate = scores quickly, potentially at the cost of getting out more.
- Neither metric alone is sufficient: a batter averaging 45 at a strike rate of 30 in T20 is a liability; a batter averaging 15 at a strike rate of 200 in Tests is equally problematic.
In Test Cricket: Average Dominates
Tests have no over limit on innings. A team can bat for two days if needed. The primary objective is to score as many runs as possible before being dismissed — which makes average the primary metric. Strike rate is secondary: batters with averages above 45 are elite regardless of strike rate, though extremely low strike rates (below 35) attract criticism for occupying the crease without scoring.
In ODI Cricket: Balance Is Key
ODIs are 50 overs per side. A top-order batter has roughly 25–40 overs to score. Here, average and strike rate need to be in balance. A batter averaging 45 at a strike rate of 85 is ideal; averaging 55 at a strike rate of 60 means they take up deliveries without scoring fast enough — problematic in the final 15 overs when 120+ run rate is needed.
In T20 Cricket: Strike Rate Is Primary
A T20 innings is 20 overs. A batter faces between 10 and 35 balls. In this context, strike rate is the primary value metric — a player scoring 25 off 10 balls (SR 250) contributes enormously even with a career average of 20. Modern T20 analysis uses Impact (runs above par) and boundary percentage alongside raw strike rate to capture a batter's true value.
| Format | Primary Metric | Good Average | Good Strike Rate |
|---|---|---|---|
| Test | Average | 40+ | 50+ (secondary concern) |
| ODI | Both balanced | 35+ | 85+ |
| T20I | Strike Rate | 25+ | 130+ |
Frequently asked questions
What is a good batting strike rate in T20 cricket?
A strike rate above 130 is considered acceptable for international T20 cricket; above 150 is very good; above 170 is elite. Context matters — a No. 3 batsman anchoring the innings at 130 is valuable; a designated finisher at No. 7 should be scoring at 180+.
Can you have a high average and low strike rate in Tests?
Yes — and it is not necessarily a problem. Steve Waugh averaged 51 in Tests at a strike rate around 48, which was considered perfectly acceptable for the era and format. Extreme cases like defensive openers averaging 30 at a strike rate of 30 do attract criticism for not scoring fast enough.
What is batting impact in cricket?
Batting impact is an analytical metric that compares a batter's actual contribution to the expected score given the match situation. It accounts for wickets in hand, overs remaining, required run rate, and opponent quality — giving a more context-aware measure than raw average or strike rate.