Batting Strike Rate Calculator

What the batting strike rate calculator does

Strike rate is how fast a batsman scores, and in the shorter formats it matters almost as much as how many runs they make. This tool works it out. You give it the runs a batsman scored and the balls they faced, and it returns the strike rate, which is runs scored per 100 balls.

Where a batting average tells you how many runs a player tends to make, strike rate tells you how quickly they make them, and the difference between those two questions is most of what this page is about.

How to use it

1. Enter the runs scored. The batsman's runs in the innings, or across a series.
2. Enter the balls faced. The number of deliveries they faced to score them.

Press Calculate for the strike rate, or Reset to clear the boxes.

How strike rate is worked out

You divide runs by balls and multiply by a hundred:

Strike rate = (runs ÷ balls) × 100

The times-a-hundred is what makes it read as runs per 100 balls, which is a tidy scale to compare players on. A strike rate of 100 means a run a ball. Above that, the batsman is scoring faster than a run a ball, below it, slower.

An example with real numbers

Say a batsman makes 75 off 50 balls.

• Strike rate = (75 ÷ 50) × 100 = 150

A strike rate of 150 means they are scoring 150 runs for every 100 balls, or one and a half runs a ball. In a T20 that is a seriously good knock. In a Test match, facing 50 balls for 75 would be reckless rather than impressive, which brings us to the thing that makes strike rate easy to misread.

Strike rate means nothing without the format

This is the part to hold on to. The same strike rate can be brilliant or poor depending on which kind of cricket is being played, because each format is a different trade-off between speed and survival.

In a T20, scoring is everything. Openers often aim for a strike rate of 130 to 150, and a finisher swinging at the death might push past 180. In a 50 over game there is more time to build, so a strike rate in the 85 to 95 range is a healthy tempo for most batsmen. In a Test match, where a player can bat for a day, a strike rate of 50 to 60 is perfectly good, because the job there is to occupy the crease and wear the bowlers down, not to blaze away. So before you judge a strike rate, ask which format it came from.

Strike rate versus average, two different questions

People sometimes treat strike rate and batting average as if they measure the same thing, but they answer completely different questions. Average is how many runs a batsman tends to score before getting out, the total runs divided by the times dismissed. Strike rate is how fast they score while they are there. A player can have a high average and a low strike rate, the patient accumulator who bats forever, or a high strike rate and a modest average, the explosive hitter who comes off half the time. The complete batsman has both, and the two figures together tell you far more than either one alone.

Questions people ask

How do you calculate batting strike rate?

Divide the runs scored by the balls faced and multiply by 100. So 60 runs off 40 balls is a strike rate of 150.

What is a good batting strike rate?

It depends on the format. Around 130 or more is good for a T20 batsman, roughly 85 to 95 in one-day cricket, and 50 to 60 is fine in Tests, where occupying the crease matters more than speed.

What does a strike rate of 100 mean?

It means the batsman is scoring at exactly a run a ball, 100 runs for every 100 balls faced. Above 100 is faster than a run a ball, below 100 is slower.

Is strike rate the same as batting average?

No. Average is how many runs a batsman makes per dismissal, a measure of how much they score. Strike rate is how fast they score while batting. A strong batsman is judged on both together.