Cricket Statistics Explained: Batting Average, Strike Rate, Economy and Required Run Rate
What every number on a cricket scorecard measures, how each is calculated — with worked examples — and the overs notation mistake that corrupts run rates.
Cricket keeps score in more numbers than any other major sport, and most of them are ratios rather than counts. A batter "averaging 42.95" has never scored 42.95 of anything; a bowler "going at 4.78" isn't measured against a clock. This guide walks through the six statistics that carry a scorecard — what each one measures, exactly how it's calculated, and the one notation trap that produces confidently wrong answers even from people who have watched cricket their whole lives.
Batting average: runs per dismissal, not per innings
A batting average is runs scored ÷ times dismissed — not divided by innings played. The distinction matters because not-out innings add runs to the numerator without adding anything to the denominator.
Take a batter with 1,847 career runs who has been dismissed 43 times: 1,847 ÷ 43 = 42.95. If that batter has actually played 51 innings but finished not out in 8 of them, dividing by innings would give 36.2 — a different and wrong number. This is why late-order batters who frequently finish not out can carry averages that look inflated next to their run totals, and it is a genuine (and endless) debate in the game rather than a flaw in the arithmetic. The cricket batting average calculator handles the not-out adjustment for you — enter innings and not-outs and it derives the dismissals.
Strike rate: two stats with one name
Cricket uses "strike rate" for two completely different measurements, and they point in opposite directions.
Batting strike rate is runs per 100 balls: (runs ÷ balls faced) × 100. A batter with 1,847 runs off 2,210 balls has a strike rate of 83.57 — they score at about 84 runs per hundred deliveries. Higher is better, and what counts as good depends entirely on format: 83 is brisk in a Test match and slow in a T20. Work out any combination with the batting strike rate calculator.
Bowling strike rate is balls per wicket — lower is better. The name collision confuses newcomers constantly; when someone quotes a strike rate, the first question is always batting or bowling?
Bowling average and economy: cost per wicket vs cost per over
A bowler's two headline numbers answer different questions. The bowling average — runs conceded ÷ wickets taken — asks what does each wicket cost? A bowler who has conceded 890 runs while taking 31 wickets averages 890 ÷ 31 = 28.71. The bowling average calculator also shows how a single cheap wicket moves the number.
The economy rate — runs conceded ÷ overs bowled — asks what does each over cost? and it is where the notation trap lives.
The 32.4 overs trap
Cricket writes overs in a notation that looks decimal and isn't. "32.4 overs" means 32 overs and 4 balls — and since an over is 6 balls, that's 32⁴⁄₆ = 32.667 overs of actual bowling, not 32.4.
Say a bowling side has conceded 156 runs in 32.4 overs. The correct economy rate is:
| Method | Arithmetic | Result |
|---|---|---|
| Correct: convert balls first | 156 ÷ (32 + 4/6) = 156 ÷ 32.667 | 4.78 |
| Wrong: treat 32.4 as decimal | 156 ÷ 32.4 | 4.81 |
Three hundredths of a run per over sounds trivial until a tournament spot turns on net run rate — where the same mistake, made across a whole innings figure, routinely flips qualification scenarios. The economy rate calculator accepts scorecard notation directly (32.4 means 32 overs 4 balls) and does the conversion internally, which is the entire reason it exists.
Required run rate: the chase, quantified
The number that makes run chases dramatic is simple division kept continuously updated: runs still needed ÷ overs remaining (with those overs converted from balls properly, as above).
A worked chase: the target is 287 in a 50-over match, and the batting side has 154 after 31.2 overs. They need 133 more runs. The overs remaining are 50 − 31.333 = 18.667 (31.2 = 31 overs 2 balls = 31.333). Required rate: 133 ÷ 18.667 = 7.13 runs per over. Every dot ball nudges it up; every boundary drops it. The required run rate calculator recomputes the whole picture from the current score line — it's the tool to keep open during a chase.
Net run rate: how tournaments break ties
When two teams finish level on points, most tournaments rank them by net run rate:
NRR = (runs scored ÷ overs faced) − (runs conceded ÷ overs bowled)
A team that scored 268 in its full 50 overs and bowled its opponent out for 240 in 48.3 overs has: 268 ÷ 50 = 5.360 for, and — because a side bowled out is charged its full allocation of overs, not the 48.3 it actually lasted — 240 ÷ 50 = 4.800 against, for an NRR of +0.56. That full-allocation rule surprises almost everyone the first time; had the naive 48.3-as-decimal figure been used instead, the answer would drift twice over. The balls-notation conversion still matters on the other side of the ledger: when an innings ends with wickets in hand — a successful chase, say, reaching the target in 44.3 overs — those 44.3 scorecard overs must become 44.5 real overs before dividing. The net run rate calculator applies both rules, which is why club scorers use one instead of a spreadsheet.
Quick reference
| Statistic | Formula | Better when |
|---|---|---|
| Batting average | runs ÷ dismissals | Higher |
| Batting strike rate | runs ÷ balls × 100 | Higher |
| Bowling average | runs conceded ÷ wickets | Lower |
| Bowling strike rate | balls ÷ wickets | Lower |
| Economy rate | runs ÷ overs (balls converted) | Lower |
| Required run rate | runs needed ÷ overs left | — |
| Net run rate | scoring rate − concession rate | Higher |
Why the ratios, not totals?
Because cricket's formats vary so wildly in length, raw totals can't compare players. Ratios normalize: an average compares a Test opener to a T20 finisher on the same scale (imperfectly — the strike-rate context matters); an economy rate compares a bowler's four-over spell to another's twenty-five-over marathon. Every statistic above is a rate for exactly this reason, and each of the Quanta calculators linked here shows its formula and a worked example on the page, so you can check the arithmetic by hand — the same way this guide does.
Spotted an edge case these tools don't handle, or a statistic you'd like added? Tell us — scorer-reported corner cases are how these calculators got their overs-notation handling in the first place.