Strike rate and batting average are the two numbers used most often to judge a batter, and they answer different questions. The average tells you how many runs a batter usually makes before getting out, while the strike rate tells you how fast they score. This guide explains both with clear formulas and worked examples using everyday numbers.
What batting average actually measures
Batting average is total runs divided by the number of times the batter was dismissed. The formula is simple: runs scored divided by times out. Notice it is not divided by innings played, because not-out innings are treated differently.
Say a batter scores 450 runs across a season and is dismissed 10 times. Their average is 450 divided by 10, which equals 45.00. That means, on average, this batter is worth 45 runs every time they bat to completion. A career Test average above 50 is considered excellent; around 40 is solid; below 30 is a concern for a specialist batter.
How not-out innings change the average
This part confuses many fans. If a batter plays 12 innings, is out 10 times and not out twice, you still divide by 10, not 12. Suppose those 12 innings produced 500 runs. The average is 500 divided by 10, which is 50.00, not 41.67.
The logic is that a not-out innings was unfinished, so it would be unfair to count it as a full dismissal. This is also why finishers and lower-order batters who are often stranded not out can carry high averages even with modest scores.
What strike rate measures
Strike rate measures scoring speed in white-ball cricket. The formula is runs divided by balls faced, multiplied by 100. It tells you how many runs a batter scores per 100 balls.
If a batter makes 60 runs from 40 balls, the strike rate is 60 divided by 40, which is 1.5, times 100, giving 150.00. That means they would score 150 runs if they faced 100 balls at that pace. In a T20, a strike rate above 140 is strong; in an ODI, somewhere around 90 to 100 is typical for an anchor and higher for an aggressor.
A worked example comparing two batters
Imagine two batters in the same T20:
- Batter A: 45 runs from 25 balls. Strike rate is 45 divided by 25 times 100, which equals 180.00.
- Batter B: 45 runs from 45 balls. Strike rate is 45 divided by 45 times 100, which equals 100.00.
Both scored 45, so their contribution to the average is identical. But Batter A used 20 fewer balls, leaving more deliveries for teammates. In T20 cricket those 20 balls can be worth 30 or more extra runs, which is why strike rate matters so much in the shorter formats.
Why you should read both numbers together
Neither number tells the full story alone. A batter with a high average but a low strike rate may score heavily yet too slowly for a run chase. A batter with a high strike rate but a low average may entertain but get out too often to be trusted. The best limited-overs batters score both quickly and consistently. When you scan a card, reading both alongside the dismissals is easy once you know how to read a cricket scorecard like a pro.
Bowlers have their own mirror-image measures. A bowling strike rate counts balls per wicket and economy counts runs per over, both explained in bowling economy and strike rate in cricket. And when teams finish level, the tie-break uses scoring rates, as our piece on net run rate in cricket explains.
How format changes what is a good number
Context is everything. In Tests, average is king and strike rate is secondary, though a quick-scoring Test batter is valuable. In ODIs, a balance is needed. In T20s, strike rate often outweighs average because survival matters less than fast runs. A T20 opener averaging 28 at a strike rate of 150 can be more useful than one averaging 40 at a strike rate of 110. The lesson is to weigh the numbers against the job the batter is asked to do, the format being played and the stage of the innings, rather than crowning whoever happens to have the bigger figure on paper.
Common mistakes when reading these numbers
Beginners often misread strike rate and batting average in three ways. First, they divide runs by innings instead of dismissals, which undercounts the average for players with many not-outs. Second, they compare strike rates across formats, forgetting that 130 is excellent in an ODI but only fair in a T20. Third, they judge a batter on a single big score rather than a body of work.
Consider a player with scores of 0, 5, 8, 120 not out and 4 across five innings, out four times. The runs total 137, so the average is 137 divided by 4, which equals 34.25. The lone century flatters the picture, while the average and a glance at the other scores reveal an inconsistent run of form. Reading the numbers together with the actual scores stops one innings from fooling you.
It also helps to set a baseline for each role. Top-order batters are expected to average more because they face the new ball with the whole innings ahead of them, while finishers may average less but strike faster. Comparing a player only with others in the same role and format keeps your judgement fair. And remember these are long-run expectations, not guarantees: a batter averaging 45 will still fail sometimes, and the average simply describes what to expect over many innings.
Worked example: building a season average step by step
The fastest way to lock in the formula is to total a short run of innings yourself. Suppose a batter plays six innings in a season with these scores, where an asterisk means not out:
| Innings | Score | Out? |
|---|---|---|
| 1 | 30 | Out |
| 2 | 0 | Out |
| 3 | 72 | Out |
| 4 | 45* | Not out |
| 5 | 18 | Out |
| 6 | 55 | Out |
Add the runs: 30 plus 0 plus 72 plus 45 plus 18 plus 55 equals 220 runs. Count the dismissals: the batter was out five times, not six, because innings four was unbeaten. The average is 220 divided by 5, which equals 44.00. If you wrongly divided by six innings you would get 36.67, undercounting the player by more than seven runs. That single not-out is the whole difference.
How averages differ by batting position
A fair comparison only works within the same role. Top-order batters face the new ball with the full innings ahead of them, so they are expected to average more. Lower-order batters and finishers often have smaller averages but score faster and are frequently left not out. Rough expectations across a limited-overs career look like this:
- Opener or number three: a career average around 40-plus is strong, because they have the most batting time.
- Middle order (four to six): averages of 35 to 45 are solid, often with a higher strike rate.
- Finisher or all-rounder: an average in the low 30s can be excellent if the strike rate is very high and many innings end not out.
So a number seven averaging 32 at a strike rate of 145 may be doing a harder, more valuable job than an opener averaging 38 at a strike rate of 120. Judge the number against the position, not in isolation.
Quick benchmarks for what counts as a good number
Keep these rough guides in mind when you scan a scorecard. For batting average, a Test figure above 50 is excellent, 40 is solid and below 30 worries selectors. For strike rate, a T20 figure above 140 is strong and above 160 is destructive, an ODI strike rate near 90 to 100 suits an anchor and 110-plus suits an aggressor, while in Tests strike rate is barely used to rank batters at all. Remember these are long-run expectations, not promises: even a batter averaging 50 will be dismissed cheaply now and then, and the average simply describes the typical outcome across many innings.
Frequently asked questions
Is a higher batting average always better?
Generally yes for consistency, but it depends on the format and role. A high average shows the batter rarely gets out cheaply. In T20 cricket, though, a slightly lower average paired with a high strike rate can be more valuable because fast runs free up balls for teammates.
Why is strike rate not used much in Test cricket?
Test matches last up to five days, so survival and big totals matter more than speed. Batting average is the main measure of a Test batter. Strike rate is still noted, since quick runs can set up a declaration, but it is treated as secondary to average and consistency.
Can a batter have an average higher than their highest score?
No. The average can never exceed the highest single score unless the batter has been not out many times. Frequent not-outs inflate the average because runs are divided by dismissals only, so a string of unbeaten innings can push the average up sharply.
How do I calculate strike rate quickly in my head?
Divide runs by balls and shift the decimal two places. For 30 runs off 20 balls, 30 divided by 20 is 1.5, so the strike rate is 150. For an even split like 40 off 40, the strike rate is exactly 100. With practice you can estimate it instantly.
What is a good strike rate in the IPL?
In the IPL a batting strike rate above 140 is good and above 150 is very strong, especially for middle-order hitters. Openers who bat longer may sit a little lower, around 130 to 140, because they balance survival with scoring. At the death, finishers often strike at 180 or more.
Does getting out for a duck lower your strike rate?
A nought off no balls does not change a strike rate, because you cannot divide by zero balls. A nought off several balls does lower it, since you scored no runs while using up deliveries. A duck always hurts the batting average, as it counts as a dismissal for zero runs.
Conclusion
Strike rate and batting average together give you a quick, honest read on any batter. The average shows how many runs they make before getting out, and the strike rate shows how fast they score. Learn the two formulas, try them on a live scorecard, and you will judge batters far more accurately than relying on runs alone.
