Batting Average Calculator
Enter total runs, innings played, and not-outs to get a batter's average — runs per dismissal.
Formula: Batting Average = Total Runs ÷ Dismissals, where Dismissals = Innings Played − Not Outs. Not-out innings still add to the runs total but don't count as a dismissal, which is why frequent not-outs can push an average up.
What Is Batting Average?
Batting average answers a simple question in a single number: on average, how many runs does this batter get before they're dismissed? It's been the headline batting statistic in cricket since scorebooks first started being kept seriously, and it's stayed there because it rewards exactly the thing Test cricket has always valued most — staying at the crease.
Unlike strike rate, average has nothing to do with how quickly those runs come. A batter could take 400 balls to reach a double-century or a fraction of that, and their average would treat both innings identically as long as the final tally of runs and dismissals matched up. That's precisely why average and strike rate are usually quoted side by side rather than as substitutes for one another — each one is blind to exactly what the other measures.
Formula & Worked Examples
Add up every run a batter has scored, then divide by the number of times they've actually been dismissed. Innings finished not out don't get counted as dismissals, even though the runs from those innings are still included in the total — which is the detail that trips up almost everyone doing this calculation for the first time.
Why It Matters
Don Bradman's Test average of 99.94 is probably the single most quoted number in the sport's history, and the reason it still gets brought up almost a century later is that nobody has come remotely close since. The next-best qualifying Test average sits more than 30 runs behind it — a gap that puts into perspective just how much weight this one number can carry when talking about a player's legacy.
Selectors and analysts use average as a first filter more than almost any other number, because it's a clean way to compare players across different eras, conditions, and opponents without needing to watch every innings they played. But it flattens a lot of nuance in doing so — an average built against weak bowling attacks at home reads identically on paper to one built grinding out runs on hostile, seaming pitches away from home.
Average also interacts strangely with batting position. A number eight batter who plays a handful of gutsy, unbeaten cameos can end up with an inflated average that has more to do with rarely being the one left to face the collapse than with genuine batting class — which is exactly why context around not-outs matters so much when reading this stat.
Common Mistakes to Avoid
- Dividing total runs by innings played instead of dismissals — this is the single most common error, and it silently deflates the average of any batter with even a couple of not-outs.
- Comparing averages across formats directly. A Test average of 45 and an ODI average of 45 reflect completely different kinds of batting under completely different pressures.
- Treating a small sample — say, a single series or a handful of innings — as if it carries the same weight as a 100-innings career average.
- Ignoring the era and conditions a player accumulated their average in; pitches, bowling quality, and even bat technology have shifted averages up and down across cricket history.
- Assuming a lower average automatically means a worse batter — all-rounders and lower-order players are often judged on a different scale entirely, since scoring isn't their primary job.
Related Calculators
Frequently Asked Questions
Why is 50 considered the benchmark for a good Test average?
It's more tradition than science, but a career average above 50 has long been treated as the line between a very good Test batter and an all-time great one, largely because so few players have sustained it across a long career.
What happens if a batter has never been dismissed?
Their average is technically undefined, since you can't divide by zero dismissals — this calculator shows 'Not Out' in that situation rather than a misleading number.
Is batting average used in T20 cricket?
It's tracked, but it's treated as a secondary stat compared to strike rate, since T20 innings are short enough that survival matters far less than scoring speed.
Can batting average go down after a not-out innings?
No — a not-out innings can only hold an average steady or push it up, since it adds runs to the total without adding to the dismissal count.
How is bowling average different from batting average?
They use the same basic idea — runs divided by an event count — but for a bowler, a lower average is better, since it means they're conceding fewer runs for each wicket they take.