Batting strike rate
The formula is runs scored divided by balls faced, multiplied by 100. A batter who makes 45 from 30 balls has a strike rate of 150. A strike rate of 100 means exactly a run a ball; below 100 means slower than a run a ball. Balls faced includes no-balls but excludes wides, because a wide is not considered a delivery the batter could play.
Two quick examples from a T20 scorecard: 27 from 18 balls is a strike rate of 150.00; 62 from 50 is 124.00. Broadcasters usually show it as "SR" next to the batter's name.
What counts as a good batting strike rate
There is no single answer; it depends entirely on the format and on the batter's role. The figures below are approximate career benchmarks for well-known Indian players and are meant as a guide rather than a leaderboard.
| Format | Solid | Aggressive | Example |
|---|---|---|---|
| Test cricket | 45–55 | 70+ | Rishabh Pant, roughly 73 |
| ODI | 85–95 | 100+ | Virat Kohli, roughly 93 |
| T20 International | 125–140 | 150+ | Suryakumar Yadav, roughly 165 |
| IPL death overs | 150 | 180+ | Hardik Pandya, Tim David |
Context changes everything. A powerplay batter facing two fielders outside the circle is expected to score faster than a number five who arrives at 40 for 3. Analysts increasingly split strike rate by phase — powerplay, middle overs, death — because a career figure hides those differences.
Strike rate versus batting average
Batting average is runs scored divided by the number of times the batter has been dismissed. Average measures how many runs you can expect; strike rate measures how fast they arrive. The two often pull against each other. A batter averaging 50 at a strike rate of 120 is a classic "anchor". A batter averaging 28 at a strike rate of 165 is a "finisher". Neither is better in the abstract: a T20 side needs both, and a Test side cares far more about the average.
Bowling strike rate
For bowlers the formula flips: balls bowled divided by wickets taken. It tells you how many deliveries a bowler needs, on average, for each wicket, so a lower number is better. Jasprit Bumrah's Test strike rate of around 42 is exceptional; anything under 50 in Tests is elite. In ODIs, a strike rate in the low 30s is very good, and in T20s a figure in the mid-teens marks out a genuine wicket-taker.
| Bowling measure | Formula | What it tells you |
|---|---|---|
| Economy rate | Runs conceded ÷ overs bowled | How expensive each over is; the key T20 number |
| Bowling average | Runs conceded ÷ wickets | Cost of each wicket; the key Test number |
| Bowling strike rate | Balls bowled ÷ wickets | How often wickets fall; useful in every format |
Worked example from one T20 innings
A bowler's figures read 4-0-28-2: four overs, no maidens, 28 runs, two wickets. Economy is 28 ÷ 4 = 7.00. Average is 28 ÷ 2 = 14.00. Strike rate is 24 balls ÷ 2 = 12.0. Meanwhile the top scorer made 72 from 44 balls, a strike rate of 163.64. Read together, the bowler was cheap and dangerous; the batter was fast and decisive.
Strengths of strike rate
- Simple to calculate and compare
- Shows tempo, which averages ignore
- Becomes very revealing when split by phase
Limitations
- Ignores match situation and pitch conditions
- Small samples swing wildly (one 20-ball cameo)
- Rewards risk without recording how often it fails
Where you will see it on screen
Batting scorecards show a score such as "72 (44)" — runs first, balls in brackets — and often the strike rate beneath. Bowling cards show overs-maidens-runs-wickets, with economy alongside. The next time a commentator says a player is "going at 150", you will know they mean one-and-a-half runs per ball, and you will be able to judge for yourself whether that is remarkable or simply what the situation demanded.