What Is a Good Strike Rate in Cricket? By Format, and By Balls Faced

Ask what is a good strike rate in cricket and most pages hand you a formula and a calculator. The formula takes ten seconds to learn. What nobody tells you is that the answer depends on two things at once: the format you are playing, and how many balls you personally have faced. Get the second part wrong and the number lies to you.

The short answer

Strike rate is runs scored divided by balls faced, multiplied by 100. A strike rate of 100 means you are scoring a run a ball. What counts as good depends entirely on format: roughly 125 to 150 is solid for a T20 batter, around 85 to 95 is respectable for an ODI top-order batter, and 50 to 60 is perfectly normal in Test cricket. In short formats the number matters more, because there are fewer balls left to fix a slow start.

The formula, once

Batting strike rate = (runs scored / balls faced) x 100

Face 20 balls, score 30 runs, and your strike rate is 150. Face 20 balls and score 12, and it is 60. That is the whole calculation. You do not need a calculator page for it.

The useful part is what the number is actually measuring. Strike rate measures the price of the balls you use up. Batting average measures how long you survive. They answer different questions, and in a short format the first one usually decides the match.

What is a good strike rate in cricket, by format

Benchmarks move over time as bats get better and fields get more aggressive, so treat these as ranges rather than targets carved in stone.

Test cricket

50 to 60 is standard for a specialist batter
Under 40 is slow but can be exactly right when the job is to bat out a session
Above 70 over a long career is genuinely aggressive

Here, strike rate is almost a side note. Time is the resource being spent, not balls.

One-day cricket

85 to 95 is a solid top-order rate
100 or higher marks you as a genuine accelerator
Under 75 needs a reason, usually a collapse you are rebuilding from

T20 and shorter

125 to 150 is the working range for most batters
Above 150 is finisher territory
Under 110 in a T20 innings of any length is usually costing the team more than the runs are worth

This is the band most people mean when they ask what is a good strike rate in cricket, because T20 is what most people watch.

The part the calculator pages leave out

Strike rate is a rate, and rates are unreliable over small samples. Face six balls, hit one four, and your strike rate reads 66. Hit two, and it reads 133. Nothing about your batting changed between those two innings. One extra boundary did.

That matters enormously in short-format matches. In a 5 over game you get 30 balls in the innings, split between two batters if you are playing a team format, or all 30 to yourself in a 1v1. Your strike rate at the end of that is a measurement of about a dozen decisions. Treat it as a score, not as a diagnosis.

The number becomes meaningful somewhere north of a few hundred balls faced. Below that, it is noise wearing a decimal point.

The number to watch instead: required rate per ball

Mid-innings, your own strike rate is the wrong thing to be looking at. The right thing is what the chase still demands. Divide the runs you still need by the balls still left, and multiply by 100. That is the strike rate the situation is asking for, and it updates every single delivery.

Here is why short formats punish dot balls so hard. Take a chase of 45 from 5 overs:

You need 45 from 30 balls, a required strike rate of 150
You play a dot ball
Now you need 45 from 29 balls, a required rate of 155

One dot pushed the requirement up by five points. Now run the same arithmetic in a 20 over chase of 160 from 120 balls. That is a required rate of 133. One dot ball makes it 134. Same mistake, one fifth of the damage.

The practical rule that falls out of this:

5 overs: a dot ball is close to a wicket. Rotate strike or take the risk, but do not defend.
10 overs: you can afford roughly one dead over. Not two.
20 overs: you have room to build. Spend the first two or three overs learning the bowler.

You can test all three of those in a live match when you play cricket online at howzatlive.com, because the game runs 5, 10 and 20 over formats and the same opponent bowls very differently across them.

Bowling strike rate is a different number

If someone tells you their strike rate is 18 and they are a bowler, they are not talking about runs at all.

Bowling strike rate is balls bowled per wicket taken, and lower is better. A Test bowler taking a wicket every 50 balls is doing well. In T20, a wicket every three overs, which is a strike rate of 18, is a strong return in a format where you only bowl four.

It is worth knowing both definitions, because commentary switches between them without warning and the two numbers move in opposite directions. High is good for a batter. Low is good for a bowler.

How to actually raise your strike rate

Chasing a higher number by swinging harder is the fastest way to a worse one, because a wicket ends the innings and the balls you would have faced go to nobody. Three things move the number without raising your risk much:

Cut out the dot ball, not the defensive shot. A pushed single off a good delivery is worth more than a flashy four two balls later, because it keeps the rate from climbing while you wait for a bad ball.
Pick one scoring area and commit early. Batters with low strike rates are usually deciding late, not swinging late. Decide before the bowler releases and adjust, rather than starting the decision when the ball is already halfway down.
Attack the bowler's fourth and fifth ball. Bowlers tighten at the start of an over and leak at the end of it, especially when they are trying to protect a plan that has not worked.

None of that is theory you have to take on faith. Play a short format against a real person and watch what happens to your rate when you stop defending the good balls and start refusing the dots. The honest version of what is a good strike rate in cricket, for you specifically, is whatever beats the required rate in front of you without getting you out.

Where to practise it

At howzatlive.com you play a live 1v1 against another real person in your browser. One of you bats, one of you bowls, and you pick 5, 10 or 20 overs, day or night conditions. There is nothing to download and nothing to pay for. You can jump into a quick match against whoever is waiting, or send a private link to a friend and settle it between the two of you, with chat running during the match.

If you would rather grind the mechanics before facing a human, there are three bots to bowl at you: Gully, Club and Academy. Bot results count at half weight, are capped at a few per day, and will carry you no higher than Scale 3. Everything above that needs real opponents.

Speaking of which, the Scale badge runs 0 to 10 and appears after five rated matches. Beating stronger opponents moves you up faster, and playing the same person repeatedly counts for less each time. Create a free account to start a rated record, or look at the leaderboard to see what the top of the Scale actually looks like before you set yourself a strike rate target.

More breakdowns like this one are on the blog, and if something here does not match what you are seeing in your matches, contact us and tell us.