Cricket Batting Strike Rate Calculator

Background.

A cricket batting strike rate is the number of runs a batter scores per 100 balls faced: SR = 100 × R ÷ B. It is the speed half of a batting record. The batting average tells you how many runs a batter makes between dismissals; the strike rate tells you how long they took to make them, and in limited-overs cricket that second question is frequently the more important one.

The definition is stable across the sports-science literature. Lemmer, writing in the Journal of Sports Science & Medicine, states it as "SR = 100 R/B with B the total number of balls the batsman faced, i.e. SR = the number of runs scored for every 100 balls faced". Murray and colleagues, in Frontiers in Human Neuroscience, give the same definition in words: "the average number of runs scored per 100 balls faced". There is no era-specific or board-specific variant to choose between — unlike, say, net run rate, the batting strike rate means the same thing in a village league scorebook and an ICC record.

The scale is worth internalising because the multiplication by 100 makes it look like a percentage when it is not. A strike rate of 100 means exactly one run per ball. Below 100 the batter is scoring slower than a run a ball; above 100, faster. There is no upper bound: a batter who hits a six off the only ball they face has a strike rate of 600. In Test cricket a career strike rate in the 50s is normal and one above 70 is aggressive. In one-day internationals the middle of the distribution sits somewhere around 85–95 for top-order batters. In T20 a top-order rate below 120 is usually a liability and a finisher may be judged on whether they can sustain 160 or more, because the format only has 120 balls to allocate and every ball a slow batter uses is a ball a fast one does not get.

The one input that trips people up is balls faced. Which deliveries count is a scorer's convention rather than a Law of Cricket: the striker is credited with a ball faced for every delivery they had the opportunity to play. A no ball counts, because the striker still has to deal with it. A wide does not, because MCC Law 22.1.2 defines a wide as a delivery that is not "sufficiently within reach for him/her to be able to hit it with the bat by means of a normal cricket stroke" — the batter never had a chance at it. The practical rule is to take the balls-faced number straight from the scorecard, where those conventions have already been applied.

The calculator runs in three modes on the same identity. The default takes runs and balls and returns the strike rate. The second inverts it for planning: at a target strike rate, how many runs must come off a given number of balls? The third answers the chase question from the batter's side: to score a given number of runs at a given tempo, how many balls will it take? Every mode also converts the tempo into runs per over — six balls to the over under MCC Law 17.1 — because that is the unit the scoreboard, the required run rate and the commentary all use.

Below the widget: the derivation, a fully worked innings, why strike rate and average must be read together rather than separately, how strike rate interacts with batting position and phase of the innings, and the specific scorecard cases that decide whether a delivery lands in the balls-faced column.

What is cricket batting strike rate calculator?

The batting strike rate is a rate statistic that normalises a batter's scoring to a fixed number of deliveries — 100 of them — so that innings of different lengths can be compared. Formally SR = 100R/B, where R is runs credited to the batter and B is balls faced. It is quoted to two decimal places and appears next to the average in every limited-overs career record and most first-class ones. Three properties matter when reading it. First, it is scale-free in innings length: 87 off 62 and 174 off 124 have exactly the same strike rate, so a long slow innings and a short quick one are directly comparable. Second, it says nothing about dismissals, so a batter who scores 30 off 15 and is out and a batter who scores 30 off 15 and remains unbeaten have identical strike rates — durability is the batting average's job. Third, it is highly context-dependent: strike rates rise steeply through a limited-overs innings as fielding restrictions change and the innings shortens, so a 'low' strike rate in the first ten overs of a T20 chase can be worth more than a 'high' one in the last two. In Test cricket, strike rate matters mostly for its effect on the clock — a team must bowl the opposition out twice, and runs scored quickly buy overs to do it in. This calculator computes the raw statistic exactly as defined; it does not apply any of the contextual adjustments proposed in the sports-science literature, because none of them is used by the official record.

How to use this calculator.

