Cricket Analytics 101: Strike Rate, Economy and the Story Behind the Numbers

Not long ago, cricket was understood almost entirely through runs, wickets and averages. Since the T20 and data revolutions, commentators talk constantly about strike rates, economy, dot-ball percentage and boundary percentage. If that sounds confusing, this guide is for you.

Basic batting numbers

Batting average = runs scored ÷ number of dismissals

The average tells you how many runs a batter typically scores before getting out. In Test cricket it remains the most important single number.

Strike rate = (runs ÷ balls faced) × 100

Strike rate tells you how quickly a batter scores: 150 runs off 100 balls is a strike rate of 150. In T20 it matters as much as average – sometimes more.

A simple example: 30 runs off 40 balls is a strike rate of 75. That's fine in a Test, but in the death overs of a T20 it can lose a match.

Basic bowling numbers

• Economy rate = runs conceded ÷ overs bowled – runs given away per over.
• Bowling average = runs conceded ÷ wickets taken – the "cost" of each wicket.
• Bowling strike rate = balls bowled ÷ wickets taken – how often a bowler strikes.

In Tests, strike rate shows how penetrative a bowler is. In T20, economy often matters more, because saving runs is as valuable as taking wickets.

Advanced metrics: the story inside the numbers

Dot-ball percentage: the share of deliveries with no run scored. Dots build pressure, and pressure brings wickets.

Boundary percentage: how many of a batter's runs come in fours and sixes – the difference between a power-hitter and a strike-rotator.

Phase-wise stats: the same batter may have very different strike rates in the powerplay, middle overs and death overs. Teams now judge players by phase rather than overall.

Match-ups: who struggles against left-arm spin, which bowler dismisses left-handers more often – this data guides captains' bowling changes.

The graphics you see on TV

• Wagon wheel: where a batter's shots went around the ground.
• Pitch map: the line and length a bowler landed the ball.
• Beehive: the height and line at which balls reached the batter.
• Worm graph: an over-by-over comparison of both teams' innings.

Watch these closely and you'll see the bowler's plan – and how the batter tried to break it.

The limits of numbers

Stats tell you a lot, but not everything. A 25-run cameo on a difficult pitch can be worth more than 80 on a flat one. Match situation, conditions, the quality of the opposition and pressure don't fully show up in the numbers. That's why experts say: "Look at the data, but watch the match too."

Getting started yourself

1. Keep a scorebook for your local games and calculate each player's strike rate and economy.
2. Build a simple spreadsheet tracking runs and wickets by phase.
3. Pay attention to the wagon wheel and pitch map while watching on TV.

You can also try the calculators on our Stats page. Gradually you'll find yourself reading matches from a whole new angle – just like an analyst.

Also read: The Auction Chessboard: How T20 Franchises Build Their Squads · Test vs ODI vs T20: The Complete Guide to Cricket's Three Formats