T20 Stats Explained: Strike Rate, Average & Impact

Strike Rate: Speed, and Only Speed

Strike rate is runs divided by balls faced, times one hundred. Forty from thirty balls is about 133. It is the single most quoted T20 number and the most frequently misused, because it deliberately ignores dismissals.

Where it genuinely matters is context. A strike rate of 150 in the powerplay, with the field up and the ball hard, is a different achievement from 150 in the nineteenth over against a bowler defending a boundary-heavy field. Same figure, different skill. Always ask when before you ask how fast.

Average: Survival, With a Catch

Average is runs divided by dismissals — not by innings. Not-outs are removed from the denominator entirely, which is a reasonable convention in Test cricket and a distorting one in T20, where a finisher may be unbeaten in a large share of his innings.

The practical consequence: a lower-order finisher can carry a flattering average built from a run of twelve-not-out cameos, while a top-order batter who faces the new ball every match and occasionally fails looks worse on paper for doing a harder job. Batting position is not a footnote to an average; it is part of the number's meaning.

Reading the Two Together

• High average, low strike rate. Reliable but potentially costly — in T20 a batter who survives while consuming deliveries somebody else would use better is not automatically an asset.
• High strike rate, low average. Explosive and volatile. Can be exactly right for an impact role and completely wrong for a top-order anchor.
• Both high. Rare, and usually the profile of a genuinely elite T20 batter.
• Both low. Almost always a sample-size story or a player out of position rather than a verdict on ability.

Which profile a side needs depends entirely on the slot being filled — the four T20 batting jobs are set out in our India young T20 batting core guide.

Bowling: Economy Usually Beats Average

For bowlers, the equivalent trap is quoting a bowling average — runs conceded per wicket — as though it were the headline number. In a twenty-over game it usually is not. Economy rate, runs conceded per over, tends to tell you far more, because restricting scoring creates the pressure that produces wickets at the other end.

A bowler who goes for very few runs in the death overs and takes one wicket may have shaped the result more than a bowler with three cheap wickets against a collapsing tail. Strike rate for bowlers — balls per wicket — is a useful third number, particularly for a powerplay specialist whose job is early breakthroughs.

Two Underrated Numbers

Beyond the headline stats, two figures do a lot of quiet work:

• Balls per boundary. How often a batter finds the rope. It separates genuine boundary hitters from batters whose strike rate is built on running, which matters enormously once the field goes back.
• Dot-ball percentage. On both sides of the ball. A batter with a high dot rate is transferring pressure to his partner; a bowler with a high dot rate is building it.

Neither appears in a television graphic, and both are available on the full scorecards at ESPNcricinfo, which is where you should go when a number matters.

Phase Splits: The Same Number, Different Players

A T20 innings splits into three natural phases — the powerplay, the middle overs when spin usually operates and the field is spread, and the death. Splitting any record by phase is the fastest way to understand a player, because the same overall strike rate can describe two completely different cricketers.

The reason these phases exist at all comes down to fielding restrictions, which are set out in the general background on Twenty20 International cricket. Once you see an innings as three problems rather than one, the tactics make far more sense.

The Sample-Size Trap

This is the one that decides most online arguments before they start. Over a handful of innings, a single unbeaten fifty can move an average by a huge margin, and one enormous over can lift a strike rate past players with years of consistency behind them.

Small samples are descriptive, not predictive. They tell you what happened; they do not tell you what happens next. This applies with particular force to very young players, which is why our Vaibhav Suryavanshi explainer treats every circulating figure as reported rather than settled.

Statistics Do Not Predict Matches

Worth stating plainly, because plenty of sites imply otherwise. Numbers describe tendencies. They do not account for the toss, the surface, dew, an injury in the warm-up or the ordinary randomness of a sport decided by inches. Dhani Game does not publish match predictions, tips or odds, and is not a sportsbook. Anyone offering a "guaranteed" call from a statistical model is selling confidence, not information.

A Different Kind of Number

One honest comparison to finish on. A cricket statistic reflects skill exercised over time. A game of chance does not — the result of a Dhani Game Wingo demo round is random every single time, and no previous sequence changes the next one. That is exactly why past results in a chance game carry no predictive value at all, a point our match-day instant games guide and cricket fever instant games guide both make explicitly.

FAQ