Open any scorecard and you will see a wall of numbers: runs, balls, fours, sixes, overs, maidens, wickets, averages and strike rates. For a new fan, it can feel overwhelming. For an experienced follower, these same numbers tell a rich story about how a match was won and lost.
In this guide, we explain the most important cricket stats in simple language, with formulas and worked examples. By the end, you will know what each stat measures, when it matters most and how to use player stats to compare cricketers fairly.
Why cricket stats matter
Cricket has always been a numbers game. Statistics help us measure consistency, scoring speed, control and wicket-taking ability. They help selectors pick teams, captains plan tactics and fans understand performances beyond the highlights.
But stats are only useful when you understand what they measure — and what they do not. A high batting average does not always mean a batter is the best choice for a T20 side, and a low economy rate does not always mean a bowler is taking wickets. Context is everything, and we will cover that too.
Batting stats
Runs
The simplest stat of all. Runs are the total number of runs a batter has scored. On their own, they tell you about volume, but not about consistency or speed. A batter who has played 200 innings will naturally have more runs than one who has played 40.
Batting average
Batting average is the classic measure of consistency.
Formula: Batting average = Total runs ÷ Number of times dismissed
Note that the divisor is the number of dismissals, not the number of innings. If a batter is not out, that innings adds runs but does not add a dismissal.
Example: A batter scores 450 runs in 12 innings and is not out three times. They have been dismissed 9 times. Their average is 450 ÷ 9 = 50.00.
In Test cricket, an average above 40 is generally considered very good, and above 50 is excellent. In ODIs, similar benchmarks apply for top-order batters. In T20 cricket, averages are naturally lower because batters take more risks.
Strike rate
Strike rate measures how quickly a batter scores.
Formula: Strike rate = (Runs scored ÷ Balls faced) × 100
Example: A batter scores 60 runs off 40 balls. Their strike rate is (60 ÷ 40) × 100 = 150.00.
Strike rate is most important in limited-overs cricket. In T20, a strike rate above 140 is usually strong for a top-order batter, while finishers are often expected to score even faster. In Test cricket, strike rate matters less, because time is rarely the main constraint.
Balls faced
Balls faced is a simple count of legal deliveries a batter has faced. It is useful because it shows how long a batter stayed at the crease and is needed to calculate strike rate.
Fifties and hundreds
Fifties (50s) and hundreds (100s) count the number of innings in which a batter reached 50 and 100 runs. They show a batter’s ability to play big innings.
A related idea is the conversion rate — how often a batter turns a fifty into a hundred.
Formula: Conversion rate = Hundreds ÷ (Fifties + Hundreds)
Example: A batter has 20 fifties and 10 hundreds. Their conversion rate is 10 ÷ 30 = 33%.
Boundary percentage
Boundary percentage shows how much of a batter’s scoring comes from fours and sixes.
Formula: Boundary % = (Runs from boundaries ÷ Total runs) × 100
Example: A batter scores 80 runs, including 8 fours (32 runs) and 4 sixes (24 runs). Boundary runs are 56. Their boundary percentage is (56 ÷ 80) × 100 = 70%.
A high boundary percentage suggests a power hitter. A lower percentage combined with a good strike rate suggests a batter who runs hard and rotates the strike well.
Dot-ball percentage (batting)
Dot-ball percentage shows how often a batter fails to score off a delivery.
Formula: Dot-ball % = (Dot balls faced ÷ Balls faced) × 100
In T20 cricket, keeping this number low is crucial. A batter who plays too many dot balls puts pressure on the rest of the line-up, even if they eventually score runs.
Bowling stats
Wickets
Wickets are the number of dismissals credited to a bowler. Run-outs are not credited to the bowler, but catches, bowled, LBW and stumpings are.
Bowling average
Bowling average measures how many runs a bowler concedes for each wicket.
Formula: Bowling average = Runs conceded ÷ Wickets taken
Example: A bowler concedes 600 runs and takes 24 wickets. Their bowling average is 600 ÷ 24 = 25.00.
Lower is better. In Test cricket, a bowling average under 30 is generally considered good, and under 25 is excellent.
Economy rate
Economy rate measures how many runs a bowler concedes per over.
Formula: Economy rate = Runs conceded ÷ Overs bowled
Example: A bowler concedes 28 runs in 4 overs. Their economy rate is 28 ÷ 4 = 7.00.
When overs are not complete, convert them properly: 3.3 overs means 3 overs and 3 balls, which is 3.5 overs in decimal terms. In T20 cricket, an economy rate under 7.5 is usually very good, although this depends heavily on the venue and the phase of the innings in which the bowler operates.
Bowling strike rate
Bowling strike rate shows how many balls a bowler needs, on average, to take a wicket.
Formula: Bowling strike rate = Balls bowled ÷ Wickets taken
Example: A bowler bowls 480 balls and takes 20 wickets. Their strike rate is 480 ÷ 20 = 24.0.
Lower is better. A low bowling strike rate means the bowler takes wickets frequently, which is especially valuable in Test cricket, where you need to take 20 wickets to win.
Dot-ball percentage (bowling)
For bowlers, dot-ball percentage is a measure of control and pressure.
Formula: Dot-ball % = (Dot balls bowled ÷ Total balls bowled) × 100
Bowlers who bowl lots of dot balls build pressure that often leads to wickets at the other end, even if they do not take many wickets themselves.
Maidens
A maiden is an over in which a bowler concedes no runs that count against them. Maidens are common in Test cricket and rare in T20 cricket, where a single maiden can be a match-changing achievement.
Quick reference table
| Stat | Formula | Better when |
|---|---|---|
| Batting average | Runs ÷ Dismissals | Higher |
| Strike rate (batting) | (Runs ÷ Balls) × 100 | Higher |
| Boundary % | (Boundary runs ÷ Runs) × 100 | Depends on role |
| Bowling average | Runs conceded ÷ Wickets | Lower |
| Economy rate | Runs conceded ÷ Overs | Lower |
| Bowling strike rate | Balls ÷ Wickets | Lower |
| Dot-ball % (bowling) | (Dot balls ÷ Balls) × 100 | Higher |
Team stats
Run rate
Run rate is the average number of runs a team scores per over.
Formula: Run rate = Total runs ÷ Overs faced
The required run rate in a chase is the runs still needed divided by the overs remaining.
Net run rate
Net run rate (NRR) is used in tournaments to separate teams that are level on points. It compares the rate at which a team scores with the rate at which it concedes runs. We explain it in full, with examples, in our IPL points table and NRR guide.
Head-to-head record
The head-to-head record shows how two teams have performed against each other. It is most useful when you look at recent matches in the same format and similar conditions.
How to compare players fairly
Stats are powerful, but they can mislead if you use them without context. Here are the rules analysts follow.
Compare within the same format
A strike rate of 90 is excellent in Test cricket and poor for a T20 opener. Always compare players using stats from the same format.
Consider the role
A finisher who bats at number six often comes in with only a few overs left. Their average will naturally be lower and their strike rate higher than an opener’s. A death-overs bowler will usually have a higher economy rate than a bowler who operates in the middle overs.
Check the sample size
Small samples can be misleading. A batter averaging 90 after five innings has not proven as much as one averaging 45 after a hundred innings. Look for larger samples before drawing firm conclusions.
Look at recent form
Career numbers include matches from many years ago. For predictions and team selection, the last 12 months often matter more than overall career figures.
Account for conditions
Some players do brilliantly in certain conditions and struggle in others. A spinner’s average on dry pitches may look very different from their average on green, bouncy surfaces. Splitting stats by venue or by home and away can reveal these patterns.
Using stats in match previews
At CricketID, stats are a central part of every match preview. We use recent batting averages and strike rates to judge form, bowling economy and strike rates to judge attacks, phase-wise stats to understand where a match will be won, and venue stats to understand the pitch.
But we always combine the numbers with context: the role of each player, the conditions and the opposition. Stats point you towards the right questions — the analysis answers them.
Frequently asked questions
What is a good strike rate in T20 cricket?
For top-order batters, a strike rate above 140 is generally considered strong in modern T20 cricket. Finishers often aim even higher. The ideal number depends on the pitch and the phase of the innings.
Is batting average or strike rate more important?
It depends on the format. In Test cricket, average usually matters more because time is rarely short. In T20 cricket, strike rate is often more important. In ODIs, both matter roughly equally.
Why is economy rate important for bowlers?
Economy rate shows how well a bowler controls the scoring. In limited-overs cricket, a bowler who concedes few runs builds pressure that often leads to wickets for the whole team.
How do I calculate economy rate with incomplete overs?
Convert the balls to a fraction of an over. For example, 3.3 overs means 3 overs and 3 balls, which is 3.5 overs. If a bowler concedes 21 runs in 3.3 overs, the economy rate is 21 ÷ 3.5 = 6.00.
Final thoughts
Once you understand the core cricket stats — batting average, strike rate, bowling average, economy rate and bowling strike rate — every scorecard becomes a story you can read. Add context like role, sample size, recent form and conditions, and you will be able to compare players and judge performances like an analyst.
For more, visit our cricket stats hub or message the CricketID desk on WhatsApp with any stats question.
Have a question about this match or stat?
Message our cricket desk on WhatsApp or drop us a line — we love talking cricket.