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

Updated July 2026.

Strike rate is runs per hundred balls. Average is runs per dismissal. Neither means much alone. Add balls per boundary, dot-ball percentage and the phase the player was batting in, and a scorecard starts telling you what actually happened rather than who scored most.

This 6 Club explainer takes the main T20 metrics one at a time, works through an illustration, and points out the sample-size traps that make most online statistics arguments worthless. It is educational only — there is no betting, no odds and no prediction here.

Strike rate is runs divided by balls, times one hundred. A batter who makes 45 from 30 deliveries has struck at 150. That is it — it measures how fast runs arrived, and nothing else.

What it hides is everything about risk and duration. A batter who makes 16 from 6 balls has a strike rate of 266 and has contributed considerably less than someone who made 60 from 45 at 133. Strike rate rewards short violent innings disproportionately, which is why quoting it without balls faced is the single most common statistical mistake in cricket conversation.

Average is runs divided by dismissals. In Test cricket it is close to a complete summary of a batter's value because occupation is itself worth something. In Twenty20, where an innings is capped at 120 balls and wickets in hand are frequently worth less than tempo, a high average can be evidence of a problem rather than a virtue.

A T20 opener averaging in the forties at a strike rate of 110 may be consuming deliveries that a faster scorer would have converted. Averages also flatter batters who are not out often, which is why finishers frequently post inflated numbers that overstate their contribution.

The numbers below are invented purely to demonstrate the arithmetic — they are not real players and not real matches.

Same runs, very different innings. A struck the ball far harder but left eleven deliveries unscored, meaning long dry spells that pushed pressure onto the other end. B rarely cleared the field but almost always scored, keeping the rate ticking and the partner comfortable. Which is better depends entirely on the situation — and that is the point. No single column answers the question.

Divide balls faced by fours and sixes hit. It isolates hitting frequency from running, and it is the fastest way to see how a strike rate was constructed. Two players at 140 can be completely different cricketers: one clearing the rope every four balls with dots in between, the other never hitting a boundary but converting almost everything into a single or two.

In practice, teams want both types. A batting order made entirely of boundary hitters collapses on a slow surface; one made entirely of runners cannot chase 200.

Dot percentage is the share of deliveries from which no run was scored. It matters because pressure in a short format is cumulative — three consecutive dots raise the required rate enough to force a risk two balls later, and that risk is where wickets come from. A batter can post a respectable strike rate while leaving a trail of dots that made the innings harder for everyone else.

When you are trying to work out why a chase that looked comfortable fell apart, the dot column usually explains it better than the wickets column.

Overs 1 to 6 have two fielders outside the circle. Overs 7 to 15 have five. Overs 16 to 20 have five and a rising required rate. These are three different games, and a season-long aggregate blends them into a number that describes nobody.

• Powerplay: judge on scoring rate and boundary frequency; accept the dismissals.
• Middle overs: judge on dot percentage and strike rotation against spin.
• Death: judge on runs per ball under a genuine required rate, not on aggregate.

This is exactly why comparing players across roles is meaningless without splitting the data — a theme we return to in our look at India's young T20 batting core.

Economy is runs conceded per over; a bowler's strike rate is balls per wicket. As with batting, phase is decisive. Conceding eight an over at the death is a good night; conceding eight in the powerplay is not. A bowler who takes wickets but goes at ten is valuable in a defence of 200 and a liability in a defence of 150.

Comparing a death specialist's season economy to a new-ball spinner's without adjusting for phase is the bowling equivalent of ranking a powerplay aggressor against a finisher on average alone.

The uncomfortable truth is that T20 numbers stabilise slowly. One innings tells you essentially nothing. Ten innings can be dominated by a single hundred or a pair of ducks. Even a full season is a modest sample once you split it by phase and condition. This is why a spectacular debut season is such a poor predictor of a career, and why the honest response to a small sample is patience rather than a verdict.

Our profile of Vaibhav Suryavanshi is a case study in exactly this: extraordinary numbers, tiny sample, and every reason to wait before drawing conclusions.

Use ball-by-ball scorecards from ESPNcricinfo, which lets you see the actual construction of an innings rather than the summary. Official squad and fixture information comes from the BCCI. Statistics graphics circulating on social media are frequently mislabelled, cherry-picked by date range, or simply wrong.

Understanding numbers better does not let you forecast a match. Cricket has too many variables — surface, dew, toss, injury, one dropped catch — and no model, tipster or paid group can beat that. Anyone selling certainty is selling a story. 6 Club is not a sportsbook, publishes no odds and makes no predictions; our games are chance-based entertainment, as our cricket and prediction games guide explains.

6 Club is an online gaming and entertainment platform for adults aged 18 and over. Games are decided by chance, they are not a source of income, and no amount of analysis changes a random outcome. Set limits before you play and stop when you reach them. See our responsible gaming page.

Common questions about reading T20 statistics properly.

Strike rate is runs scored divided by balls faced, multiplied by one hundred. A batter who makes 45 from 30 balls has a strike rate of 150, meaning 150 runs per 100 balls. It measures speed of scoring only and says nothing about how often the batter gets out.

Neither works alone. Strike rate without volume rewards a batter who slogs eight balls and departs; average without strike rate rewards someone who blocks. The useful reading combines them with the phase the batter was in and the situation of the match.

Balls faced divided by the number of fours and sixes hit. It shows how frequently a batter clears the field rather than how fast they accumulate overall, and it is useful for spotting a player whose strike rate is built on running rather than hitting, or the reverse.

Because pressure in T20 comes from consecutive dots more than from wickets. A batter with a respectable strike rate but a high dot percentage is likely scoring in bursts and pushing the required rate up in between, which forces the next batter into a harder job.

Economy is runs conceded per over, and what counts as good depends entirely on the phase bowled. A death-overs specialist and a powerplay spinner face completely different tasks, so comparing their season economy without splitting by phase is misleading.

More than most arguments assume. Single innings tell you almost nothing, and even ten or fifteen innings can be swung heavily by one big score or one duck. Look for a body of work across conditions and oppositions before treating a number as a characteristic rather than a phase.

Read a T20 scorecard in columns, not in headlines: runs and balls together, boundaries and dots together, and always with the phase in mind. Do that and most confident statistical claims you see online fall apart within seconds. For more cricket reading try our India vs Zimbabwe T20 guide, or browse the 6 Club homepage. Play responsibly, 18+.