1. 01Choose a mode. 'Strike rate' answers the ordinary question. 'Runs needed' works out the score a target tempo implies off a given number of balls. 'Balls it takes' works out how long a given score will occupy at a given tempo.
2. 02Enter runs scored — the number printed against the batter's name. Byes, leg byes and wides go to the team rather than the striker, so they are already excluded on the scorecard.
3. 03Enter balls faced. Count no balls as balls faced and do not count wides. If you are reading a printed scorecard this is already handled; if you are counting from a live feed, the 'B' or 'BF' column is the one you want.
4. 04Read the strike rate, then read the runs-per-over figure underneath it. Runs per over is the same tempo in the unit the scoreboard uses: a strike rate of 140 is 8.40 an over, which tells you immediately whether the batter is ahead of or behind a chase.
5. 05Compare the strike rate against the batting average rather than in isolation. A batter averaging 25 at a strike rate of 160 and one averaging 40 at 110 contribute in different ways, and which is more valuable depends entirely on the format and the batting position.
6. 06For a target, switch to 'Runs needed', enter the strike rate you want and the balls you expect to face, and the calculator returns the score that produces it — useful for setting a realistic phase-by-phase plan rather than a single innings total.

The formula.

The identity is SR = 100 × R ÷ B.

Divide runs by balls to get runs per ball, then multiply by 100 to move the decimal point somewhere readable. A batter on 87 from 62 balls is scoring 1.4032 runs per ball; multiplied by 100 that is a strike rate of 140.32. The factor of 100 has no cricketing meaning — it exists purely so that the everyday range of the statistic falls between roughly 50 and 200 rather than between 0.5 and 2.0, and it is why the number is often mistaken for a percentage.

The conversion to runs per over uses the six-ball over, which is not an assumption but MCC Law 17.1: "The ball shall be bowled from each end alternately in overs of 6 balls." Runs per over is therefore SR × 6 ÷ 100. A strike rate of 100 is 6.00 an over; 140 is 8.40; 160 is 9.60. This is the bridge between a batter's individual tempo and the team-level rates used by the required run rate and net run rate calculators, and it is why the two families of statistic can be reasoned about together.

The two inverse modes are algebra on the same line. Solving for runs gives R = SR × B ÷ 100 — at a strike rate of 140 off 62 balls you need 86.8 runs, which in practice means 87. Solving for balls gives B = 100 × R ÷ SR — 87 runs at a strike rate of 140 occupies 62.14 balls. Fractional answers are expected here and are not rounded away: they are planning quantities, and rounding 62.14 down to 62 would quietly raise the implied strike rate.

Two edge cases are handled explicitly rather than papered over. A strike rate off zero balls faced is undefined — scorecards print a dash for a batter who has not faced a delivery — so the calculator raises an error rather than dividing by zero. And zero runs is a perfectly legal input in the default mode: a batter out for a duck off seven balls has a strike rate of exactly 0.00, which is a real number rather than a missing one. Zero runs is refused only in the 'balls it takes' mode, where it would imply zero balls and answer nothing.

A worked example.

Frequently asked questions.

References& sources.

1. [1]Lemmer, H. H. (2011). 'The single match approach to strike rate adjustments in batting performance measures in cricket.' Journal of Sports Science & Medicine, 10(4), 630–634. Open access. Defines the statistic implemented here: "SR = 100 R/B with B the total number of balls the batsman faced, i.e. SR = the number of runs scored for every 100 balls faced."
2. [2]Murray, N. P., Lawton, J., Rider, P., Harris, N. & Hunfalvay, M. (2021). 'Oculomotor behavior predict professional cricket batting and bowling performance.' Frontiers in Human Neuroscience, 15, 768585. Open access. Defines batting strike rate as "the average number of runs scored per 100 balls faced. A higher strike rate represents how effective a batsman is at scoring quickly."
3. [3]Marylebone Cricket Club — Laws of Cricket, Law 17 (The over). Law 17.1: "The ball shall be bowled from each end alternately in overs of 6 balls." Law 17.3.2 excludes no balls and wides from the six. This is the constant behind the runs-per-over and overs-faced conversions on this page.
4. [4]Marylebone Cricket Club — Laws of Cricket, Law 22 (Wide ball). Law 22.1.2: "The ball will be considered as passing wide of the striker unless it is sufficiently within reach for him/her to be able to hit it with the bat by means of a normal cricket stroke" — the reason a wide is not counted as a ball faced. Law 22.7 debits all runs from a wide against the bowler.
5. [5]International Cricket Council — ICC Men's T20 World Cup 2026 Playing Conditions (PDF). Clause 13.6.1: "All matches will consist of one innings per side, each innings being limited to a maximum of 20 overs" — the 120-ball budget that makes strike rate the dominant batting statistic in the format.