T20 Stats Explained: Strike Rate, Average & Impact

Quick answer: Strike rate is runs per 100 balls — it measures speed. Average is runs per dismissal — it measures survival. In T20 the scarce resource is balls, not wickets, so neither number means much alone. Read them together, with the phase the batter operates in and the number of innings behind the figure.

Cricket statistics have never been more visible or more misused. A clip goes viral, a caption attaches a number to it, and within an hour the number is being quoted as though it settles an argument. Most of the time it does not, because the figure has been detached from the context that made it meaningful. This Jai Club guide is a plain-English tour of the T20 batting metrics you will actually encounter, what each one measures, and the specific ways each can mislead you.

Strike Rate: Speed, and Nothing Else

Strike rate is runs divided by balls faced, times 100. A batter making 45 from 30 balls has a strike rate of 150. That is the whole calculation, and its simplicity is both its strength and its weakness. It tells you how fast someone scored. It tells you nothing about whether they lasted, when they batted, or what the situation demanded.

The classic trap is comparing strike rates across phases. A finisher arriving at the seventeenth over faces bowlers under pressure with the field spread and licence to swing at everything; an opener faces the new ball with fielding restrictions but also a hard, moving ball. A middle overs anchor may be batting on a collapsing scorecard where survival is worth more than tempo. Three very different jobs, three very different expected strike rates, and a raw comparison between them is close to meaningless.

Average: Survival, in a Format That Barely Rewards It

Batting average is runs scored divided by times out. In Test cricket that is close to the single most important number a batter has, because the binding constraint is wickets. In T20 the binding constraint is balls — there are only 120 of them — and a batter who protects their wicket by scoring slowly can lose a match while improving their own average.

Two more wrinkles. Not-outs inflate the average of finishers, because a batter who is unbeaten in a chase never has that innings counted as a dismissal. And a small number of very large scores can carry an average upward while the median innings stays modest. Average is worth reading; it is not worth reading first.

MetricWhat it measuresIts main blind spot
Strike rateScoring speed per 100 ballsIgnores dismissals and phase
AverageRuns per dismissalRewards slow accumulation; inflated by not-outs
Boundary %Share of runs or balls hit to the ropeUndervalues running between wickets
Balls per dismissalHow long a batter survivesSays nothing about tempo
Phase splitsWhere in the innings runs come fromNeeds a decent sample to stabilise

Boundary Percentage and Balls Per Dismissal

Boundary percentage answers a question the headline numbers skip: how is this batter scoring? Two players can both strike at 140, one by hitting a six every eight balls and rotating little else, the other by finding gaps and running hard. Those are different skills with different reliability — boundary hitting is more pitch- and ground-dependent, running is more repeatable but caps out lower.

Balls per dismissal is the quiet companion to strike rate. Speed with no survival produces a batter who dazzles occasionally and fails often. Survival with no speed produces a batter who is technically not out and practically a liability. Looking at the two together is most of what “impact” means before anyone builds a fancier model for it.

Reading a Scorecard in Order

  1. Check the sample size firstHow many innings sit behind the figure? Six innings is an anecdote; sixty starts to describe a method.
  2. Identify the role and batting positionOpener, anchor, spin-hitter or finisher — the expected numbers differ enormously by job.
  3. Read strike rate and balls per dismissal togetherSpeed without survival, or survival without speed, are both incomplete pictures.
  4. Split by phasePowerplay, middle overs and death produce different scoring conditions. Compare like with like.
  5. Look at boundary percentageIt tells you whether the runs come from power or from placement and running.
  6. Check the competition levelAge-group, domestic, franchise and international records are not interchangeable.
  7. Verify at the sourceConfirm any figure on ESPNcricinfo before repeating it — captions get numbers wrong constantly.

Where to verify: ball-by-ball records, phase filters and career summaries are maintained by ESPNcricinfo. For the format’s rules and history, the Twenty20 International reference is a reasonable starting point.

The Traps That Catch Most People

Four recur constantly. Cherry-picked splits: a statistic filtered until it flatters someone — “since 2024, in away matches, batting second” — is usually a sample of four innings wearing a suit. Level mixing:age-group numbers quoted next to international numbers as though the bowling were comparable. Recency: two big scores producing a permanent reputation. And outcome bias:judging a shot or a selection by whether it happened to work rather than whether it was the right call given the situation.

All four appear heavily around a young player having a breakout run, which is why our Vaibhav Suryavanshi guide and our young T20 batting core guide deliberately describe roles and shapes rather than freezing figures into the page.

Statistics describe, they do not predict. No metric forecasts an individual innings or a match result. Jai Club publishes no odds, tips or predictions, and our instant games are random-outcome entertainment unconnected to any real cricket — see our cricket prediction games guide.

Play responsibly. Game outcomes are random and never guaranteed. Set a budget before you play, treat it as entertainment rather than income, never chase losses, and take part only if you are 18 or older. See our responsible gaming page.

T20 Stats FAQ

How is batting strike rate calculated in T20?

Strike rate is runs scored divided by balls faced, multiplied by 100. 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 — it says nothing about how often the batter gets out, which is why it is never read alone.

What is a good T20 strike rate?

It depends entirely on the role and the phase. A finisher batting in the last three overs is expected to score far faster than an anchor rebuilding after early wickets, and both can be doing their job well. Comparing strike rates across different roles without adjusting for phase is the most common mistake in T20 analysis.

Why does batting average matter less in T20?

Average measures runs per dismissal, which suited formats where surviving was the main constraint. In T20 the constraint is balls, not wickets — a team has only 120 of them. A batter with a high average built on slow scoring can actively cost their side, so average is read alongside strike rate rather than above it.

What is boundary percentage?

It is the share of a batter’s runs that came in fours and sixes, or alternatively the share of balls faced that went to the boundary. It is useful because boundary hitting is the main engine of T20 scoring, and because it separates batters who accelerate through power from those who do it through running and placement.

What are phase splits?

A T20 innings is usually divided into the powerplay (overs 1–6), the middle (7–15) and the death (16–20). Splitting a batter’s record by phase shows where their runs actually come from. Two players with identical overall numbers can have completely different phase profiles and therefore completely different value to a side.

How big does a sample need to be before the numbers mean something?

There is no fixed threshold, but the smaller the sample the more you should treat a figure as a description of what happened rather than a prediction of what will happen. A strike rate over six innings is an anecdote; over sixty it starts to describe a method. Always check how many innings sit behind a number.

Do these stats let me predict a match or a player’s score?

No. Statistics describe what has already happened; they do not forecast individual innings, which are affected by pitch, opposition, match situation, weather and chance. Nobody can predict a cricket result, and Jai Club publishes no odds, tips or predictions of any kind.

Where should I look up cricket statistics?

ESPNcricinfo maintains ball-by-ball data and career records for professional cricket, including phase-based filters, and the BCCI publishes official squad and fixture information for Indian cricket. Between them you can check almost any claim you see shared on social media.