Bowling average measures how many runs a bowler typically concedes per wicket taken — unlike strike rate, lower is always better here. It’s the single number most used to compare bowlers across formats and eras, and this calculator tells you exactly which tier a given average falls into.
Below the calculator you’ll find a manual step-by-step walkthrough, common scoring mistakes, a full benchmark table, why bowling average has remained cricket’s core bowling number for over a century, and an expanded FAQ.
Cricket Bowling Average Calculator
🏏 Blogyz CalcEstimates only — formulas follow the official standard for this stat, but always confirm against your league’s exact scoring rules.
Bowling Average vs Economy Rate
Bowling average and economy rate measure different things and are often confused. Average tells you how many runs it costs to get a wicket — a wicket-taking measure. Economy rate tells you runs conceded per over, regardless of wickets — a containment measure. A bowler can have a great economy rate while taking very few wickets, or vice versa.
Worked Example
A bowler concedes 612 runs across a season while taking 24 wickets — the calculator’s defaults. That’s a bowling average of 25.50, right on the border between “excellent” and “solid” by Test-match standards. Take just 4 more wickets for the same runs conceded and the average drops to 21.9, moving comfortably into elite territory — which shows how sensitive this stat is to wicket-taking, not just economy.
Why Format Changes What “Good” Means
Test bowling averages are generally lower than white-ball averages because batters take more risks in limited-overs cricket, handing bowlers more wickets relative to runs conceded — even though those same bowlers often leak more runs per over. Comparing a bowler’s Test average directly to their T20 average tells you very little; each format needs its own benchmark.
Why Captains Watch This Number Closely
Bowling average heavily influences how captains allocate overs — a bowler with a low average against a specific batter or in a specific phase of play is far more likely to be brought back for a crucial spell than one with a similar economy rate but a worse average. Selectors also lean on career bowling average, adjusted for era and conditions, as one of the primary numbers separating merely useful bowlers from genuine matchwinners over a long career.
Bowling average also plays a major role in how bowling attacks are balanced on selection day — a team will often pair a low-average strike bowler who takes wickets in clusters with a more defensive, high-economy-but-still-solid-average bowler whose job is to build pressure and set up wickets at the other end, rather than fielding five bowlers chasing the exact same role.
Step-by-Step: How to Calculate Bowling Average by Hand
Step 1: Add up total runs conceded by the bowler across the innings or season you’re measuring. Step 2: Add up total wickets taken. Step 3: Divide runs conceded by wickets taken. For example, 612 runs conceded and 24 wickets taken: 612 ÷ 24 = 25.50. That’s the entire calculation — the only real requirement is that at least one wicket has been taken, since dividing by zero wickets is mathematically undefined.
Because it’s such a simple two-input formula, bowling average is tracked continuously through a match, a series, and a career, and it’s one of the very few cricket statistics that translates cleanly across formats without needing rate adjustment, unlike strike rate or economy rate which are inherently tied to balls or overs bowled.
Common Mistakes When Calculating Bowling Average
The most common mistake is including runs conceded off no-balls and wides that are scored as extras against the bowler but not properly reconciled with the wickets column — every run charged to a bowler’s figures (including penalty runs from no-balls and wides) counts in the runs-conceded total, so leaving these out understates the average. A second mistake is counting run-outs as bowler wickets — a run-out is credited to the fielding side but not to the bowler’s personal wicket tally, since the bowler didn’t directly dismiss the batter. A third mistake is averaging bowling averages themselves across multiple matches instead of totaling runs and wickets first — averaging a series of per-match averages produces a mathematically different (and less accurate) number than the correct cumulative calculation.
Bowling Average Benchmarks at a Glance
These are the exact thresholds this calculator uses, generally calibrated to Test-match standards:
| Bowling Average | Tier | What It Typically Means |
|---|---|---|
| Below 25 | Excellent | Among the best wicket-taking bowlers in the format |
| 25 – 29.9 | Solid | A dependable, above-average bowler |
| 30 – 34.9 | Average | Roughly matches typical international standards |
| 35 and above | Below Par | Struggling to convert overs into wickets efficiently |
Why Bowling Average Has Stayed Cricket’s Core Bowling Number
Bowling average has been tracked since the earliest days of organized cricket precisely because it answers the single most important question about a bowler in the simplest possible way: how many runs does it cost, on average, to get this bowler a wicket? Unlike strike rate (which measures speed of wicket-taking) or economy rate (which measures containment), bowling average blends the core job of a bowler — taking wickets — with the cost of doing so, in one number that’s stayed relevant across more than a century of the sport’s evolution, from uncovered pitches and timeless Tests to modern flat, batter-friendly surfaces.
What Actually Lowers a Bowler’s Average
Consistency in line and length is the foundation — a bowler who repeatedly forces batters into uncomfortable decisions tends to accumulate both wickets and economy over time, which naturally pulls the average down. Variations (a well-disguised slower ball, a wrong’un from a wrist-spinner, seam movement off the pitch) create wicket-taking opportunities that pure pace or accuracy alone can’t, especially against set batters who’ve adjusted to a bowler’s stock delivery. Bowling in partnership with a strong bowler at the other end also genuinely helps — batters forced to rotate strike against sustained pressure from both ends are statistically more likely to make the mistake that produces a wicket.
FAQ
What’s a good Test bowling average?
Under 25 is considered excellent for a Test-match bowler, under 30 is solid, and above 35 is generally viewed as below par at the international level.
Why is average “undefined” with zero wickets?
Dividing runs conceded by zero wickets is mathematically undefined — a bowler needs at least one wicket before an average can be calculated at all.
Does bowling average differ meaningfully between Test and T20 cricket?
Yes — T20 bowling averages tend to run higher than Test averages because batters take more risks and hit more boundaries in the shorter format, even though those same bowlers often take wickets more frequently per ball bowled (a lower bowling strike rate) than in Tests.
What’s considered an elite career bowling average in Test cricket history?
Historically, a career Test bowling average under 25 sustained across a long career is considered a mark of an all-time great bowler, since averages tend to rise over a long enough sample as a bowler faces every type of batting lineup and pitch condition.
Can bowling average be zero?
In theory, yes, if a bowler takes wickets while conceding zero runs — extremely rare, but mathematically it would produce a bowling average of 0.00, the lowest possible value.
Why do captains sometimes bowl a low-average bowler less than expected?
Workload management, matchups against specific batters, pitch conditions on a given day, and protecting a bowler’s fitness across a long tour or series can all lead a captain to bowl a statistically excellent bowler less than pure numbers alone would suggest.
Is bowling average the same thing as bowling strike rate?
No — bowling average measures runs conceded per wicket, while bowling strike rate measures balls bowled per wicket. A bowler can have a low average but a relatively high strike rate (efficient but not fast at taking wickets), or the reverse, and the two numbers are read together for a fuller picture.
