T20 Stats Explained: Strike Rate, Average & Impact

The formulas, first

Four calculations cover ninety per cent of what you will ever need:

• Batting strike rate = runs ÷ balls faced × 100
• Batting average = runs ÷ number of times dismissed
• Bowling economy = runs conceded ÷ overs bowled
• Bowling strike rate = balls bowled ÷ wickets taken

Note the trap built into the vocabulary: “strike rate” means opposite things for batters and bowlers, and for batters a high number is good while for bowlers a low number is good. That single ambiguity causes more confused arguments than any other term in cricket.

Strike rate: what it really measures

A batting strike rate answers exactly one question: how fast did this player convert deliveries into runs? It says nothing about how difficult the bowling was, what the pitch was doing, whether the innings was a rescue job or a free-hit finish, or whether the runs mattered.

Consider two innings of 45. One comes off 30 balls in the powerplay against a new ball on a flat surface; the other comes off 30 balls in the middle overs against high-quality spin on a slow deck. Identical strike rates, wildly different achievements. This is why the phrase “he has a strike rate of 140” is the beginning of an analysis, not the end of one.

Sample size compounds it. Over three or four innings a single explosive knock can lift a strike rate by twenty points and keep it there for a season — which is exactly the caution we apply to the reported numbers in our Vaibhav Suryavanshi records and stats profile.

Batting average in a format that ignores it

Batting average was designed for a format where survival is the point. In Test cricket, occupying the crease has intrinsic value. In a twenty-over innings, the team has exactly 120 deliveries and usually finishes with wickets in hand — so the binding constraint is balls, not wickets.

That inversion changes everything. A batter averaging 40 at a strike rate of 110 is consuming deliveries that a faster scorer could have converted more efficiently. A batter averaging 22 at a strike rate of 165 may generate more team runs despite looking worse on the traditional metric. Neither is automatically right — it depends on the role. But you cannot evaluate a T20 batter on average alone without producing nonsense.

The practical fix is simple: never quote one without the other. “28 at 148” is a description of a player. “28” is a description of nothing.

Boundary percentage and dot-ball percentage

These two are the most underrated numbers on a scorecard, and together they explain almost every batter’s style.

• Boundary percentage — the share of runs from fours and sixes. Very high means power-dependent: devastating when it lands, cheap when it does not. Lower, with a healthy strike rate, means the player is rotating strike well — a rarer and more reliable skill.
• Dot-ball percentage — how often the batter fails to score. Dots do not just cost runs; they transfer pressure to the next delivery and the one after. A batter with a decent strike rate but a very high dot percentage is scoring in violent bursts, which is harder for a team to plan around.

The same pair works in reverse for bowlers. A bowler with a high dot percentage is controlling the game whether or not the wickets column agrees, and in a short sample control is far more predictive than wickets.

Phase splits: the stat that changes your mind

A T20 innings is three distinct games stitched together, and splitting any statistic by phase is the single most illuminating thing you can do with a scorecard:

• Powerplay (overs 1–6) — fielding restrictions, hard new ball, highest risk and highest reward. Strike rates are inflated and dismissals are frequent.
• Middle overs (7–15) — spread fields, spin, the phase where matches are quietly won and lost. Scoring here is genuinely difficult, and a good middle-overs strike rate is worth far more than the same number in the powerplay.
• Death overs (16–20) — maximum aggression, wide yorkers, scrambled fields. Strike rates look absurd and averages collapse. Both are artefacts of the phase.

Once you view players through their phases, the role-based way of thinking in our young T20 core guide makes immediate sense: a finisher and an opener are not doing the same job badly or well, they are doing different jobs.

Economy, strike rate and the bowler’s side

For bowlers, economy rate is king in T20 — runs conceded per over — because containing is usually more valuable than taking a wicket in a format where the batting side has wickets to spare. Bowling strike rate (balls per wicket) matters more in the powerplay and at the death, where a wicket genuinely breaks momentum.

Averages for bowlers are the least useful of the three in T20, for the same reason batting averages are: they answer a question the format is not asking. Watch economy in the middle overs and dot percentage everywhere, and you will read a bowling performance far more accurately than the wickets column allows.

Impact: the honest limits

“Impact” ratings attempt to fold all of the above into one number by weighting each contribution by the match situation — runs when a chase was tight are worth more than runs in a dead over. They are genuinely useful, and they are also opinions.

Every impact model contains human choices: how much to weight the death overs, how to value a dot ball against a wicket, how to adjust for opposition quality. Change the weights and the rankings change. So read an impact score the way you would read a film review — informed, worth considering, not a measurement. The raw components on ESPNcricinfo are the auditable part.

Six ways cricket stats mislead

• Small samples. Three innings is an anecdote, not a career.
• Ignoring role. Comparing a finisher’s average to an opener’s is meaningless.
• Ignoring conditions. A 160 strike rate on a flat deck is not a 160 on a turner.
• Format blending. First-class averages and T20 strike rates describe different sports.
• Survivorship. Not-outs inflate averages, particularly for lower-order finishers.
• Selective endpoints. “Since March” usually means the window that flatters the argument.

Recognising these six is roughly the whole skill. It will also inoculate you against the genre of social-media “stat card” that pairs a cherry-picked number with a confident claim about what happens next — the presentational style favoured by tipping accounts, which is a good reason to distrust it.

Read one scorecard properly

1. Open a completed match scorecard on ESPNcricinfo.
2. For each top scorer, write down runs, balls, and calculate the strike rate yourself.
3. Note which phase each innings occurred in. Was it a powerplay burst or a middle-overs grind?
4. Count boundaries and work out roughly what share of the runs they represent.
5. Do the same for the two most economical bowlers, and count their dot balls.
6. Now compare your reading with the match report. You will usually find you noticed something it did not.

Ten minutes of that will do more for your understanding of the game than a season of highlights packages. Background on how the format evolved is on the T20 International entry, and for a worked example of following a live series through official channels see our India vs Zimbabwe T20 2026 guide.

One last thing worth stating plainly: understanding statistics better does not let you predict a match. Cricket is a chaotic system with a small number of high-leverage moments, and no model — public or paid — reliably forecasts it. We publish no odds, no tips and no predictions, for exactly that reason. If you want something quick during the innings break, the card tables on Teen Patti Stars are just card games of chance — Dragon Tiger and Andar Bahar settle in seconds, played on a budget you set, entirely unrelated to the cricket. Our match-day guide covers that properly.

Summary: strike rate is speed, average is survival, and T20 cares far more about the first than the second. Split everything by phase, read boundary and dot percentages together, treat impact ratings as opinions, and always check the raw figures on ESPNcricinfo before you argue with anyone.