Batting strike rate tells you how quickly a batter scores. It is expressed as runs per 100 balls faced, so a strike rate of 150 means the batter scores one and a half runs for every ball. In Test cricket it is a secondary number, but in ODIs and especially T20s it is often the first thing analysts look at. Enter runs and balls faced above to get the strike rate, runs per ball and balls per run.
How to use the strike rate calculator
- Type the runs scored by the batter. You can use a single innings, a series or a career total.
- Type the number of balls faced. Scorecards list this in the "B" column.
- The strike rate appears immediately, along with runs per ball and the number of balls the batter needs, on average, for each run.
Use the example buttons to load three famous white-ball innings and compare how fast each one was.
The strike rate formula
Strike rate = (Runs ÷ Balls faced) × 100
Multiplying by 100 turns a small decimal into an easy-to-read number. A batter who makes 45 from 30 balls scores 1.5 runs per ball, which becomes a strike rate of 150. Because there are six balls in an over, you can convert strike rate to a run rate per over by dividing by 100 and multiplying by 6. A strike rate of 150 is therefore the same tempo as 9 runs an over.
Which balls count as "faced"?
- Legal deliveries count, including dot balls and balls the batter leaves.
- No-balls count as balls faced, because the batter can hit them and score runs from them, even though the bowler must deliver the ball again.
- Wides do not count. A wide is ruled out of the batter's reach and the runs go to extras, not to the batter.
Real match example
Glenn Maxwell 201* v Afghanistan
- Runs
- 201 not out
- Balls faced
- 128
- Strike rate
- 201 ÷ 128 × 100 = 157.03
Australia were 91 for 7 chasing 292 when Maxwell took over. He finished the chase almost single-handedly, despite cramping badly, in the first ODI double century made in a run chase.
Real match example
AB de Villiers 149 v West Indies
- Runs
- 149
- Balls faced
- 44
- Strike rate
- 338.64
- Hundred reached in
- 31 balls (fastest in ODIs)
A strike rate above 300 over more than 40 balls is almost unheard of in international cricket. It shows how strike rate highlights innings that change a match in a short time.
For contrast, load Rohit Sharma's 264 against Sri Lanka at Eden Gardens in November 2014, the highest individual score in ODI history. He faced 173 balls, a strike rate of 152.60. That is slower than de Villiers, but sustained over far more deliveries, which is why strike rate should always be read alongside the size of the innings.
What is a good strike rate?
Context matters more than any single number, but broad ranges help:
- T20 cricket: around 130 is acceptable for an anchor, 140 or more is good for a top-order batter, and finishers are often expected to strike at 160 or more at the death.
- ODIs: 85 to 100 is good for a top-order batter in the modern game; over 100 is aggressive.
- Tests: 50 to 60 is typical. A high Test strike rate is a bonus rather than a requirement.
Phase of the innings also matters. Strike rates are naturally lower in the middle overs, when fielders are spread, and higher in the powerplay and the final overs.
Strike rate versus average
Strike rate measures speed; batting average measures reliability. A batter who scores 18 off 8 balls has a strike rate of 225 but has not contributed many runs. Another who scores 60 off 60 has a strike rate of 100 but has batted a long time. Neither number tells the full story alone. In T20 analysis people often multiply or plot the two together to find batters who are both quick and consistent.
Common mistakes
- Adding wides to balls faced. This makes the batter look slower than they were.
- Leaving no-balls out of balls faced. No-balls are faced by the batter, so they belong in the count.
- Comparing strike rates across formats. A Test strike rate of 70 is excellent; the same number in a T20 would usually be too slow.
- Judging a tiny sample. A strike rate built on five balls tells you very little.
Using strike rate in match situations
When a chase gets tight, strike rate turns into a target. If a team needs 60 from 36 balls, the batters need a combined strike rate of about 167. Our required run rate calculator converts that into runs per over, and the runs required for fifty or century calculator shows how many balls a batter needs to reach a milestone at their current tempo. Follow any live game on CricketSky's live scores page and check a batter's numbers against these benchmarks in real time.
