T20 Stats Explained: Strike Rate, Average & Impact

Quick answer: Strike rate is runs per 100 balls — it measures speed. Average is runs per dismissal — it measures survival. In T20 you need both together, plus the innings count, the phase of the innings and the match situation, before any number means anything at all.

Cricket statistics are having a strange moment. There have never been more numbers available, and there has never been more confident nonsense circulating built on top of them. A graphic appears, a strike rate is quoted without an innings count, two formats get compared, and a perfectly good argument is settled by a figure that does not support it. This guide fixes that with plain-English definitions and worked examples. It is the reference piece behind our Vaibhav Suryavanshi explainer and our look at India's young T20 core, both of which lean heavily on reading numbers honestly.

Strike rate: the speed number

Strike rate = (runs ÷ balls faced) × 100. It answers one question: how fast did this batter score? A batter making 45 from 30 balls has a strike rate of 150. One making 45 from 45 balls has 100. Same runs, very different innings.

What strike rate does not tell you is whether those runs helped. Consider two innings:

A and B have identical numbers and completely different value. C looks the worst on paper and may well have been the innings of the match. This is why context always comes before the figure.

Batting average: the survival number

Average = runs ÷ times out. In Test cricket this is close to the perfect measure, because occupying the crease is the job. In Twenty20, where an innings is capped at 120 balls, survival can be actively unhelpful. A batter who scores slowly and rarely gets out can post a fine average while costing his side matches.

Two quirks worth knowing. Not-outs inflate averages, and a finisher who is frequently unbeaten at the end of a chase will show an average that flatters him. And in T20 many analysts prefer runs per innings — total runs divided by innings played, regardless of dismissals — precisely because it removes that distortion.

Reading them together

Neither number works alone. Read as a pair, they describe a batter's type:

• High average, high strike rate. The rare complete T20 batter. Scores fast and lasts.
• Low average, very high strike rate. The impact hitter. Wins games in bursts, fails often. Judged on the games won, not the failures.
• High average, modest strike rate. The anchor. Valuable in collapses and on difficult pitches, a liability if used in the wrong phase.
• Low average, modest strike rate. Out of form or out of role — the numbers cannot tell you which.

Bowling numbers: economy, average, strike rate

Bowlers have their own three, and the T20 hierarchy is different from the Test one.

The phase matters enormously here too. A death-overs specialist and a powerplay bowler are doing different jobs against different fields, and comparing their economy rates without saying which overs they bowled is meaningless.

The stats that get misused most

• Cross-format comparisons. A first-class average and a T20 average are not on the same scale. Ever.
• Sample size omitted. "Strike rate 187" over four innings is a fact about four innings, not about a player.
• Age-group treated as senior. Under-19 runs are a signal, not an equivalent.
• Career figures used for current form. A career number smooths over exactly the recent stretch you were asking about.
• Stale screenshots. Statistics update every match. Graphics do not.
• Ignoring conditions. A strike rate of 130 on a slow, gripping surface may be a better innings than 160 on a flat one.

The remedy for all six is the same and takes thirty seconds: open the player's profile on ESPNcricinfo and read the figure in its own row, with its own innings count, in its own format. For official squad and fixture information, the BCCI site is the reference for Indian teams.

How to actually read a scorecard

A quick routine that turns a scorecard from a wall of digits into a story:

• Start with the fall of wickets. It tells you the shape of the innings — where the pressure came and who absorbed it.
• Look at balls faced before runs. The balls column is where the tempo lives.
• Check the extras. A large extras column often explains a close finish better than any individual performance.
• Read bowling figures with the phase in mind. Four overs at the death is a different task from four in the powerplay.
• Note the boundary count. Fours and sixes versus runs off other deliveries tells you how the total was built.

Statistics describe; they do not predict

This is the point everything above has been building to. Cricket statistics are a record of what happened. They are not a forecasting engine, and a past strike rate does not tell you what the next innings will be. Conditions, toss, match-ups, fitness, pressure and simple chance all intervene, in combinations nobody resolves reliably.

Which is why Jai Club publishes no match predictions, no odds and no tips — not as a matter of policy alone, but because the honest position is that no one can do it. Our piece on enjoying prediction games responsiblymakes the same argument from the fan's side.

Between the overs

If you fill innings breaks with something, Jai Club runs Wingo, a colour-prediction lottery that resolves a round in roughly a minute. It is a game of chance, its result has nothing to do with the match on screen, and it is not a bet on cricket. Our match-day games guide explains how to keep it small and contained, and the free Wingo demo lets you see the format without spending anything.

Set a limit first, keep it fixed, and never raise it to recover a loss — that instinct is a recognised warning sign of problem gambling. See our responsible gaming page. Adults 18 and over only.