T20 Stats Explained: Strike Rate, Average, Impact and How to Read a Scorecard

Strike rate is runs per 100 balls. Batting average is runs per dismissal. Almost every bad cricket argument on the internet comes from reading one without the other, or from comparing two batters doing completely different jobs. This 66 Club Lottery guide explains what each T20 number actually measures, what it hides, and how to read a scorecard so it tells you the truth.

Quick Answer: The Two Core Numbers

A batter who scores 45 from 30 balls has a strike rate of 150. A batter with 300 runs and six dismissals averages 50. Both figures are simple arithmetic — the difficulty is entirely in interpretation, and that is what the rest of this page is about.

Strike Rate, Properly Explained

Strike rate is the T20 number, because in a format with a fixed ball allocation the scarce resource is deliveries rather than wickets. A batter who scores 30 from 30 balls has, in most situations, actively cost the side runs even though the scorecard looks tidy.

But strike rate on its own is close to meaningless without three companions:

• Balls faced. A strike rate of 200 from six balls is a nice cameo. The same figure from sixty balls is a match-winning innings. The number is identical; the achievement is not remotely comparable.
• Phase. Runs come more easily in the powerplay with fielding restrictions than at the death against a spread field and a yorker plan.
• Match situation. Scoring at 160 while three wickets down in the fourth over is a very different task from scoring at 160 with a platform already built.

Batting Average and What It Hides

Average is runs divided by dismissals, not by innings. That single detail creates most of the confusion around it, because not-outs inflate the figure. A finisher who is regularly unbeaten at the end of an innings accumulates a flattering average without necessarily being more reliable than anyone else.

Average was designed for a format where occupying the crease was the point. In T20 it has been demoted to a supporting role: useful for anchors and top-order batters who face a lot of balls, close to irrelevant for a specialist finisher. If you are going to use it, use it next to innings played, not-outs and balls faced.

Why the Two Only Work Together

Take four hypothetical batters and you can see immediately why one number never settles an argument:

The second row is where most bad takes live. A player with a low average and a huge strike rate is routinely called inconsistent when they are, in fact, executing a brief that guarantees frequent dismissals. Judge the player against their role — the roles are set out in our India's young T20 batting core guide.

Phase Matters More Than the Total

Modern T20 analysis is almost entirely phase-based, because a T20 innings is really three different games stitched together:

A career strike rate is an average across all three, which is why two batters with identical headline figures can be doing entirely unrelated jobs. Any decent statistics site lets you split by phase, and doing so is the single biggest upgrade you can make to how you read cricket.

Bowling Numbers: Economy vs Strike Rate

The bowling side has its own pair of numbers that people mix up just as often:

• Economy rate — runs conceded per over. In T20 this is usually the headline figure, because containment is how matches are won.
• Bowling strike rate — balls per wicket. This matters for the bowler whose job is to break a partnership rather than to dry up an end.
• Bowling average — runs per wicket. Least useful of the three in T20, since it blends both jobs into a single number.

The same phase logic applies. A death-overs specialist with an economy of nine may be outperforming a powerplay bowler with an economy of seven, because they are bowling in the hardest four overs of the innings against batters who are attacking every ball.

How to Read a Scorecard Properly

1. Read the score in balls, not runs. "45 (30)" carries more information than "45".
2. Check when the batter came in. The fall-of-wickets line tells you the situation they walked into.
3. Look at the boundary count. Runs made in boundaries versus runs made in ones and twos describe very different innings.
4. Read the bowling figures alongside. A high strike rate against an expensive attack is a smaller achievement than the same figure against a tight one.
5. Note the conditions. Ground size, pitch behaviour and dew change what a par score even means.
6. Then, and only then, form a view. The headline number was never enough.

Six Stat Traps to Avoid

• Comparing across roles. An opener and a finisher are not competing on the same scale.
• Ignoring balls faced. The most common error in cricket discussion, by a wide margin.
• Treating not-outs as reliability. They inflate averages without proving anything.
• Cherry-picking a window. "Last five innings" can be chosen to prove any argument you like.
• Confusing volume with quality. A long career produces big totals; totals are not rates.
• Reading a viral graphic as data. Check it against a real database before repeating it.

Small Samples and the Pattern Reflex

The deepest problem in reading cricket statistics is not arithmetic. It is that human beings are built to see patterns in small amounts of information, and we do it automatically. Three good innings become "in form". Two failures become "struggling". Neither conclusion is supported by that little evidence.

This is the same reflex that leads people to read meaning into short runs of game results. In our result chart guide we make the point in a very different setting: a run of outcomes in a game of chance carries no information about the next one, however convincing the pattern looks. Cricket is not pure chance — skill genuinely persists — but the instinct to over-read a small sample is identical, and it misleads in both places.

The practical version: wait for more innings before you decide anything, and be suspicious of your own confidence when the sample is small. It is also why we treat every early-career figure in our Vaibhav Suryavanshi guide as indicative rather than conclusive.

Useful External Resources

• ESPNcricinfo — scorecards, career records and the statistics tools to split figures by phase.
• Twenty20 International (Wikipedia) — how the format and its records are formally defined.
• BCCI (official) — official squads, fixtures and match information for Indian cricket.

18+ and Responsible-Play Note

Statistics describe the past; they do not forecast anything, and this site publishes no predictions, tips or odds. The games at 66 Club Lottery are 18+ entertainment, are games of chance, and have no connection to cricket results. Set a budget before you play and keep it fixed — our responsible gaming guide covers the warning signs and support options.

Conclusion

Strike rate measures speed, average measures reliability, and neither means much alone. Read both next to balls faced, the phase the runs came in, and the situation the batter walked into. Do that and most cricket arguments resolve themselves, because you will notice that the two players being compared were never doing the same job.

And remember what statistics are for: describing what happened, not predicting what will. If you want a quick game between overs, the 66 Club Lottery Wingo game is a separate game of chance you can try free on the demo or read about in our match-day guide — 18+, inside a budget you set first.