The cricket strike rate calculator above turns runs and balls faced into a batting strike rate, the standard measure of how quickly a batter scores. It works for any format, because the definition does not change between them, and it adds the numbers that make a strike rate readable: the run rate it corresponds to, the proportion of the innings that came in boundaries, and how the batter scored when the ball did not reach the rope.
Arb Digital publishes free calculators for people who want a specific number without an account or an app. This one exists because a strike rate on its own is a thin statistic. Two innings of 76 from 52 balls can look identical on a scorecard and be completely different innings, and the extra numbers here are what separate them.
What This Cricket Strike Rate Calculator Does
The headline figure is runs per hundred balls. The grid converts that into an equivalent run rate per over, which is the unit commentary and scoreboards actually use, then breaks the innings apart. It reports how many runs came from fours and sixes, how many balls the batter faced per boundary, and the strike rate achieved on the balls that were not hit for four or six.
That last number is the interesting one and almost nobody calculates it. An innings where the boundaries are stripped out shows how well the batter kept the scoreboard moving between them, which is what separates a controlled innings from one that depended on a handful of big hits. The bars underneath show the split of runs directly.
The format selector changes nothing in the arithmetic. It only sets the benchmark the result is described against, because a strike rate of 75 is slow in a T20 and rapid in a Test match. The same calculation, read in three different contexts.
How to Use It
- Enter runs scored by the batter. Runs the batter did not score personally, such as byes and leg byes, do not belong here even though they were scored while that batter was on strike.
- Enter balls faced. Legal deliveries and no-balls count. Wides do not, because a wide is not deemed to have been faced.
- Add fours and sixes if you want the boundary breakdown. Leave them at zero to work with the strike rate alone.
- Pick a format to have the result described against a reasonable benchmark for that kind of cricket.
- Compare the two strike rates — overall and non-boundary — to see how much of the scoring rate rested on clearing the field.
The Formula and How It Is Calculated
Batting strike rate is SR = (runs ÷ balls faced) × 100, which expresses scoring as runs per hundred deliveries. The default example of 76 runs from 52 balls gives (76 ÷ 52) × 100 = 146.15.
Because an over is six legal deliveries, the equivalent run rate is the strike rate divided by 100 and multiplied by six: 146.15 × 6 ÷ 100 = 8.77 runs per over. The boundary figures follow directly. Eight fours and three sixes are 32 + 18 = 50 runs, which is 65.8 percent of the innings, struck across 11 scoring shots for 52 ÷ 11 = 4.73 balls per boundary. Removing them leaves 26 runs from 41 balls, a non-boundary strike rate of 63.4.
What counts as a ball faced is defined by the playing conditions rather than by the arithmetic. Under the Laws of Cricket maintained by the MCC a wide is not a delivery the striker is deemed to have received, so it is excluded, while a no-ball is included. Byes and leg byes count toward the team total but not toward the batter's runs, so they inflate the run rate without touching the strike rate. Competition-specific variations are set out in the ICC playing conditions.
Batting Strike Rate and Bowling Strike Rate Are Not the Same Statistic
Both are called strike rate and they measure opposite things in opposite units, which causes more confusion than any other pair of cricket statistics. Batting strike rate is runs per hundred balls, and higher is better. Bowling strike rate is balls per wicket, and lower is better.
They are not two views of one quantity. A batting strike rate of 150 is excellent; a bowling strike rate of 150 would mean a wicket every 25 overs, which is close to unemployable. There is no scale on which they can be compared, and the shared name is an accident of usage rather than a family resemblance.
The bowling equivalents of the batting numbers here are economy rate, which is runs conceded per over, and average, which is runs conceded per wicket. Between them, bowling strike rate and economy rate say what a bowler is for: a low strike rate means a wicket-taker, a low economy rate means a container, and the best bowlers manage both.
Why Strike Rate Alone Cannot Rank Two Innings
Strike rate says nothing about how long a batter survived, and average says nothing about how quickly they scored. Each is blind to the other's dimension, which is why every serious attempt to compare batters uses them together.
Consider two T20 innings. One batter makes 40 from 20 balls and is out; another makes 60 from 45 and finishes not out. The first has the higher strike rate, 200 against 133, and the second contributed more runs and left the side better placed. Which was worth more depends entirely on the match situation, and no single number contains that.
Context stacks up quickly. A strike rate of 130 in the first six overs against a new ball is a different achievement from 130 in the last four against a tiring attack, on the same pitch, in the same match. Chasing changes the calculation again, because a required rate makes fast scoring necessary rather than merely useful. The Duckworth-Lewis-Stern calculator exists precisely because run scoring is not linear across an innings, and the net run rate calculator handles the team-level version of the same question.
The Non-Boundary Strike Rate Is the Number Analysts Actually Want
Boundaries dominate scorecards. In the default example, 11 scoring shots produced two thirds of the runs, which means the other 41 balls produced the remaining third. Splitting those two apart tells you something the combined figure hides.
A batter with a high overall strike rate and a low non-boundary strike rate is scoring in bursts. That is a high-variance approach: when the big shots come off the innings looks superb, and when they do not the batter can be stuck on a low score having consumed a lot of deliveries. A batter with a moderate overall rate and a strong non-boundary rate is rotating strike, taking twos and keeping the scoreboard moving without risk.
Dot ball percentage is the other side of the same measurement and is worth tracking alongside it. In limited-overs cricket a run of dot balls transfers pressure to the batter far more effectively than a single good delivery does, and a batter who scores heavily off boundaries while leaving long strings of dots can have an excellent strike rate and still be losing their team the game. If you are working out percentages across a season's worth of innings, the percentage calculator and the weighted average calculator handle the aggregation.
How Strike Rates Compare Across the Three Formats
The same arithmetic produces numbers that mean entirely different things depending on the format. In Test cricket a strike rate near 50 is unremarkable and the priority is occupying the crease, so a low figure carries no criticism at all. In fifty-over cricket the expectation sits closer to 85 or 90 for a top-order batter, rising steeply in the closing overs. In T20 anything under about 120 will be questioned, and finishers routinely operate well above 150.
The reason is the constraint each format imposes. Tests limit runs by wickets in hand and by time; there is no ball shortage, so scoring quickly buys relatively little. Limited-overs cricket caps the deliveries available, which turns every dot ball into a lost opportunity and makes tempo the central resource. Shorten the format further and the effect intensifies, which is why T20 strike rates keep climbing as teams get better at using the whole batting order.
This is also why comparing a batter's career strike rate across formats is close to meaningless without splitting it by format first. An aggregate across all cricket blends three different games into one number that describes none of them.
Arb Digital publishes hundreds of free calculators across sports, maths, health and finance — no sign-up, no limits. If something you need is missing, tell us and we will look at building it.
Browse All Free Tools Suggest a ToolCommon Mistakes to Avoid
- Counting wides as balls faced — a wide is not deemed to have been received by the striker, so including it understates the strike rate.
- Including byes and leg byes in the batter's runs — they count toward the team total only, and adding them inflates an individual strike rate.
- Comparing batting and bowling strike rates — one is runs per hundred balls and higher is better, the other is balls per wicket and lower is better.
- Ranking innings on strike rate alone — it is blind to how long the batter lasted, to the match situation and to what the side needed.
- Averaging strike rates across innings — add all the runs and all the balls first. A simple mean of the individual rates gives short innings the same weight as long ones.
Related Free Tools From Arb Digital
Work out a team's tournament position with the net run rate calculator, or a revised target in a rain-affected match with the Duckworth-Lewis-Stern calculator. For season-long aggregation the weighted average calculator combines innings correctly, the percentage calculator handles boundary and dot-ball shares, and the ratio calculator compares any two counts directly. The mean, median and mode calculator is useful when a career average is skewed by one huge innings. The full free online tools hub lists everything else.
Frequently Asked Questions
Divide the runs scored by the balls faced and multiply by 100. A batter who makes 76 from 52 balls has a strike rate of 146.15, meaning they would score about 146 runs if they faced a hundred deliveries at that tempo.
No. A wide is not deemed to have been received by the striker, so it is excluded from balls faced. A no-ball is included, because the striker did face the delivery even though it was illegal.
Strike rate is an individual measure in runs per hundred balls. Run rate is a team measure in runs per over. Because an over is six balls, a strike rate of 100 corresponds to a run rate of six, so dividing by 100 and multiplying by six converts between them.
No, and the shared name is misleading. Bowling strike rate is the number of balls a bowler needs per wicket, so a low figure is good. Batting strike rate is runs per hundred balls, so a high figure is good. The two cannot be compared on any scale.
It depends entirely on the format. Around 50 is normal in Test cricket, roughly 85 to 90 for a top-order batter in fifty-over cricket, and above 120 in T20, with finishers often well past 150. An aggregate across formats describes none of them.
Add up all the runs and all the balls faced, then apply the formula once. Taking a simple average of the individual strike rates gives a twelve-ball cameo the same weight as a hundred-ball innings, which distorts the result.
It is the rate the batter scored at on deliveries that were not hit for four or six. A large gap between it and the overall figure means the innings depended on boundary hitting rather than on rotating the strike.
