T20 Stats Explained: Strike Rate, Average & Impact

Almost every cricket argument on the internet is really an argument about a statistic somebody has misread. Strike rate gets quoted without balls faced, averages get compared across incompatible roles, and “impact” gets treated as though it were an official record. This Jai Club explainer goes through the numbers on a T20 scorecard one at a time: what each one measures, what it cannot see, and how to read a scorecard so it tells you the truth.

Plain-English stats No tips or odds Read the scorecard

Strike Rate: Runs per Hundred Balls

Batting strike rate is runs divided by balls faced, times 100. A batter who makes 45 from 30 has a strike rate of 150 — a shorthand for “at this speed, 100 balls would produce 150 runs”. In a format where each side gets exactly 120 balls, speed is the currency, which is why strike rate has displaced average as the headline batting number in T20 commentary.

The trap is that strike rate is entirely blind to dismissal. A batter who swings at everything and is out for 12 from 6 balls posts a strike rate of 200; a batter who makes 60 from 40 posts 150. The first number is bigger and the second innings is worth vastly more. Strike rate also becomes wildly unstable over small samples: a single 30-ball hundred can lift a whole season’s figure by twenty points or more. Always read the balls-faced column next to it.

Batting Average: Runs per Dismissal

Average is runs divided by the number of times the batter has been out — not by innings played. Not-outs are removed from the divisor entirely. That single rule explains most of the strange averages in T20: a finisher who bats at seven and is unbeaten in half his innings can show a very high average off a small pile of runs, because the denominator barely moves.

Average tells you how reliably a batter avoids getting out. In Test cricket that is close to the whole game. In T20 it is one input among several, because a wicket is only twenty balls of a resource you may not even use. A middle-order batter averaging 45 at a strike rate of 110 is often actively hurting his side; the same figures in a different format would be excellent. Context is everything.

Balls Faced: The Number Nobody Quotes

Balls faced is the most under-used column on a scorecard. It is what turns two rates into a real story: it tells you how much of the team’s 120-ball resource this batter consumed, and it is the sanity check on every rate you are about to quote. Sixty from 34 and sixty from 55 are completely different innings, and only one of them helped.

It is also the fastest way to spot a misleading career figure. If someone shows you a spectacular strike rate, the follow-up question is always the same: over how many balls? A rate built on 90 deliveries is a rumour, not a record.

Boundary Percentage and Dot-Ball Percentage

Boundary percentage — the share of balls a batter hits for four or six — is one of the more honest T20 metrics, because in a format this short most of the gap between innings comes from boundaries rather than running. It is harder to distort with a couple of not-outs than an average is, and it correlates well with the thing teams actually want from a top-order batter.

Its mirror image is dot-ball percentage. Dots are the hidden cost of an innings: a batter who scores at a healthy rate but leaves a trail of dots forces someone else to take a risk later. When a commentator says a batter “never really got going”, the dot-ball column is usually what they are describing without naming it.

Bowling: Economy, Strike Rate and Phase

On the bowling side, economy is runs conceded per over and bowling strike rate is balls per wicket. Both need phase context to mean anything. An economy of eight is poor in the powerplay and often very good at the death, because the two phases are entirely different jobs against entirely different fields. Comparing two bowlers’ overall economy without knowing when each of them bowled is one of the most common mistakes in cricket analysis, and it is the bowling equivalent of comparing an opener to a finisher on average.

The corresponding batting distinction — powerplay attacker, middle-order accumulator, death-overs finisher — is set out in our guide to India’s young T20 batting core. Roles first, numbers second: that ordering fixes most bad arguments.

“Impact”: Useful Idea, Unofficial Number

Impact metrics try to weight runs by when and under what pressure they were scored, on the reasonable premise that twenty from eight at the death can be worth more than forty from forty in the middle overs. The idea is sound. The problem is that there is no standard: every broadcaster, site and analyst runs a different model with different weightings, so two impact scores for the same innings can flatly disagree.

Treat impact as one analyst’s opinion expressed in decimals. Unlike runs, balls and wickets — which are recorded facts kept by ESPNcricinfo in the ball-by-ball record — an impact rating is a construction. Ask what the model rewards before you accept its verdict.

Mind the Format Boundary

A surprising share of statistical arguments online are people quoting numbers from different competitions at each other. Franchise T20, domestic T20 and Twenty20 International cricket are separate records with different standards of opposition and different conditions. Aggregating them produces a number that describes nothing in particular. Check the format tab before you compare.

A Five-Step Way to Read Any T20 Scorecard

1. Runs and balls first — the two raw facts everything else is derived from.
2. Then the phase — which overs did this innings actually cover?
3. Then the match situation — chasing or setting, wickets in hand, required rate.
4. Then the rates — strike rate and average, read against the role.
5. Then the opposition and surface — a slow, low pitch changes what a good score is.

Do this a few times and the headline numbers stop being persuasive on their own, which is exactly the point. It is the same discipline we apply to the records in our profile of Vaibhav Suryavanshi — read the figure, then read what is behind it.

Understanding Stats Is Not Predicting Matches

This needs saying clearly, because the two get deliberately conflated by people selling tips. Statistics describe what has already happened. They do not forecast what will. A batter averaging 50 can be bowled first ball by a good delivery; a bowler with a superb economy record can be hit for 22 in an over. Cricket is a small-sample game full of single events, which is exactly why it is worth watching and exactly why it cannot be predicted.

We publish no odds, no tips and no predictions anywhere on this site. If you enjoy fan prediction games as a social thing, our note on cricket fans and prediction games, responsibly explains where the honest line sits, and our India vs Zimbabwe T20 fan guide takes the same approach to a series.