About the Cricket Strike Rate
The Cricket Strike Rate & Average Calculator turns three simple box-score numbers, runs scored, balls faced, and times dismissed, into the two most-quoted batting metrics in the game. Strike rate tells you how quickly a batter scores relative to the deliveries they face, while batting average tells you how many runs they typically produce before getting out. Together they separate raw scoring speed from durability at the crease, useful whether you are reviewing a single innings or a full season of figures.
How It Works
You enter total runs scored, the number of balls faced, and how many times the batter was dismissed across the innings or period being analyzed. The calculator divides runs by balls faced and multiplies by 100 to get strike rate, then separately divides runs by dismissals to get batting average. If dismissals is zero, meaning the batter remained not out throughout, the average is reported as undefined rather than a number, since dividing by zero dismissals has no meaningful result.
Formula & Methodology
Both figures come from the same three inputs but measure different things. Strike rate treats every ball faced as the denominator, so a batter who faces many dot balls sees their strike rate drop even if total runs are high. Batting average instead treats dismissals as the denominator, rewarding batters who accumulate runs without losing their wicket, regardless of how many balls that took.
Examples
One-Day Innings
A batter scores 245 runs off 190 balls across a set of innings and is dismissed 5 times. Strike rate works out to (245 / 190) x 100 = 128.95, and batting average is 245 / 5 = 49.00.
Unbeaten Knock
A batter scores 60 runs off 45 balls and is never dismissed in the sample. Strike rate is (60 / 45) x 100 = 133.33, while average is displayed as 'Not out (undefined)' since there are no dismissals to divide by.
Advantages
- Produces both headline batting numbers from one entry instead of calculating each by hand.
- Correctly flags the not-out case instead of showing a misleading average of zero or an error.
- Works for any sample size, from a single innings to a full career total.
Common Mistakes
- Comparing strike rates across formats without context, since a Test innings and a T20 innings imply very different scoring expectations.
- Forgetting that a very high average built on a small number of dismissals can be misleading if the sample is short.
- Entering balls faced as overs bowled at the batter instead of actual deliveries faced, which produces an incorrect strike rate.
Edge Cases to Watch For
- Balls faced must be greater than zero, otherwise the calculator returns an error instead of a strike rate.
- Zero dismissals (an unbeaten innings, or a run of not-outs) produces 'Not out (undefined)' for average rather than a divide-by-zero result.
- The two numbers are calculated independently of overs bowled at the batter, so match situation, required run rate, and bowling quality are not factored in.
Common Use Cases
- Batters and coaches reviewing an innings or a season to compare scoring speed against consistency.
- Fantasy cricket players and analysts benchmarking a player's recent form.
- Scorers and commentators quickly verifying figures during or after a match.