← All tools/Calculators/Sports/Cricket Strike Rate Calculator

Cricket Strike Rate Calculator

Calculate a batter’s strike rate from runs scored and balls faced.

runs
balls

Strike rate

—

Strike rate (0–300 scale)

How it works

Strike rate = runs ÷ balls × 100

A strike rate of 100 means one run per ball on average.
150 means 1.5 runs per ball on average.

This is batting strike rate: runs scored divided by balls faced, multiplied by 100. “Runs” is everything the batter scored, and “balls faced” is the number of legal deliveries faced. The × 100 turns the answer into runs per 100 balls, which is the standard way cricket talks about it. A strike rate of 100 means one run per ball on average, 150 means 1.5 runs per ball, and 50 means one run every two balls. The figure applies to any format, but a good number in one format is ordinary in another, so always read it with the format in mind. Batting strike rate — for bowling strike rate (balls per wicket), see the Cricket Bowling Strike Rate Calculator. The two share a name and nothing else: one measures how fast a batter scores, the other how often a bowler takes a wicket.

Worked example: 75 runs off 50 balls gives a strike rate of 75 ÷ 50 × 100 = 150.00. That is 1.5 runs per ball on average.

Worked example 2: a batter scores 122 off 92 balls in an ODI in Mumbai. The strike rate is 122 ÷ 92 × 100 = 132.61 — about 1.33 runs per ball. In a T20 that would be a steady, useful innings; in a Test it would be very fast. For contrast, 45 off 28 balls is 45 ÷ 28 × 100 = 160.71 — a late-innings burst at more than a run and a half per ball.

What the result means

Strike rate only makes sense next to the runs and the format. A strike rate of 132.61 off 92 balls, like the innings above, is a strong one-day knock: the batter scored quickly and stayed in long enough for it to matter. The same 132.61 off 12 balls would be a cameo — quick, but only 16 runs, and the team would barely notice it. In Tests 50 to 60 is solid, in one-day cricket around 90 is strong, and in T20 130 is the mark of a batter in form. Read it with the average, too. A batter averaging 40 at a strike rate of 130 is a genuine match-winner; a batter averaging 15 at the same strike rate is a slogger who gets out trying. The two numbers together are what selectors look at.

Frequently asked questions

What is a good strike rate?

It depends on the format: in Test cricket 50 to 60 is solid, in one-day cricket around 90 is strong, and in T20 anything above 130 is brisk.

Can the strike rate be above 100?

Yes. Scoring more than one run per ball on average — through boundaries or running — pushes it above 100.

What if no balls have been faced?

Runs divided by zero balls has no answer, so the page asks for at least one ball faced.

Is strike rate or batting average more important?

They answer different questions, so neither replaces the other. Batting average says how many runs a batter scores before getting out; strike rate says how fast those runs come. In Tests, average matters more, because survival is the job. In T20, strike rate matters more, because 20 overs are all there are. A complete batter has both — an average above 35 and a strike rate above 130 in T20, for example — and judging on one alone flatters sloggers or stonewallers.

Do wides and no-balls count in strike rate?

The runs count, but the delivery does not count as a ball faced. A wide adds a run to the batter’s total without adding a ball, and a no-ball does the same, so a batter who picks up several extras will see a slightly higher strike rate. Enter runs and legal balls faced as the scorecard shows them.

More tools

Guides

Tell us what you think

Loving this tool, or stuck on something? Tell us — it takes a minute.

We’ll only use your name and email to reply if needed. The tool and page are filled in for you.