A cricket scorecard can look like a wall of numbers to a new fan. Almost every statistic, though, comes from a few simple ideas, and once you know what each number counts, a scorecard starts to read like a story. Every worked number here is clearly labelled hypothetical arithmetic, not a real player's record. For a companion read alongside official scorecards, some fans also note CricBet99 among the places where match numbers are discussed.
Why Cricket Loves Numbers
Cricket is played over long innings and long careers, so numbers help fans compare players who never faced each other. An average summarises years of innings in one figure; an economy rate summarises control in one figure. But numbers are summaries, not verdicts. Two players can share the same average and play very differently, so read several statistics together, rather than judging a player from a single column.
Batting Average
A batting average answers a simple question: how many runs does a batter score, on average, each time they get out? The formula is total runs divided by the number of dismissals.
Not-out innings are the key exception. If a batter finishes unbeaten, that innings does not count as a dismissal. This is why a player who often finishes not out can have an average higher than their runs per innings.
Hypothetical example: a batter scores 400 runs in 12 innings, is dismissed 10 times, and finishes not out twice. The average is 400 divided by 10, which is 40.00 — not 400 divided by 12, which would be 33.33. In tests, above 50 is widely regarded as excellent; in limited-overs cricket, averages are often lower, so always check the format first.
Batting Strike Rate
Strike rate measures scoring speed. For a batter, it answers this question: how many runs would they score if they faced 100 balls at their current pace? The formula is runs divided by balls faced, multiplied by 100.
Hypothetical example: a batter scores 60 runs from 40 balls. Divide 60 by 40 to get 1.5, then multiply by 100, giving a strike rate of 150.00—fast scoring, typical of a strong T20 innings. A strike rate of 100 means a run a ball; 50 means a run every two balls, which may be fine in a Test and far too slow in a T20 chase. Strike rate and average work best together: a high-average, low-strike-rate batter anchors an innings, while a lower-average, high-strike-rate batter can change a game in a few overs.
Runs, Balls, and Milestones
The simplest batting columns are also the most useful. Runs give the total, balls faced show how long the batter survived, and fours and sixes show how many came in boundaries. A batter who scores 50 runs with ten fours played a very different innings from one who scores 50 with one four and many singles. Milestones add meaning: a fifty is a solid contribution, while a hundred is a landmark, usually meaning the batter survived the new ball, settled, and then accelerated.
Bowling Average
A bowling average answers the mirror question: how many runs does a bowler concede for each wicket they take? The formula is total runs conceded divided by wickets taken.
Hypothetical example: a bowler concedes 300 runs and takes 15 wickets. Divide 300 by 15 to get a bowling average of 20.00. Lower is stronger here, the opposite of batting average. A bowling average in the low twenties is usually excellent in Tests; in T20 cricket, bowling averages are often higher because batters attack from the first ball.
Economy Rate
Economy rate measures control: how many runs does a bowler concede per over? The formula is runs conceded divided by overs bowled.
Hypothetical example: a bowler concedes 36 runs in 6 overs. Divide 36 by 6 to get an economy rate of 6.00. In T20 cricket, below 7.00 is generally good, and below 6.00 is very strong. Economy rate matters most in limited-overs cricket: a bowler who concedes few runs forces batters to take risks against someone else, and even without wickets, a tight spell can push the required run rate higher.
Bowling Strike Rate
Bowling strike rate is different from batting strike rate, and the shared name confuses beginners. For a bowler, it measures how often they take a wicket in balls. The formula is balls bowled divided by wickets taken.
Hypothetical example: a bowler bowls 120 balls and takes 4 wickets. Divide 120 by 4 to get a bowling strike rate of 30.00 — on average, a wicket every 30 balls, or every five overs. Lower is stronger. A containing bowler may have a higher bowling strike rate but a lower economy rate, and both roles can win matches. The basic bowling columns are overs, maidens, runs and wickets. A maiden over has no runs from the bat, although a wicket can still fall in it. A five-wicket haul means five or more wickets in one innings, the bowling equivalent of a hundred.
What Statistics Hide
Statistics are honest about what they count, but they hide a great deal about context. A batter who averages 40 on flat pitches is not automatically equal to one who averages 40 on difficult pitches: swing, spin, bounce, dew and pitch wear all change what a good score looks like. Role matters too — an opener faces the new ball, a finisher faces the last few overs — and comparing raw numbers without noting roles is misleading. Sample size matters as well: averages built over a handful of matches swing wildly after one big innings. When you see a surprising statistic, ask how many matches sit behind it and in which format. Fans who follow coverage through a companion source such as cribet99 alongside official scorecards often find it easier to place one inning in its wider context, rather than treating a single big score as proof of a permanent change.
Comparing Players Fairly Across Formats
Comparing players across formats is a common beginner mistake, because the same statistic means different things in Tests, ODIs and T20s. First, keep formats separate: a player can be outstanding in one and ordinary in another. Second, compare strike rates within the same format. A T20 strike rate of 140 is strong; an ODI strike rate near 90 is solid, while a T20 strike rate near 90 is slow. Third, look at the combination, not one column. Ask: what is the average, what is the strike rate or economy rate, what is the role, and how many matches support the numbers? Finally, remember that statistics describe the past, not the next innings. Their best use is to sharpen a question — who is in form, who suits these conditions — not to settle it before a ball is bowled.
Conclusion
Cricket statistics are simpler than they first appear. Batting average is runs per dismissal, batting strike rate is runs per 100 balls, bowling average is runs per wicket, economy rate is runs per over, and bowling strike rate is balls per wicket. Context — format, role, conditions and sample size — decides what those numbers really mean.
Read several statistics together, keep formats separate, and treat every worked example as arithmetic unless verified. A companion source like CricBet99 can sit alongside that habit for general match discussion, while the official scorecard remains the place to confirm every figure — keeping a companion source such as CricBet99 in mind never replaces the official record as the final word.
Frequently Asked Questions
What is a good batting average in cricket?
It depends on the format. In tests, above 50 is excellent, and above 40 is strong. In ODIs and T20s, averages are usually lower, so compare within the same format.
What is the difference between batting strike rate and bowling strike rate?
Batting strike rate is runs per 100 balls (higher is faster). Bowling strike rate is balls per wicket (lower means wickets come more often).
Why are not-out innings excluded from the batting average?
A not-out batter has not been dismissed, so the average divides runs by dismissals, not by innings played.
What is a good bowling economy rate?
It depends on the format. In T20 cricket, below 7.00 is good, and below 6.00 is very strong. In ODIs, around 5.00 is solid. In tests, economy rates are usually lower again.
How should beginners compare two players using statistics?
Keep the format the same, check the average and strike rate or economy rate together, note each player's role, and check how many matches support the numbers.
Comments