Cricket Strike Rate & Batting Average Calculator

Free Cricket Strike Rate & Batting Average Calculator

This calculator works out a batter's strike rate and batting average — two of the most-watched cricket stats, especially during IPL, T20 World Cup, and ODI World Cup season. Enter total runs, balls faced, innings, and not-outs to get instant, accurate results, plus a benchmark comparison against typical numbers for T20, ODI, or Test cricket.

Add fours and sixes hit to unlock a boundary breakdown showing exactly how much of the total came from boundaries versus running between the wickets — useful for understanding a batter's real scoring style beyond the headline numbers.

Strike Rate & Batting Average Formulas

Batting Strike Rate = (Runs Scored ÷ Balls Faced) × 100. It measures scoring speed — runs per 100 balls — and is the number broadcasters flash up after every big hitting innings.

Batting Average = Total Runs ÷ Number of Times Dismissed. It measures consistency — how many runs a batter typically makes before getting out. If a batter has never been dismissed across the innings entered, the average is technically undefined, since dividing by zero dismissals has no meaningful answer; this calculator flags that case clearly instead of showing a misleading number.

Why Both Numbers Matter Together

Strike rate and average pull in different directions. A batter can boost strike rate by taking more risk, which often lowers average as more risky shots end in dismissal. Equally, a batter can protect their average by playing cautiously, which typically slows the strike rate down.

The best judgement of a batter almost always looks at both figures side by side rather than either one alone — which is why this calculator compares both against typical format benchmarks rather than showing just a single headline number.

What's a Good Strike Rate and Average by Format?

T20 cricket rewards speed above all else: a strike rate above 130-140 is considered strong for a top-order batter, and finishers are often expected to strike above 150, while an average around 30 is respectable given how often risk is taken.

ODI cricket sits in between: a strike rate around 85-95 with an average in the high 30s to 40s is typical for a reliable top-order or middle-order batter, since innings need to be built across 50 overs rather than sprinted through.

Test cricket flips the priority almost entirely toward average: a strike rate around 45-55 is common even for attacking players, while an average above 40 is generally considered the benchmark for a specialist batter at international level.

Reading the Boundary Breakdown

The donut chart splits total runs into three sources: runs from fours, runs from sixes, and runs picked up from running between the wickets (singles, twos, threes, and any byes attributed to the bat elsewhere aren't separated out here). A high boundary percentage usually signals an aggressive, high-strike-rate approach, while a batter with a lower boundary share but similar runs is likely rotating the strike efficiently through ones and twos.

Balls per boundary is another quick read on hitting frequency — a lower number means boundaries are coming more often relative to balls faced, which usually tracks closely with a higher overall strike rate.

Worked Example

Suppose a batter has scored 245 runs off 180 balls across 6 innings, with 2 not-outs. Strike rate = (245 ÷ 180) × 100 ≈ 136.11. Dismissals = 6 − 2 = 4, so average = 245 ÷ 4 = 61.25.

That combination — a strike rate well above the typical T20 benchmark alongside a high average — would read as a genuine match-winning performance rather than either a pure aggressor or a pure anchor.

Common Mistakes When Calculating These Stats

A few errors come up repeatedly when working these numbers out by hand.

• Dividing runs by innings played instead of dismissals when calculating average — not-out innings should not count as a full dismissal.
• Forgetting to multiply by 100 when calculating strike rate, which gives a fraction instead of the familiar runs-per-100-balls figure.
• Comparing a T20 strike rate directly against a Test strike rate without adjusting for the completely different scoring pace expected in each format.
• Treating a small sample of innings (like a single match) as a reliable long-term average, when a career average needs a much larger sample to be meaningful.
• Ignoring not-outs entirely, which understates how consistently a batter is finishing innings unbeaten.

How to Use This Calculator

Pick a format to set the comparison benchmark, then enter runs, balls faced, innings, and not-outs. Add fours and sixes if you want the boundary breakdown and balls-per-boundary figures, or tap one of the quick-fill example innings to see it in action instantly.

The scoreboard summary table, benchmark comparison bars, boundary donut chart, and full step-by-step working all update immediately as you type — handy for post-match analysis, fantasy cricket team selection, or checking a stats assignment.