Cricket Stats 101: Batting Statistics

An obsession with sports statistics. It's what separates Man from the lesser primates. We start the year obsessing over NBA and NCAA assists, steals, and field goal percentages and NHL penalty-kill numbers. It continues through the spring and summer with MLB earned run averages, slugging percentages, and strike-out-to-walk ratios. And ends with yards-per-carry, touchdown-to-interception ratios, and third-down-efficiency numbers of our favorite NFL and college football players and teams.

Cricket, thankfully, has just as deep a reliance on -- and appreciation for -- numbers, equations, and analysis as anything you're already watching. So, if you’re looking for a new sport to unleash some analytics on, you've come to the right place. (And, unlike the other sports mentioned above, cricket is played 12 months out of the year, so you can worry about things like runs-per-over all year long!)

First, we'll look at batting statistics -- I'll get to bowling stats in another piece. I'll give an overview of the main stats that teams, players, and fans concern themselves with and then look at which statistics are the most relevant for the different formats of the game -- T20, ODI, and Test cricket. It'll help you better understand and enjoy the game and make you a juggernaut in your fantasy cricket leagues.

The most basic way to compare one player to another would be to look at the total number of runs that they've scored over the course of a season or tournament. This becomes muddy, though, when you have players who've played different numbers of innings or games due to injury, team strategy, or any variety of other factors. The sport needed an equation or statistic that would allow folks to compare apples and oranges in a logical and meaningful way.

If we go back about 50 years to the days when there was only multi-day Test cricket, the main stat that people focused on for batters was Batting Average -- the total numbers of runs scored divided by the number of times a batter is out. It's essentially the number of runs scored per wicket lost by the batter. The highest career average is legendary Australian batsman Don Bradman's 99.94. (For comparison, the highest Test average for a current player with at least 20 innings is Harry Brooks' still otherworldly 62.15.) In general, a career Test average of 40 is considered very strong and an average of 50 gets you into the game's elite players. For the most part, Batting Average is a solid way to not only compare batters from different teams but also -- as the sport's obsession with Bradman's 99.94 shows -- a way to compare players from different eras.

The growth of limited overs games -- 50-over ODIs and 20-over T20 matches -- has changed the way the game looks at batting stats. It's no longer good enough to average 30 or 40 or even 50 runs per match; it's now just as important -- if not more important -- to score runs quickly. It's great to average 30 runs per innings, but if it takes you 60 balls to score that 30, you're not going to be too helpful to a T20 lineup that's only going to face 120 balls. (Another issue with Batting Average and limited overs games is that you have a lot of lower order batters that score runs at the end of an innings without being put out. They may end up accumulating a lot of runs over the course of a season or tournament without losing many wickets. As a result, because of the stat's very basic math, they end up with an overly inflated Batting Average that's not truly representative of their skills.)

For limited overs games -- especially T20 matches like those played in Major League Cricket, Minor League Cricket, and the upcoming World Cup to be played here in June -- a different metric is used to see not only who can put up big numbers, but who can put them up in the shortest amount of time. Strike Rate measures how many runs per 100 balls a player accumulates -- total runs divided by total balls faced multiplied by 100.

Putting up runs quickly is the key to success in shorter formats of the game. In Test cricket, wickets are more valuable than balls because you can bat for days. In shorter formats of the game, balls are more valuable than wickets because you only get a limited number of them. And in T20, that number is the most limited. Every ball is important when your team only gets a crack at 120 of them.

So, what's a good T20 Strike Rate? Let's look at some numbers. The typical T20 score is around 180 for 120 balls (and it might be slightly higher or lower depending on the league and where the match is being played). That averages out to 1.5 runs per ball. If a team can average more than 1.5 per ball, they'll score higher than 180. To do this, teams need some run scorers with Strike Rates above 150. The best in the T20 game consistently have strike rates in the 150s or above. And for the game's greats, the sky is the limit. Among players batting in at least ten innings in last year's Indian Premier League, Australian Glenn Maxwell led all batters with a 183.48 Strike Rate. On this side of the planet, the Seattle Orca's Heinrich Klassen topped Major League Cricket with a 197.47 SR and the Dallas Mustang's Corey Anderson led all regular batters in Minor League Cricket with a 187.06 rate.

All stats are not created equal. And when it comes to cricket, not all stats carry the same weight. Depending on what format of the game is being played, some stats are more telling than others. If you're looking for the best batters in Test cricket, Runs and Batting Average are where you should be focusing. For limited overs matches, keep an eye on Runs, but your attention should be on Strike Rate.

(Thanks to Tom Dunmore at Major League Cricket for letting me tweak and repurpose a piece I had previously written for the league's site. And the cover image of Virat Kohli was done in like 15 seconds using AI. Wow, that stuff is scary!)