A scorecard can tell you a batter made 72 and a bowler took 3 for 28, but the numbers that decide selection debates, auction prices and captaincy calls are the ratios sitting underneath those raw totals. Averages, strike rates and economy rates compress thousands of deliveries into a single figure that lets you compare a top-order batter from one era with another, or a death bowler with a new-ball specialist. Each figure answers a different question, and knowing what it measures — and what it hides — is the difference between reading a scorecard and understanding it.
Batting Average: Runs Per Dismissal
The batting average measures how many runs a batter typically scores before getting out. The formula is simple:
Batting average = total runs scored ÷ number of times dismissed.
A batter who scores 500 runs across a season and is dismissed 10 times has an average of 50. Crucially, the denominator is times out, not innings played. Not-out innings count toward the runs but not toward the dismissals, which is why a player who finishes unbeaten regularly — a number eleven who survives, or a finisher who is there at the end — can carry an average that looks higher than their scores alone suggest.
Consider a batter with scores of 40, 0, 60 and 100 not out. That is 200 runs, but only three dismissals, so the average is roughly 66.7, not 50. The average rewards consistency and the ability to convert starts, but it says nothing about how quickly those runs arrived. A player averaging 45 in Test cricket and a player averaging 45 in T20 are doing very different jobs, which is where strike rate enters.
Batting Strike Rate: How Fast the Runs Come
Strike rate captures scoring speed rather than volume. For batters it is expressed per 100 balls:
Batting strike rate = (runs scored ÷ balls faced) × 100.
A batter who makes 60 from 40 balls has a strike rate of 150, meaning they would score 150 runs per 100 deliveries at that tempo. The same 60 runs from 90 balls produces a strike rate of about 67 — identical run value, very different match impact. In Test cricket a strike rate near 50 can be perfectly valuable when the job is to occupy the crease; in a T20 powerplay the same number would be a liability.
Average and strike rate are most powerful read together. A high average with a modest strike rate describes an accumulator who rarely fails but rarely accelerates. A high strike rate with a low average describes a dangerous but inconsistent hitter. Format context shapes which profile a team wants, and the demands change even within an innings — the field restrictions covered in our guide to powerplay rules in limited-overs cricket are exactly why top-order strike rates spike in the first six overs. The mechanics that let a player score quickly without throwing their wicket away are explored in our complete guide to batting technique.
Bowling Average, Strike Rate and Economy
Bowlers are measured by three ratios that, between them, describe cost, frequency and control. They draw on the same raw inputs — runs conceded, wickets taken, balls bowled — but combine them differently.
Bowling average: runs per wicket
Bowling average = runs conceded ÷ wickets taken.
A bowler who concedes 300 runs and takes 15 wickets averages 20 — the runs it costs, on average, to buy each wicket. Lower is better, the mirror image of the batting average. A bowler averaging 22 is, in pure exchange terms, more efficient at taking wickets than one averaging 30.
Bowling strike rate: balls per wicket
Bowling strike rate = balls bowled ÷ wickets taken.
If a bowler sends down 360 balls and takes 12 wickets, the strike rate is 30 — a wicket every 30 deliveries, or once every five overs. This matters most in Test cricket, where taking twenty wickets is the only route to victory; a strike bowler who removes batters quickly is more valuable than the average alone reveals, because time and overs are finite.
Economy rate: runs per over
Economy rate = runs conceded ÷ overs bowled.
A bowler who concedes 48 runs from 8 overs has an economy of 6.00. In limited-overs cricket this is often the headline number, because restricting runs can matter as much as taking wickets. A spinner who goes for 5 an over through the middle and a quick who concedes 9 at the death are judged against entirely different expectations. How those roles divide up — new ball, middle overs, death — and why economy has to be read against them is covered in our complete guide to bowling.
The three figures interlock. A bowler can have a fine economy but a poor strike rate (tidy, but not threatening), or a sharp strike rate with a high economy (takes wickets, but leaks runs doing it). Judging a bowler on one number alone is how scorecards mislead.
Run Rate, Required Run Rate and Net Run Rate
Team-level numbers govern the chase. The run rate is simply runs scored divided by overs faced: 180 runs from 30 overs is a run rate of 6.00. During a chase, the required run rate tells the batting side how fast they must score to win:
Required run rate = runs still needed ÷ overs remaining.
A side needing 90 from the last 10 overs requires 9.00 an over. As the required rate climbs above the current rate, pressure shifts to the batters; as it falls below, the bowling side is under threat. Commentators track the gap between the two ball by ball because it is the truest live measure of who is winning.
Rain complicates all of this. When overs are lost, a simple run rate is unfair to one side, which is why revised targets use a more sophisticated model — explained fully in our breakdown of the Duckworth-Lewis-Stern method.
Net run rate (NRR) is the tournament tie-breaker. Qualitatively, it compares the rate at which a team scores its runs across the competition with the rate at which it concedes them. Score quickly and concede slowly and your NRR is positive; the reverse drags it negative. The important subtlety: when a team is bowled out, its full quota of overs is used in the calculation rather than the overs it actually faced, so collapsing cheaply hurts NRR far more than the scoreline alone implies. It rarely decides a final, but it routinely decides who reaches one.
Why Context Decides What a Number Means
No cricket statistic is meaningful in isolation, because every figure is shaped by the conditions that produced it. The same numbers carry different weight depending on:
- Format. A Test average of 45 and a T20 strike rate of 145 are both excellent, yet they measure almost opposite virtues — endurance versus acceleration.
- Era and pitch. Flat batting decks inflate averages and economy rates alike; bowler-friendly conditions deflate them. Comparing raw numbers across decades without that context is misleading.
- Role. An opener’s strike rate and a finisher’s strike rate answer different briefs, just as a new-ball bowler’s economy is not comparable to a death specialist’s.
Sample size matters too. A bowling average of 12 across three matches tells you very little; the same figure across fifty matches is a genuine signal. The numbers are only as honest as the volume of cricket behind them, and they sit on top of the game’s rules — how a dismissal is recorded, when a delivery counts as a legal ball, how extras are charged. Those foundations are set out in the MCC’s official Laws of Cricket, and in plainer terms in our complete guide to the Laws of cricket.
What to Read Next
Once the core ratios make sense, the natural next step is to see how they play out in real situations. Start with the rules that generate every number on a scorecard in our guide to the Laws of cricket, then look at how strike rate is built through sound stroke-making in our batting technique guide and how economy is managed under pressure in our bowling guide. For the maths that overrides a simple run rate when the weather intervenes, our explainer on the Duckworth-Lewis-Stern method shows how a fair target is calculated when overs are lost.
