Batting Average vs Strike Rate in Cricket Explained: Which Matters More?

Two numbers define a batsman's performance: batting average (total runs divided by number of dismissals) and strike rate (total runs divided by balls faced, multiplied by 100). In Tests: average is the primary metric (how many runs do they score before getting out). In T20 cricket: strike rate is the primary metric (how quickly do they score). In ODIs: both matter — average reflects consistency; strike rate reflects pace. The 'debate' between average and strike rate is cricket's equivalent of WAR vs batting average in baseball — which composite of batting skill matters most.

Batting Average: The Test Cricket Standard

Batting average = total runs / innings dismissed. A not-out innings adds to runs scored but does NOT count as a dismissal — this means a batsman who is often not-out (tail-enders who are frequently stranded, or batsmen who declare while not-out) can have inflated averages. Typical Test averages by position: Opening batsmen (positions 1-2): 35-45 is considered average; 45+ is very good; 50+ is exceptional. Middle-order (positions 3-5): 40-50 average; 50+ exceptional. All-rounders (6-7): 30-40; below 30 is specialist bowling value. Why average is the right Test metric: in Tests, the primary goal of a batsman is to stay in and score as many runs as possible in each innings. A batsman who averages 45 — scoring 45 runs every time before being dismissed — is contributing substantial defensive and attacking value regardless of how quickly they score. Steve Smith (average 60+), Virat Kohli (average 50), and Joe Root (average 58) define what exceptional Test averages look like.

Strike Rate: The T20 Standard

Strike rate = (runs / balls faced) × 100. A strike rate of 100 means 1 run per ball; 150 means 1.5 runs per ball. Typical T20I strike rates by context: powerplay hitters (positions 1-2): 130-160 is average; 160+ exceptional. Middle-order (positions 3-5): 130-150 is good; 150+ aggressive. Finishers (6-8): 150+ necessary; 180+ elite. Why strike rate is the right T20 metric: in T20 cricket, you have 20 overs (120 balls for 10 wickets) — scoring rate per ball is directly constrained by the finite balls available. A batsman who averages 45 but scores at SR 100 costs 45 balls per 45 runs — effectively allowing other team's bowlers to contain scoring. A batsman who averages 25 but scores at SR 180 contributes 25 runs in 14 balls — providing the same run rate contribution in a fraction of the balls.

Impact Metrics: Beyond Average and Strike Rate

Cricket analytics (following baseball's sabermetrics influence) has developed 'impact' metrics that combine average and strike rate: (1) Runs Above Replacement (RAR) — how many more runs does this batsman contribute compared to a 'replacement-level' player in the same position; (2) Win Probability Added (WPA) — how much did this batsman increase their team's win probability with their innings; (3) Expected Runs vs Actual Runs — given the match situation (balls remaining, wickets down, run rate required), how much better/worse than expected was the innings. These metrics are used by all IPL franchise analytics teams but are rarely published publicly. The limitation of standard average and strike rate: they don't account for match context (a 30-run innings in a chase of 185 with 3 overs remaining is worth more than a 30-run innings in a completed 400-run total).