Strike rate means two opposite things in cricket, and the two are not related. A batter’s strike rate is runs scored per 100 balls faced, and higher is better. A bowler’s strike rate is balls bowled per wicket taken, and lower is better.
| Strike rate | Formula | Reads as | Better when |
|---|---|---|---|
| Batting | (runs ÷ balls faced) × 100 | Runs per 100 balls | Higher |
| Bowling | balls bowled ÷ wickets | Balls per wicket | Lower |
How to calculate batting strike rate
Divide the runs by the balls faced, then multiply by 100. It works the same for a single innings or a whole career.
Single innings. A batter makes 125 from 62 balls. 125 ÷ 62 = 2.0161, × 100 = a strike rate of 201.61.
Whole career. Virat Kohli has 14,941 ODI runs from 15,903 balls. 14,941 ÷ 15,903 = 0.9395, × 100 = 93.95, which is exactly the figure on his profile.
What counts as good depends entirely on the format. A strike rate in the 50s can be an excellent Test innings on a difficult pitch; the same number in a T20 is a problem. That is why the figure is never read on its own.
How to calculate bowling strike rate
Divide the balls bowled by the wickets taken. There is no multiplication step, and the answer is a count of deliveries, not a percentage.
Single innings. A spinner bowls 14 overs and takes two wickets. That is 84 ÷ 2 = a strike rate of 42.
Whole career. Shane Warne took 708 Test wickets from 40,705 balls. 40,705 ÷ 708 = 57.49 balls per wicket.
⚠️ Look that figure up and you will see 57.4, not 57.5. That is not an error and it is worth knowing why: cricket statistics are conventionally truncated to one decimal place, not rounded. The same thing happens right down the list — Glenn McGrath’s 29,248 balls for 563 wickets is 51.95, shown as 51.9; Mitchell Starc’s 20,313 for 445 is 45.65, shown as 45.6. If your own calculation ends in a 5 and the published number looks a tenth low, this is why.
Bowling strike rate is a Test statistic first
The two strike rates matter in opposite formats, which is the part most explanations skip.
In Test cricket a bowler’s job is to take twenty wickets, so balls per wicket is the number that decides selection — runs conceded along the way matter much less. In T20 and ODI cricket a bowler can be genuinely valuable without taking a wicket at all, provided they keep the scoring down, so economy rate carries more weight.
Strike rate versus economy rate
These get confused constantly. Economy rate is runs conceded per over: runs ÷ (balls ÷ 6). It says nothing about wickets, and strike rate says nothing about runs.
Warne’s Test career shows both: 17,995 runs from 40,705 balls is 6,784.2 overs, so 17,995 ÷ 6,784.2 = an economy rate of 2.65, alongside that strike rate of 57.49. Starc, by contrast, strikes far more often — 45.65 balls per wicket — while going at 3.43 an over. One bowler is harder to score off; the other takes wickets faster. Neither number tells you that on its own.
Strike rate in cricket: quick answers
What is strike rate in cricket? For a batter, runs per 100 balls faced. For a bowler, balls bowled per wicket.
How do you calculate batting strike rate? (runs ÷ balls faced) × 100.
How do you calculate bowling strike rate? balls bowled ÷ wickets taken. No multiplication.
Is a high strike rate good? For a batter, yes. For a bowler, no — a lower bowling strike rate means quicker wickets.
What is the difference between strike rate and economy rate? Strike rate counts balls per wicket; economy rate counts runs per over. A bowler can be excellent at one and ordinary at the other.
Why does my calculation not match the published figure? Cricket statistics are truncated to one decimal place rather than rounded, so a result of 57.49 is published as 57.4.
More cricket terms explained: what a dot ball is, what extras are and what a par score means.
Follow us on Telegram for the latest updates from the world of sports!
Interested in cricket betting? Click here to check out the list of top sites.
Author: William Paul
Featured photo: AFP / PUNIT PARANJPE