What Is Strike Rate in Cricket? Batting & Bowling Explained

Ask a commentator to name one number that separates a Test blocker from a T20 finisher, and they’ll say strike rate. Confusingly, the same term covers two completely different jobs. For a batter, it measures how fast they score. For a bowler, it measures how fast they take wickets, and the “good” direction flips depending on which one you’re looking at.

Batting strike rate

Batting strike rate tells you how quickly a batter scores runs. It rewards aggression and matters most in limited-overs cricket, where every ball is precious.

Batting strike rate = (Runs scored ÷ Balls faced) × 100

A strike rate of 100 means a run a ball. 150 means one and a half runs a ball. 80 means the batter is scoring slower than a run a ball. Higher is generally better, but a Test opener grinding through a tough session and a T20 finisher swinging from ball one are doing entirely different jobs, and comparing their strike rates head-to-head tells you nothing.

Bowling strike rate

Bowling strike rate measures how often a bowler takes a wicket. Here a lower number is better, since it means fewer deliveries needed per dismissal.

Bowling strike rate = Balls bowled ÷ Wickets taken

A strike rate of 30 means a wicket roughly every five overs. An 18 means a wicket every three overs, which is genuinely sharp bowling. Pair this stat with bowling average (runs per wicket) and economy rate (runs per over) and you get a much fuller read on how a bowler actually performed.

Worked example

Say a batter scores 75 runs off 50 balls:

• Batting strike rate = (75 ÷ 50) × 100 = 150.00

Now say a bowler sends down 120 balls (20 overs) and takes 4 wickets:

• Bowling strike rate = 120 ÷ 4 = 30.0 (a wicket every 30 balls)

Both numbers describe a good day at the office, but they measure different things entirely, so don’t put a batting strike rate next to a bowling strike rate and expect the comparison to mean anything.

What is a good strike rate?

There’s no single benchmark, because expectations shift by format. A batting strike rate that looks sluggish in T20 might be reckless in a Test match. The table below gives realistic guidelines, not fixed rules.

Format	Good batting strike rate	Good bowling strike rate
Test	50–70	Under ~55 balls/wicket
ODI	85–100+	Under ~35 balls/wicket
T20	130–150+	Under ~18 balls/wicket

In Tests, staying at the crease and building an innings counts for more than speed, so a modest batting strike rate is fine. In T20, batters are expected to attack from the first ball, and bowlers earn their keep by breaking partnerships fast rather than just containing runs.

Strike rate on its own only tells half the story. A batting strike rate means little without knowing how many runs came with it, and a bowling strike rate should always be read alongside average and economy before you judge a bowler either way.