T20 Stats Explained: Strike Rate, Average & Impact (Read a Scorecard Properly)

Strike rate is runs per 100 balls: divide the runs by the balls faced and multiply by 100. A batter who makes 40 from 25 balls has a strike rate of 160. It is the closest thing T20 has to a single headline number, because the format gives each side a fixed 120 balls and the scarce resource is deliveries rather than wickets.

That fixed-balls structure is what flips the priority relative to Test cricket. In a five-day match, wickets are the scarce resource and occupying the crease has value in itself. In T20, a batter who uses 30 balls for 25 runs has actively cost his side, no matter how respectable the score looks in isolation.

The trap is treating strike rate as context-free. A strike rate of 130 while chasing on a slow, turning surface can be a superb innings; the same figure on a flat deck in a high-scoring game can be a drag on the total. The number tells you the rate, not whether the rate was good.

Average is runs divided by the number of times the batter was dismissed — not innings played. Not-outs increase the average because those innings add runs without adding a dismissal, which is why finishers and lower-order batters often carry averages that flatter them.

Average has not become useless in T20; it has become secondary. It still tells you about reliability, which matters for a top-order batter expected to bat through. But used alone it will systematically favour slow accumulators and punish the aggressive players a T20 side is built on.

The sensible reading is to hold both numbers together. Average tells you how often the batter fails; strike rate tells you what the innings is worth when he does not. Neither answers the other's question.

Economy rate is runs conceded per over, and in T20 it is usually the first number people look at. It is also heavily determined by role: a bowler who bowls the nineteenth and twentieth overs will almost always have a worse economy than one bowling overs two and three, because the batters are attacking differently.

Bowling strike rate — balls bowled per wicket — measures how quickly a bowler takes wickets rather than how cheaply. The two can diverge sharply. A wrist spinner may take a wicket every fifteen balls while going at nine an over; a defensive seamer may concede six an over and rarely take one. Both can be doing the job they were picked for.

The useful habit is to ask what phase the bowler operated in before judging either number. Phase-split data is available on ESPNcricinfo, and it turns a misleading career economy into a genuinely informative one.

Broadcasters increasingly use impact-style metrics that try to weight a contribution by match situation — runs scored when the required rate was climbing, wickets taken at a moment the game turned, and so on. The intent is sound: a 30 from 15 in a tight chase is worth more than the same innings in a dead game.

The caution is that these metrics are proprietary and not standardised. Two broadcasters can produce different impact figures for the same innings because they weight the inputs differently, and none of them is a published, checkable statistic in the way an average is.

Treat them as a useful conversation-starter rather than evidence. If you want a number you can verify and reproduce, stick to the classical set — runs, balls, dismissals, overs, wickets — and split them by phase.

Most bad cricket arguments come from a short list of recurring errors. Recognising them will make you a considerably better reader of a scorecard than most people posting about one.

The first is comparing across formats. The second is judging a specialist by a generalist metric — a finisher by average, an opener by economy of dismissal. The third is ignoring sample size, especially with young players. The fourth is forgetting era inflation: a strike rate that was outstanding fifteen years ago is ordinary now. The fifth is treating a career figure as a current one, when form moves in seasons.

None of this makes statistics untrustworthy. It makes them precise instruments that need to be pointed at the right question — which is a very different thing.

This is the point at which cricket analysis and betting content part company. Statistics are a record of what has already happened. They can characterise a player's tendencies, but they do not tell you what will happen in the next match, and no amount of historical data closes that gap.

6 Club does not offer cricket betting, match odds or tipping, and nothing here is a prediction of any result. This is a fan guide, written for entertainment. Every stat is quoted as reported at the time of writing — check ESPNcricinfo for the current figure before you repeat it.

6 Club runs games of chance — colour prediction and Wingo — which have no relationship to any cricket result and make no claim to. They are entertainment for adults (18+), played within a budget you set in advance.