🎯 Bowling Average Calculator

How to Use This Bowling Average Calculator

Bowling average is the headline measure of a bowler: runs conceded per wicket taken. Lower is better. Enter total runs conceded and total wickets taken across any sample, a season, a career, or a single series, and the calculator returns the average with a plain-English assessment.

The Bowling Average Formula

The formula is the mirror of batting average, which is runs per dismissal for batters. For bowlers, the cost is runs and the product is wickets, so 450 runs for 18 wickets is 25 runs per wicket. A bowler with no wickets has no defined average, which is why the calculator requires at least one wicket. Bowling average ignores overs bowled entirely, so it pairs naturally with economy rate (runs per over) and strike rate (balls per wicket). The three together describe cost, thrift, and penetration.

Worked Example

Enter 450 runs conceded and 18 wickets. Average = 450 / 18 = 25.00. In Test cricket this is excellent, genuinely world-class territory over a long career. In ODIs it is good without being remarkable. In T20s it would be on the expensive side, since the format compresses averages downward and economy matters more. Same number, three verdicts. Always name the format before judging a bowling average, and always check the sample size: 18 wickets is a decent series, not a career.

Bowling Average Across Formats and History

Test cricket sets the highest bar because batters can wait for bad balls. Career averages under 30 mark good Test bowlers, under 25 mark great ones, and the famous historical benchmark is Sydney Barnes at 16.43 from the early 1900s, a figure from a very different era of uncovered pitches. In ODIs, where batters attack more, under 30 remains the good-bowler line and under 25 is elite. In T20s, averages naturally fall because batters take risks, but economy rate and strike rate matter more to selectors than average. Spinners often average better at home where pitches grip, and quicks better with the new ball, so splits by condition tell a fuller story than one career number.

Using the Stat Wisely

Bowling average rewards wicket-takers and punishes containing bowlers who do the quiet work, so never use it alone. A bowler averaging 32 with an economy of 4.5 in ODIs may be more valuable than one averaging 28 at 6 runs per over, depending on role. Sample size matters enormously: five wickets at 12 is a good month, not a career. For club cricketers tracking their own stats, record all three numbers each season and watch the trends. A falling average with a steady economy means you are taking more wickets without leaking runs, which is the real skill.

A Second Worked Example: The T20 Specialist

A T20 bowler concedes 300 runs and takes 20 wickets across a season. Average: 300 divided by 20 is 15.00. In T20 cricket that is outstanding; the format's aggression keeps most good bowlers in the low 20s, and anything under 20 over a real sample marks genuine quality. The same 15.00 in Tests would be all-time-great territory, which shows why the format label matters more than the number.

Pair it with economy: 300 runs in, say, 60 overs is 5.00 an over in older scoring or 7.50 in the modern game depending on overs. Average says how costly the wickets were; economy says how costly the overs were; strike rate says how frequent the wickets were. One stat is a headline; three are a profile.

Great Averages in History

The benchmark for Test bowling is Sydney Barnes, whose 189 wickets came at 16.43, a figure from the early 1900s that still tops the all-time list for bowlers with long careers. Sub-20 Test career averages are vanishingly rare in the modern game; the greats of recent eras cluster in the low 20s. Muttiah Muralitharan's 800 wickets at 22.72 pair otherworldly longevity with elite economy of cost.

These numbers also show the format gulf: historical Test averages in the teens and twenties reflect long-form cricket's patience, while T20's hit-or-bust economy produces different scales entirely. Judge against the format's history, not against a universal standard that does not exist.

Common Bowling-Average Mistakes

First: the zero-wicket void. No wickets means no average, not zero; the calculator requires at least one wicket because division by zero is not a statistic. Second: format blindness. A 25 average is world-class in Tests and ordinary in T20s; always name the format first.

Third: the runs-charged confusion. Wides and no-balls count against the bowler; byes and leg-byes do not. Scorebook errors here corrupt the average silently. Fourth: run outs. They are not bowler wickets; including them flatters the average dishonestly. Fifth: the tiny sample. Three wickets for 30 runs is a 10.00 average and a meaningless one; averages need seasons, not spells.

Second Worked Example: The All-Rounder's Season

A club all-rounder bowls 120 overs in a season, concedes 480 runs, and takes 18 wickets. The average is 480 divided by 18, which is 26.67. That is a genuinely good club number: anything under 30 at amateur level means you are taking wickets without leaking runs. Now compare a teammate who takes 22 wickets but concedes 660 runs: average 30.00. The second bowler takes more wickets but costs more per wicket, and the average captures that trade exactly. Enter both sets of figures above to settle the debate with arithmetic instead of opinions.

Average vs Strike Rate vs Economy: Which Tells the Truth

Bowling average answers one question: how many runs per wicket. Two related stats answer the others. Strike rate is balls per wicket, which measures wicket-taking speed; economy is runs per over, which measures control. A Test bowler with an average of 25 and a strike rate of 50 takes wickets fast and cheaply: the classic great. A bowler with an average of 25 but a strike rate of 75 is economical but slow to strike, the holding bowler every attack needs. All three matter, and the greats of each era lead in at least two.

Format changes which stat rules. In Tests, average is king because wickets win matches and time is abundant. In T20s, economy often matters more than average: a bowler who goes for 6 an over without taking wickets still did their job. Judge a bowler by the stat their format rewards, not by a single number dragged across all three.

Reading an Average in Context

Raw averages mislead without context. A Test average of 28 in the 1990s, on uncovered-era-style pitches against great batting lineups, meant more than the same number on modern flat tracks. Home-away splits matter too: many fine bowlers average 5 runs better at home. And early-career averages lie in both directions: a young bowler's 40 after 5 Tests usually improves, while a veteran's 22 after a short peak usually regresses. The number is honest; the sample size is what needs interrogating.