T20 Stats Explained: Strike Rate, Average & Impact

Quick answer

Strike rate is runs per 100 balls faced — the most important batting number in T20 because an innings is only 120 balls long. Batting average is runs per dismissal, which matters less in T20 than in longer formats but still tells you about reliability within a role. Economy is runs conceded per over, usually the key bowling number. And impact is any attempt to weight those raw figures by match situation. None of them predicts anything — they describe what already happened.

Strike rate: what it really measures

Batting strike rate is simple arithmetic: runs ÷ balls faced × 100. A batter who makes 45 from 30 balls has a strike rate of 150. The figure answers one question and one question only — how quickly did this batter convert deliveries into runs?

In T20 that question is central, because the scarce resource is not wickets, it is balls. A team has ten wickets but only 120 deliveries, and in most T20 innings the side is not bowled out. Runs left unscored because of slow batting cannot be recovered at the end. That is why a strike rate below the team’s required rate is a genuine problem even if the batter is not getting out.

The limitation is equally important. Strike rate has no memory of how many balls were faced. A batter who hits 12 from 4 balls has a strike rate of 300, which sounds extraordinary and means very little. Always read strike rate next to balls faced.

Batting average in a format that ignores it

Batting average is runs ÷ dismissals. In Test cricket it is close to a complete summary of a batter, because occupying the crease is itself valuable. In T20 it is a supporting number rather than the headline.

The reason is that not getting out has limited value if it is achieved by scoring slowly. A batter averaging 40 at a strike rate of 110 may be actively costing their side runs compared with a batter averaging 25 at a strike rate of 160. Average also punishes finishers structurally: a player who walks in at the seventeenth over and is asked to hit from ball one will be dismissed often, and that is the job working correctly, not failing.

Why the two must be read together

Neither number stands alone. The useful view is the combination, interpreted through the player’s role.

This is also why comparing players across roles produces nonsense. A finisher and an opener should be compared with other finishers and other openers respectively. Our guide to India’s young T20 core sets out what each role is actually being asked to do.

Sample size: the mistake everyone makes

More cricket arguments are ruined by sample size than by anything else. A batting average after four innings is not a description of a player; it is a description of four afternoons. One large score can move an early-career average by twenty runs, and one duck can move it back.

A rough rule that serves most viewers well: treat anything under about ten innings as an anecdote, ten to thirty as a suggestion, and beyond that as evidence — while still checking what competition those innings came in. Runs in age-group cricket, domestic T20 and international cricket are not interchangeable, a point we make in our guide to reading a young player’s stats.

Bowling numbers: economy and strike rate

Bowlers have their own pair of numbers, and they trade off in a similar way.

• Economy rate — runs conceded per over. In T20 this is usually the headline, because four tight overs can decide a match.
• Bowling strike rate — balls per wicket. This matters most when a side needs breakthroughs rather than containment.
• Bowling average — runs per wicket. A blend of the two, less used in T20 analysis.
• Dot-ball percentage — often more revealing than economy, because pressure in T20 is built by consecutive dots.
• Phase splits — a bowler’s powerplay economy and death-overs economy can be completely different numbers.

That last point is the one commentators rely on most. A bowler with a mediocre overall economy may be excellent in the powerplay and poor at the death, and knowing which is which explains most captaincy decisions you see.

How to read a T20 scorecard properly

A scorecard read in the right order takes thirty seconds and tells you the story of the match. Try this sequence:

1. The result and margin first — runs or wickets, and how many balls were left.
2. The powerplay score — how the innings started usually explains everything that followed.
3. Top scorer with balls faced — not just the runs. 60 from 30 and 60 from 50 are different innings.
4. The middle-overs run rate — where most T20 matches are quietly won or lost.
5. The best and worst bowling figures — and which phase those overs came in.
6. Extras — a surprisingly large factor in close finishes.

Verified scorecards for essentially every match are on ESPNcricinfo, and official Indian fixtures and squads come from the BCCI.

Impact: the stat that is hardest to count

Everyone watching cricket knows that not all runs are equal. Twenty runs against the best bowler when the required rate is rising is worth more than twenty against the fifth bowler in a comfortable chase. “Impact” measures try to capture that by weighting runs and wickets according to the situation in which they occurred.

They are genuinely useful, but they should be read with a caveat: every impact model contains judgement calls about how much a situation is worth, and different models produce different answers about the same innings. Treat an impact figure as one informed opinion expressed numerically, not as a fact in the way that “45 from 30 balls” is a fact.

Reading an innings by phase

T20 innings split naturally into three phases, and almost every statistic behaves differently in each.

Once you read a scorecard in phases, players start making more sense. A finisher’s numbers should be judged in the death column, not the overall one. A spinner’s economy belongs in the middle overs. The apparent contradictions in raw career figures usually dissolve when you split them this way.

Statistics, chance and the gambler’s fallacy

This is where a statistics guide has to be honest about its own limits. Numbers describe the past. They do not determine the future, and in games of pure chance they do not even hint at it.

The classic error is the gambler’s fallacy — the belief that an outcome is “due” because it has not occurred recently. In a game of chance, each round is independent: a colour that has not appeared for ten rounds is exactly as likely on the eleventh as it was on the first. No record of past results, no pattern, and no lucky number changes that. We make the same point in our lucky number and rashifal guide, and in cricket fans and prediction games.

Cricket is not pure chance — skill matters enormously — but it is uncertain enough that no statistic forecasts a result. If you ever see confident numerical “predictions” being sold, the thing being sold is confidence. The problem gambling overview describes where that kind of certainty-seeking can lead.

Between overs

If you enjoy the numbers side of cricket, you probably also enjoy the rhythm of the match itself — and the gaps in it. Jai Club runs one-minute rounds that some readers use during innings breaks. They are separate games of chance with no connection to the match, no statistical relationship to any player, and no prediction involved.

Our match-day quick games guide explains how to keep that in proportion, the how to play Wingo page covers the format, and the free play-money demo lets you see it with nothing at stake.

Play responsibly (18+)

Understanding statistics is a good way to enjoy cricket more. It is not a way to beat a game of chance, and no page on this site suggests otherwise. If you play anything, set a budget in INR first — our budget basics guide shows how — never chase a loss, and stop while it is still fun. You must be 18+. See the responsible gaming guide or return to the Jai Club homepage.