T20 Stats Explained: Strike Rate, Average & Impact

टी20 में स्ट्राइक रेट = (रन ÷ गेंदें) × 100, और औसत = रन ÷ आउट होने की संख्या। दोनों को साथ पढ़ना ज़रूरी है — अकेले कोई भी आँकड़ा पूरी कहानी नहीं बताता। आँकड़े यह बताते हैं कि पहले क्या हुआ; वे अगली पारी की भविष्यवाणी नहीं करते।

Quick answer

Strike rate is runs per 100 balls faced — (runs ÷ balls) × 100. Batting average is runs divided by the number of times a batter has been dismissed. In T20 the two must always be read together, because a high strike rate over very few balls and a high average built slowly can both be misleading in opposite directions. Add boundary percentage, dot-ball percentage and the phase of the innings a player bats in, and you have a genuinely useful picture. Any single number in isolation is a headline, not an analysis.

Strike rate: the T20 headline number

Strike rate answers one question — how quickly does this batter score? The formula is simply (runs ÷ balls faced) × 100. A batter who makes 45 from 30 balls has a strike rate of 150.00; the same 45 from 40 balls is 112.50. In a format where every team faces the same 120 legal deliveries, the rate at which a batter converts balls into runs is close to the whole game.

Two cautions. First, strike rate is meaningless over tiny samples. A batter who hits a six off the only ball faced has a strike rate of 600, which tells you nothing. Second, it is heavily shaped by when a batter bats. A finisher facing six balls in the nineteenth over is operating under different constraints from an opener facing thirty in the powerplay, and comparing their raw strike rates without noting that is a category error. This is exactly the trap people fall into when a headline quotes a young player's figure after three innings — see our Vaibhav Suryavanshi guide for how quickly small samples produce extreme numbers.

Batting average: still useful, differently

Batting average is runs ÷ dismissals — note, dismissals, not innings. Not-outs are excluded from the denominator, which is why a finisher who is frequently unbeaten can post an unusually high average without ever facing many balls. In Test cricket, average is close to the definitive measure of a batter, because time is not the binding constraint. In T20 it is a secondary measure: it tells you about reliability, how often a batter converts a start into something substantial, and how rarely they fail cheaply.

What it does not measure is cost. In T20 a slow innings consumes a resource — balls — that the team cannot get back, so a batter with a high average and a low strike rate may be actively hurting the total while looking good on the scorecard. That is the central insight of modern T20 analysis, and it is why the format's selection logic changed.

Why the two must be read together

A framework for reading numbers, not a rating system. Always check the innings count before drawing any conclusion from a T20 batting record.

Boundary percentage and dot balls

Two supporting metrics do a lot of quiet work. Boundary percentage is the share of balls faced that went to the fence — because T20 totals are built overwhelmingly from fours and sixes rather than accumulated singles, a batter's boundary rate often explains their strike rate better than anything else. Dot-ball percentage is its mirror: the share of balls that produced no run. A batter can have a decent strike rate while leaking dots if they clear the ropes often enough, but consecutive dots transfer pressure to the other end and are a common cause of a middle-order stall.

For bowlers the same pair inverts — a high dot-ball percentage is an asset, and boundaries conceded per over is often more revealing than raw economy.

Bowling: economy, average and strike rate

1. 1

   Economy rate = runs conceded ÷ overs bowled

   The T20 headline for bowlers. Under seven is generally strong; context matters hugely depending on the phase bowled.

2. 2

   Bowling average = runs conceded ÷ wickets taken

   How expensive each wicket was. Less central in T20 than in longer formats, but useful for strike bowlers.

3. 3

   Bowling strike rate = balls bowled ÷ wickets taken

   How often a bowler takes a wicket. Note it means the opposite of a batting strike rate — lower is better.

4. 4

   Dot-ball percentage

   Often the best single indicator of a T20 bowler's control, because dots build the pressure that produces wickets at the other end.

5. 5

   Phase of the innings bowled

   A death bowler's economy is measured against a different bar from a powerplay or middle-overs bowler. Never compare across phases blindly.

What "impact" really means

Broadcasters increasingly use "impact" ratings, and the idea behind them is sound: a run in the nineteenth over of a tight chase is worth more than a run in the fourth over of a dead rubber, so raw totals under-describe what happened. Impact models weight contributions by match situation — pressure, phase, the quality of bowling faced, the state of the game — and produce a single figure.

Treat these figures as interpretive rather than factual. Every impact model embeds somebody's judgement about how much a situation is worth, different providers weight things differently, and the same innings can score quite differently across two systems. That does not make them useless — it makes them an argument, not a measurement. Runs, balls and wickets are facts; impact is a model.

Phases: powerplay, middle overs, death

Almost every T20 statistic makes more sense once split by phase. The powerplay (overs 1–6) has fielding restrictions, so boundaries are cheapest and attacking batting is at its most efficient. The middle overs (roughly 7–15) are where spin operates and where innings most often stall — this is the phase that separates good T20 batting units from ordinary ones, and it is why teams pick specialist spin-hitters. The death (16–20) is chaos by design: extreme strike rates, high dismissal rates, and numbers that look absurd out of context.

Once you internalise the phases, a lot of selection logic becomes legible — including why India's current side is built the way it is, which our young T20 core guide sets out role by role. Background on the format is on the Twenty20 International reference page.

How to read a scorecard in five steps

• Read runs and balls together, always. "42" means nothing; "42 off 21" means something.
• Note the batting position and the over they came in. Role explains most apparent anomalies.
• Check the bowling faced. A score against a full-strength attack is not the same as one against a depleted one.
• Look at the fall-of-wickets column. It reveals whether a batter was rebuilding or free to attack.
• Check the sample size. Under about fifteen innings, any T20 batting record is noise dressed as a trend.

Do those five and you will read a scorecard better than most people quoting statistics on social media — where cricket numbers are shared stale, cropped or simply invented at least as often as they are shared accurately.

The hard limit of all cricket statistics

Here is the boundary this guide will not cross. Every metric above is descriptive. It summarises what has already happened. None of them forecasts what a player will score in the next match or what the next ball will do, and no amount of analytical sophistication changes that. Cricket is a high-variance game played by human beings in conditions that shift by the hour.

So when you see statistics deployed as though they predict a result — with odds attached or without — be sceptical of the framing. We do not publish odds, betting content or match predictions on this site, and we would not present statistics as a way to forecast one. Our responsible fan-play guide covers the distinction between enjoying a game around a match and treating it as a way to profit from cricket knowledge.

The same principle governs our own products, and we would rather say it plainly than bury it. The 66 Lottery Wingo game and colour prediction are games of chance — every round independent and random, no skill, no reading of patterns, no cricket knowledge that helps. If you want to see how a round works, try it free on demo Wingo. Set a limit before you start (our budget basics guide shows how), never chase a loss — the clearest early sign of problem gambling — and use the responsible gaming page for free confidential support. Strictly 18 and over.