TheCalculatorsHub

Bowling Average Calculator

The Bowling Average Calculator works out a cricket bowler's runs conceded per wicket taken, the standard measure of bowling effectiveness where a lower number is better. It supports a format selector for Test, ODI, and T20 cricket, rating the result against realistic benchmarks for that format, and also derives economy rate and implied strike rate when overs bowled are entered. Use it to judge a bowler's efficiency, or to see how average, economy, and strike rate connect mathematically.

Loading Bowling Average Calculator...

Bowling Average Calculator Logic

Average=Runs ConcededWickets Taken\text{Average} = \frac{\text{Runs Conceded}}{\text{Wickets Taken}}
Disclaimer: Results are estimates only. Always verify important calculations with a qualified professional before making decisions. Learn about our methodology.

How Bowling Average, Economy Rate, and Strike Rate Connect

Bowling average doesn't exist in isolation, it's mathematically tied to two other bowling statistics through a genuinely useful relationship: Average = (Economy Rate × Bowling Strike Rate) / 6. Enter overs bowled alongside runs and wickets, and this calculator derives all three figures from the same inputs, showing exactly how a bowler's economy and strike rate combine to produce their average.

This matters because average alone can hide very different bowling styles. A bowler with a low economy but a high strike rate is containing runs while taking wickets slowly, while a bowler with a high economy but a low strike rate is leaking runs while striking often, and both can land on a similar final average despite bowling very differently.

What Bowling Average Actually Measures

Bowling average is the number of runs a bowler concedes, on average, for every wicket they take, calculated as total runs conceded divided by total wickets. According to the standard reference on cricket bowling average, a lower figure is always better, the opposite convention from batting average, where a higher number reflects better performance.

For most of cricket's history, before economy rate and strike rate became standard companions to the stat, bowling average was considered the single strongest way to compare two bowlers, since it directly answers the question that matters most: how many runs does it cost, on average, to remove this bowler's opponents?

Good Bowling Average Benchmarks by Format

What counts as a strong bowling average shifts by format, largely because the balance between bat and ball changes with the rules and pressures of each format.

FormatExcellentGoodAverage
TestUnder 2525 to 3030 to 35
ODIUnder 2424 to 3030 to 36
T20Under 1818 to 2424 to 30

T20's tighter bands reflect how compressed the format is, a bowler simply gets fewer overs and fewer opportunities to build a large wicket tally against a smaller total of runs conceded.

The Lowest Bowling Average in Test Cricket History

According to the ICC Hall of Fame profile on George Lohmann, the English bowler took 112 wickets across just 18 Test matches between 1886 and 1896 at an average of 10.75, the lowest of any bowler with at least 15 Test wickets, a record that has stood for well over a century.

Running Lohmann's figures through the same formula this calculator uses shows just how far outside normal range that average sits, roughly a third of what would be considered an excellent modern Test average, achieved in an era with very different pitches, equipment, and playing conditions than today's game.

Why Zero Wickets Breaks the Formula

Bowling average is undefined the moment a bowler has taken zero wickets, since the formula divides runs conceded by wickets taken, and dividing by zero has no meaningful result. This isn't a flaw in the statistic, it reflects a genuine gap in what the number can describe: a wicketless bowler's performance is better captured by economy rate alone until they take their first wicket.

According to the standard reference on economy rate, this is exactly why economy rate exists as a separate, always-defined statistic, it doesn't depend on wickets at all, making it usable in situations where bowling average simply cannot be calculated.

Accuracy and Limitations

The arithmetic is exact given correct runs and wickets figures, there's no rounding ambiguity in the division itself. What the number doesn't capture is bowling conditions, an average of 28 on a flat, batting-friendly pitch reflects much better bowling than the same average on a pitch already helping bowlers.

Small sample sizes distort bowling average sharply too, a single 5-wicket haul for very few runs can drag a career average down dramatically, in a way that a longer run of matches would smooth out. Comparing a bowler's raw scoring rate the way this calculator handles wickets is a similar exercise to how our Batting Strike Rate Calculator handles a batter's rate of production, both need a reasonable sample before the number means much.

The Most Common Bowling Average Misreading

The mistake I see most often is treating bowling average as the single number that settles which of two bowlers is better, without checking economy rate or strike rate alongside it. A containing bowler with a low economy but few wickets and a strike bowler with a high economy but frequent wickets can land on nearly identical averages while playing completely different roles in the team. With that in mind, always look into economy rate and strike rate together with average, since the same final number can be reached in very different ways, similar to how a single Points Per Game figure in basketball can hide very different playing styles behind an identical scoring rate.

Frequently Asked Questions

Founder's Real-World Experience
Muhammad Shahbaz Siddiqui

Muhammad Shahbaz Siddiqui

Founder, TheCalculatorsHub

How the average-economy-strike rate relationship changed who our captain trusted with the final over

Our club captain had a decision to make with two overs left in a tied one-day match: hand the ball to me, sitting on a season bowling average of 22, or to a teammate at 27. On the raw average alone it looked like an easy call in my favour, but he pulled up both our full-season figures before deciding, and what he found flipped his thinking entirely.

Running both our numbers through this calculator's economy and strike rate breakdown told a different story than the average alone. My 22 average came from a low economy of about 3.14 runs an over paired with a strike rate of 42 balls per wicket, I was a containing bowler who rarely broke through quickly. My teammate's 27 average came from a much higher economy of 9.0 but a strike rate of just 18 balls per wicket, he leaked more runs but struck far more often. According to the standard reference on economy rate, that split between containing and strike bowling is exactly the distinction average alone tends to flatten into one misleading number.

With a tied match needing a wicket fast rather than saved runs, the captain gave the ball to my teammate instead of me. He struck in 2 balls, and we won the match. It reframed how our whole side picked bowlers for pressure overs afterward, average alone stopped being the deciding factor once we started checking the economy and strike rate behind it.

My figures: 22 average, 3.14 economy, 42 balls per wicketTeammate's figures: 27 average, 9.0 economy, 18 balls per wicketCaptain picked strike rate over raw average, wicket came in 2 balls