Bowling Average Calculator - Runs Conceded per Wicket

A bowling average calculator works out a cricket bowler's bowling average by dividing the runs they have conceded by the wickets they have taken. In cricket a bowling average is the number of runs a bowler gives away for each wicket, and the lower it is, the better the bowler is performing.

• • Comparing bowlers: Rank two bowlers on who concedes fewer runs per wicket across a season or a career.
• • Reading a scorecard: Turn raw runs and wickets into the single average that scorecards and tables report.
• • Tracking form: Watch whether a spell pulls a season average down or pushes it up as more wickets arrive.

The average is a ratio, not a count. A bowler who concedes 320 runs for 10 wickets has an average of 32, meaning each wicket cost the batting side 32 runs; conceding 147 for 6 wickets drops that to 24.5.

Our bowling average calculator is built for exactly this: you type the runs conceded and the wickets taken, and it returns the average without you reaching for a division or a scorecard archive.

Because the number rewards wicket-taking as much as run-saving, it captures bowlers who buy wickets even when they leak a few runs, which a pure runs total would hide.

A bowling average measures how cheaply a bowler takes wickets, while the cricket batting average calculator measures how productively a batter scores, so the two together describe a player's full contribution.

The tool applies the standard cricket definition: bowling average equals runs conceded divided by wickets taken. It then optionally derives economy rate and strike rate when you also enter balls bowled.

• Runs Conceded: Total runs the bowler has given away, including extras such as wides and no-balls.
• Wickets Taken: Total dismissals credited to the bowler.
• Balls Bowled: Optional total balls, used to derive economy rate (runs per over) and strike rate (balls per wicket).

If you also enter balls bowled, the calculator reports economy rate as runs conceded per six-ball over and strike rate as balls bowled per wicket, two companions that the average alone does not show.

Just as the batting strike rate calculator expresses scoring speed per 100 balls, a bowling average expresses cost per wicket, so both are rates that summarise a performance in one number.

Because the average is a single ratio, it hides the pace of wicket-taking. A bowler with a tidy number built from only a couple of dismissals may look better than a strike bowler who leaks runs while taking wickets quickly.

According to Wikipedia - Bowling average, In cricket, a player's bowling average is the number of runs they have conceded per wicket taken, and the lower the bowling average is, the better the bowler is performing. It is commonly used alongside economy rate and strike rate.

Just as the batting strike rate calculator expresses scoring speed per 100 balls, a bowling average expresses cost per wicket, so both are rates that summarise a performance in one number.

Four ideas sit behind every bowling average. Understanding them keeps the number honest and stops small samples from misleading you.

The average answers 'how costly', strike rate answers 'how fast', and economy answers 'how leaky'. Reading all three stops a bowler with a flattering average on a tiny sample from looking elite.

Elite career figures sit around 20 and below; George Lohmann's Test career average of 10.75 is the lowest on record, which shows how far a careful bowler can pull the ratio down.

Treat the average as a cumulative tally, not a per-match figure. Every new wicket and every new run shifts it, which is why a few cheap wickets early in a career can still move it sharply.

Bowling average belongs to a family of cricket summary stats; the net run rate calculator rolls team batting and bowling into a single match-level rate that tournament tables use to rank sides.

Enter your bowler's running totals and the tool returns the average, plus economy and strike rate when you add balls. Follow these steps for a clean result.

1. 1 Enter runs conceded: Add up every run the bowler has given away, including wides and no-balls credited against the bowler.
2. 2 Enter wickets taken: Count the dismissals credited to the bowler across the same span of matches.
3. 3 Add balls bowled (optional): Type the total balls if you want economy rate and bowling strike rate alongside the average.
4. 4 Read the average: The main result is runs conceded per wicket, shown to two decimals.
5. 5 Compare across spells: Re-run with a season total versus a single match to see how the average moves.

A bowler has conceded 320 runs for 10 wickets from 600 balls. The calculator returns a bowling average of 32.00, an economy rate of 3.20 runs per over, and a strike rate of 60.0 balls per wicket.

When a match is shortened, the target set by the Duckworth-Lewis calculator changes how many runs a bowler concedes against a revised total, which feeds straight back into their average.

Working the division by hand is fine for one spell but error-prone across a season of scorecards. A dedicated tool keeps the arithmetic exact and the companions in view.

• • One number from two inputs: Runs and wickets become a clean average without you doing the division by hand.
• • Companion stats on demand: Add balls bowled and the same entry returns economy and strike rate, the two figures selectors weigh with the average.
• • Honest small-sample view: The tool shows a null average when no wickets are taken, instead of pretending a bowler who has never struck is perfect.
• • Season versus career tracking: Re-enter running totals after each match to watch the average drift as form changes.

Because the average, economy, and strike rate all sit in one panel, you avoid the common trap of praising a low average that came from only a couple of wickets.

Coaches can reverse the tool too: set a target average and total wickets, then see how many runs a bowler can afford to concede before the average slips past it.

For selection meetings the three rates together are far more useful than any single one, because they separate the bowler who buys wickets from the one who simply bowls tidily.

A bowler building a low average helps a side enforce the follow-on, and the cricket follow-on calculator shows the first-innings lead a team needs to force that decision.

Two inputs decide the average, and a few caveats decide whether you should trust it. Knowing them stops the number from misleading you.

• • With zero wickets the average is undefined, so the tool reports it as not available rather than a misleading number.
• • On a small wicket count the average is unstable; a single expensive or cheap spell can swing it sharply, so qualification rules usually apply before ranking.

The average also hides how wickets were taken. A bowler with a 25 average from 200 balls is far more threatening than one with the same 25 from 600 balls, which is exactly why strike rate matters alongside it.

Surfaces and match format shift the baseline too: T20 averages run higher than Test averages because batters attack and boundaries flow, so compare averages only within the same format.

According to Wikipedia - Bowling average (small-sample caveat), When a bowler has taken only a small number of wickets, their bowling average can be artificially high or low and unstable, which is why qualification restrictions are generally applied before ranking the best bowling averages.

Other sports use a single rate to judge productivity in the same spirit: baseball's on-base percentage calculator summarises how often a batter reaches base, just as a bowling average summarises how costly each wicket was.