T20 Stats Explained: Strike Rate, Average & Reading a Scorecard

Batting strike rate

Strike rate is runs scored per 100 balls faced: (runs ÷ balls) × 100. Score 30 from 20 balls and your strike rate is 150. It answers one question only — how quickly did this batter convert deliveries into runs.

In the shortest format that question is close to the most important one, because balls are the scarce resource. A team gets 120 of them and no more, so a batter consuming deliveries without scoring is spending a shared budget. This is the core insight that reshaped how Twenty20 International cricket is played and selected for.

The catch: strike rate is wildly unstable over short innings. Twelve from four balls is a strike rate of 300 and tells you essentially nothing. Always read it next to balls faced.

Batting average

Batting average is runs divided by the number of times dismissed — not by innings played. Not-outs are excluded from the denominator, which is why finishers who are frequently unbeaten can carry averages that look inflated relative to their apparent contribution.

Average measures survival: how long a batter typically lasts. In Test cricket that is the central question. In T20 it is a supporting one, because occupying the crease has no value unless runs come with it. A batter averaging 40 at a strike rate of 110 may be actively costing his side matches.

Why you need both numbers, always

Read the two together and a scorecard starts making sense. Read one alone and you will find yourself defending or attacking players for reasons that have nothing to do with what they were asked to do — a point our young T20 core guide works through role by role.

Bowling economy and bowling strike rate

Bowling has its own trio, and the names overlap confusingly with the batting ones:

• Economy rate — runs conceded per over. The headline T20 bowling number, because containment wins matches in a format with only 20 overs.
• Bowling strike rate — balls bowled per wicket taken. Lower is better. Note this is the opposite direction from batting strike rate.
• Bowling average — runs conceded per wicket. Combines the other two into one figure, which makes it convenient and slightly blunt.

As with batting, phase matters enormously. An economy of eight in the death overs is excellent; the same economy in the middle overs is poor. Comparing bowlers without asking when they bowled is the single most common error in bowling analysis.

Phases change the meaning of every number

A T20 innings is three different games stitched together, and each has its own scale:

• Powerplay (overs 1–6). Only two fielders outside the circle. Scoring is easier, risk is higher, and wickets cost more than runs.
• Middle (overs 7–15). The field spreads and spin usually arrives. Strike rates dip across the board, so a strike rate of 130 here is not the same as 130 in the powerplay.
• Death (overs 16–20). Maximum risk on both sides. Batting averages collapse, economy rates balloon, and impact stops resembling any season-long average.

Reading a single scorecard line properly

A line such as 44 (23), 4 fours, 2 sixes looks simple. Get the full picture by asking four questions in order:

1. How many balls? 23 balls is a real innings; 6 balls is a cameo. This governs how much weight anything else deserves.
2. When did he bat? Powerplay, middle or death changes the difficulty of every run.
3. What was the situation? Chasing 210 with wickets down is a different task from setting a total at 40 for none.
4. What were the conditions? Ground size, pitch and dew make some 44s worth far more than others.

Four traps that fool almost everyone

• The small sample. Three innings is not a trend. One century can move a career average by twenty runs. Wait for dozens of innings before concluding anything.
• The not-out inflation. Finishers accumulate not-outs, which flatters average while saying nothing about how well they finished.
• The context-free comparison. Comparing a powerplay opener with a death-overs finisher on average alone compares two unrelated jobs.
• The era effect. Scoring rates have risen sharply over two decades. A strike rate that was outstanding in 2010 is ordinary today.

Boundary percentage and the dot-ball problem

Two underused numbers explain more about a T20 innings than either of the headline ones. The first is boundary percentage: the share of deliveries a batter converts into fours or sixes. In a format where running two is hard work and running three is nearly extinct, boundaries do most of the scoring, and a batter with a high boundary percentage generates runs without needing to survive long.

The second is the dot-ball percentage, and it is the quiet killer. Every dot transfers pressure to the next delivery. A batter who plays out fifteen dots in a forty-ball innings has effectively handed his partners a shorter innings than the scoreboard suggests, even if his own strike rate looks respectable. For bowlers, the mirror applies: dot balls are the most reliable route to a wicket, because they force the risk.

Read these two alongside strike rate and a great deal becomes clearer — particularly why a 30 from 25 can be a worse contribution than a 20 from 11, and why bowlers who concede singles freely are rated below those who simply stop the scoring.

What “impact” really means

Impact metrics try to answer the question the basic numbers cannot: how much did this performance change the probable outcome of the match? A 20-ball 35 while wickets tumble in a chase can matter more than an unbeaten 60 in a game already decided.

These models are useful and worth reading, but they are interpretations rather than facts, and different models disagree. Treat an impact rating as one informed opinion among several — not as a settled measurement like balls faced. The raw scorecard is the ground truth; everything built on top of it involves judgement.

You can test all of this yourself. The ball-by-ball scorecards and the Statsguru query tool on ESPNcricinfo let you split a career by phase, opposition and ground, and it is genuinely instructive to see how differently the same player reads once the powerplay, middle and death overs are separated.

Patterns, streaks and randomness

One more habit worth carrying beyond cricket. Humans are exceptionally good at seeing patterns in short runs of data, and exceptionally bad at recognising when those patterns are just noise. A batter with three low scores is “out of form”; a batter with three high ones is “in the zone”. Sometimes true, often simply variance.

The same illusion drives “chart reading” in games of pure chance, where results are random by design. A colour appearing five times in a row does not make the sixth outcome more or less likely — the game has no memory. Our prediction tips page explains this honestly, and our responsible prediction-games guide covers why no game or model can predict a cricket match either.

Final thoughts

The whole skill of reading a T20 scorecard fits into one sentence: strike rate tells you how fast, average tells you how long, balls faced tells you whether either number deserves attention, and the phase of the innings tells you what “good” even means. Add a decent sample size and most bad cricket arguments disappear.

Try it on a real career next — our Vaibhav Suryavanshi guide is a good test case, because the numbers are extraordinary and the sample is tiny. For where each player fits, read the young T20 core guide, and for the break between innings, 66 Lottery has a free demo. Play as an adult, and never confuse a pattern with a prediction.