Explainer

What cricket analytics actually measures

Averages and strike rates are the start, not the finish. A plain-language tour of the numbers analysts use, what each one is good for, and where each one misleads.

The short version: every cricket statistic answers one narrow question. The skill is matching the question you care about to the number that actually answers it, and knowing what that number leaves out.

Two kinds of data

Scorecard data is what most people know: runs, balls, wickets, overs, the way each batter got out. It tells you what happened in a match.

Ball-by-ball data records every delivery: who bowled it, who faced it, how many runs came from it, and whether a wicket fell. It tells you when and against whom. That is what lets you split an innings into phases, or ask how a batter scores against a particular bowler. Free sources such as Cricsheet publish ball-by-ball data for many international and league matches.

Some professional providers add more: where the ball pitched, its speed, where the shot went. That is useful, but it is rarely available for Associate cricket, so this site mostly works with ball-by-ball data.

The basic measures

MeasureHow it's worked outWhat it answersWatch out for
Batting averageruns ÷ times outHow many runs a batter makes per dismissalNot-outs inflate it; says nothing about speed
Strike rate (batting)runs ÷ balls × 100How fast a batter scoresDepends heavily on when they bat
Economy rateruns conceded ÷ oversHow expensive a bowler isDeath-over bowlers will look worse
Bowling averageruns conceded ÷ wicketsRuns a bowler pays for each wicketUnstable with few wickets
Bowling strike rateballs ÷ wicketsHow often a bowler takes a wicketSame: needs a decent number of wickets
Dot-ball %balls with no run ÷ ballsPressure built (bowler) or absorbed (batter)Whether wides and no-balls are counted varies
Boundary %balls hit for 4 or 6 ÷ balls facedHow a batter's runs are madeGround size matters

None of these is wrong. Each is a summary, and a summary always throws something away. A batter averaging 35 at a strike rate of 95 and one averaging 25 at 150 can both be valuable in T20 cricket; the average alone would rank them one way and the strike rate the other.

Context: the phase of the innings

In T20 cricket, the same over is played very differently depending on when it comes. Analysts usually split the innings into three phases.

The three phases of a T20 innings A bar of 20 overs split into powerplay (overs 1 to 6), middle overs (7 to 15) and death overs (16 to 20). Powerplay · 1–6 Middle overs · 7–15 Death · 16–20 2 fielders outside the circle rotate, build, use spin boundaries, yorkers, slower balls Over 1 Over 20
A common way to split a T20 innings. The powerplay is set by the playing conditions; the 7–15 / 16–20 split is an analyst's convention, and some analysts draw the line elsewhere.

Once you split by phase, many puzzles go away. A bowler with a high economy rate may simply bowl most of his overs at the death, where every bowler concedes more. A batter with a modest strike rate may bat through the middle overs and give the finishers a platform. Comparing players within the same phase is fairer than comparing their overall numbers.

Context: the matchup

A matchup is a pairing: a type of batter against a type of bowler. Classic questions are how left-handers fare against off-spin, which turns the ball away from them, or how a top order copes with left-arm pace.

To answer them you need to know, for every ball, the batter's hand and the bowler's style. Ball-by-ball data usually does not carry that. That gap is why we built a player profile register on top of Cricsheet.

Caution

Matchup samples shrink fast. A batter may face only a few dozen balls of left-arm spin in an entire international career. Treat a single player's matchup numbers as a hint, and team- or competition-level matchups as more reliable.

Context: the opposition and the conditions

Runs against a top-ranked side and runs against a team playing its first international season are not worth the same. Neither are runs on a small ground with a fast outfield and runs on a slow, low pitch. Good analysis either adjusts for this or at least says it out loud.

This matters even more in Associate cricket, where the gap between the strongest and weakest teams in a tournament can be very wide. We look at that in Five innings is not a career.

From numbers to decisions

For a coach or a captain, the value of analysis is in a few clear, usable observations: this batter scores most of his runs square of the wicket, this bowler's slower ball goes for runs, this opponent loses wickets in clusters in the middle overs. More data is rarely the problem. Choosing what matters is.

That is the approach on this site: start with the question, pick the measure that answers it, show the evidence, and be honest about how much the evidence can bear.