Stats hub

Cricket Stats, Explained the Simple Way

Numbers tell the hidden story of every match. Our cricket stats hub explains the key batting, bowling and team metrics with simple formulas and real-match examples, so you can read any scorecard like an analyst.

Batting Stats

StatFormulaWhat it tells you
Batting AverageRuns ÷ Times dismissedHow many runs a batter scores per dismissal — the classic measure of consistency.
Strike Rate(Runs ÷ Balls faced) × 100Scoring speed. Vital in T20, where 140+ is strong for a top-order batter.
Boundary %(Runs from 4s and 6s ÷ Total runs) × 100How much a batter relies on boundaries versus running.
Dot Ball %(Dot balls faced ÷ Balls faced) × 100How often a batter gets stuck — lower is better in limited-overs cricket.
Conversion Rate100s ÷ (50s + 100s)How often a batter turns a fifty into a hundred.

Bowling Stats

StatFormulaWhat it tells you
Bowling AverageRuns conceded ÷ WicketsRuns a bowler gives away for each wicket — lower is better.
Economy RateRuns conceded ÷ Overs bowledRuns per over. In T20 cricket, an economy under 7.5 is usually very good.
Bowling Strike RateBalls bowled ÷ WicketsHow many deliveries a bowler needs per wicket.
Dot Ball %(Dot balls ÷ Balls bowled) × 100Pressure created — a key sign of control in white-ball cricket.

Team Stats That Decide Tournaments

🧮

Net Run Rate (NRR)

Run rate scored minus run rate conceded across a tournament. It separates teams level on points.

How NRR works →
⚔️

Head-to-Head Record

Wins and losses between two teams, best read alongside recent matches and the venue.

🏟️

Venue Averages

Average first-innings score, chasing success and pace-vs-spin wicket split at a ground.

Read pitch guide →
⏱️

Phase Stats

Runs and wickets in the powerplay, middle overs and death overs — where T20 games are won.

How to Use Stats Without Being Misled

Stats are powerful, but only with context. Keep these rules in mind:

  • Sample size matters. A batter averaging 80 after four innings tells you far less than one averaging 45 after eighty innings.
  • Compare like with like. A strike rate of 130 is ordinary for a T20 opener but excellent in an ODI.
  • Check the conditions. Bowling averages built on seaming pitches may not travel to flat, dry tracks.
  • Look at recent data. A player’s last 12 months often matter more than career figures.
  • Pair numbers with roles. A finisher’s average is naturally lower because they often bat with little time left.

For a deeper walkthrough with worked examples, read our full guide to cricket stats explained.

Got a Stats Question?

Not sure how a number is calculated or what it means for the next match? Ask our desk.

Scroll to Top