Cricket Batting Statistics: Average, Strike Rate & Impact Explained

Cricket is, more than any other team sport, a numbers game. A scorecard tells you, at a glance, how many runs each batter made, how many balls they faced, how many overs each bowler bowled and how many wickets they took. From those raw counts, the sport has built a half-dozen derived metrics that fans and selectors use to compare players across formats, eras, and conditions. Most fans use them loosely. Some metrics actually mean something different from what they appear to mean. Strike rate in Tests is not the same conversation as strike rate in T20s. A batting average of 50 in ODIs is not the same achievement as a batting average of 50 in Tests. NRR is widely cited and widely misunderstood.

This piece is the evergreen primer. What batting average is, what strike rate is, what NRR (net run rate) is, what the Impact stat measures, and where each of them works and breaks. With worked examples, format-by-format context, and the misuse cases to watch out for.

---

Batting average

Definition: runs scored divided by times dismissed.

A batter who scores 1,000 runs and is dismissed 20 times has an average of 50.00. A batter who scores 1,000 runs and is dismissed 25 times has an average of 40.00.

The key word is "dismissed". Not-out innings count toward runs but not toward dismissals. So:

• 50, 60 not out, 30 = 140 runs, 2 dismissals → average of 70.00
• 50, 60, 30 = 140 runs, 3 dismissals → average of 46.67

The not-outs lift the average meaningfully when they accumulate.

What a "good" average means

Format by format:

• Tests: average above 50 = great; above 40 = good; above 30 = serviceable.
• ODIs: average above 45 = great; above 38 = good; above 32 = serviceable.
• T20Is/T20s: average above 35 = great; above 28 = good; above 24 = serviceable.

These thresholds shift over time. The 1990s benchmark for "great" Test average was 45+. Today it is 50+. By era and conditions, the bar moves.

Where average misleads

The single biggest misuse of batting average is in T20 cricket. A batter who scores 30 (40) and is not out has an average of, in that innings, infinity. A batter who scores 30 (15) and is dismissed has an average of 30.00. The first batter has the higher average. The second batter has done more for their team. T20 batting is about strike rate; average alone gives an incomplete picture.

A second misuse: across very different conditions. Tom Hayward's averages in 1900-era Tests on un-prepared pitches are not directly comparable to modern Test averages on covered pitches. Era matters.

For a worked example, see how we use combined metrics in our IPL 2026 powerplay openers Impact Query rankings. The IQ score is, in essence, a way of combining three batting numbers — runs, strike rate, dismissals — into one.

---

Strike rate

Definition: runs scored per 100 balls faced.

A batter who scores 50 off 30 balls has a strike rate of 166.67. A batter who scores 50 off 100 balls has a strike rate of 50.00.

What a "good" strike rate means

By format:

• Tests: strike rate above 60 = aggressive; above 50 = standard; above 40 = blocker (Cheteshwar Pujara, peak Rahul Dravid).
• ODIs: strike rate above 100 = aggressive; above 85 = standard; above 75 = anchor.
• T20Is/T20s: strike rate above 150 = aggressive; above 130 = standard; above 110 = slow.

A T20 strike rate of 130 in 2026 is, depending on the role, either acceptable (anchor at the top of the innings) or below standard (middle-order finisher).

Where strike rate misleads

A batter who scores 5 off 1 ball has a strike rate of 500. A batter who scores 50 off 25 balls has a strike rate of 200. The first batter has the higher strike rate. Sample size matters. Strike rate over a small number of balls is not informative.

The second issue: strike rate against weak attacks vs strong attacks. A 200 strike rate against a part-time bowler is less impressive than a 150 strike rate against a top-five death bowler.

---

Net Run Rate (NRR)

Definition: the difference between a team's scoring rate and the scoring rate they have conceded, averaged over a tournament.

NRR is calculated as:

NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled)

A team that has scored 600 runs in 50 overs and conceded 500 runs in 45 overs has:

• Run rate scored: 12.0
• Run rate conceded: 11.11
• NRR: +0.89

NRR is used in IPL and World Cup standings as a tiebreaker between teams on equal points.

Where NRR misleads

NRR rewards heavy batting wins (especially when defending) more than equivalent margin chases. A team that bowls the opposition out for 100 in 20 overs and chases in 10 overs has a much better NRR boost than a team that does the same chase in 18 overs.

This creates strange incentives at the end of league stages — teams sometimes manipulate batting tempo specifically to improve NRR for a tiebreaker.

For an explainer of how NRR factors into IPL playoff scenarios, look at the IPL 2026 home advantage and standings analysis — every season the bottom of the playoff cut-off is decided by NRR.

---

Impact stat

Definition: a composite metric (varying by definition; the most common is Cricbuzz's) that measures a player's contribution to a match's outcome relative to context.

Impact metrics are not standardised across cricket — different broadcasters and analytics firms use different formulas. The general shape is:

• Batting impact: runs scored, weighted by the difficulty of the chase or the value of the platform.
• Bowling impact: wickets taken, weighted by the value of the wickets (top-order vs tail).
• Fielding impact: catches and run-outs.

The most-cited derivative — Cricbuzz Match Performance Index, or various analytics-house derivatives — produces a single per-match number that captures the totality of a player's contribution.

Where the Impact stat misleads

Two issues. First, methodology varies between providers, so a Cricbuzz Impact and an ESPNcricinfo "Match Performance" are not the same number. Second, the metric reflects what the formula values, which is not always what fans value. A batter who scores 30 in a successful chase will sometimes score lower on a no-context Impact metric than a batter who scores 80 in a losing cause.

The metric is genuinely useful but only when read alongside the underlying numbers.

---

Strike rate vs average — the key tension

The most important thing a fan should understand about cricket statistics is this: average and strike rate are different lenses, not interchangeable ones.

In Tests, average is the primary lens. The job is to score runs without getting out. Strike rate matters secondarily — you cannot score 80 over 50 overs and call yourself a Test great — but the dismissal rate is the headline.

In T20s, strike rate is the primary lens. The job is to score fast. Dismissal rate matters secondarily — you cannot strike at 200 if you average 8 — but the run rate is the headline.

In ODIs, both matter equally. A batter averaging 45 at strike rate 75 (Mahela Jayawardene-style) is comparable to a batter averaging 38 at strike rate 95 (Jos Buttler-style). Different routes to similar value.

---

Worked example: comparing two T20 openers

Player A — IPL 2026:

• 6 matches
• 240 runs
• 3 dismissals
• 150 balls faced

Average = 240 / 3 = 80.00. Strike rate = 240 × 100 / 150 = 160.00.

Player B — IPL 2026:

• 6 matches
• 220 runs
• 5 dismissals
• 130 balls faced

Average = 220 / 5 = 44.00. Strike rate = 220 × 100 / 130 = 169.23.

Who is more valuable? Average says Player A by a wide margin. Strike rate says Player B is slightly faster. The richer comparison: Player A occupies the crease more, scores almost as fast, and gets out less. Player A is more valuable in most match-states.

For a real worked example using these comparisons, see our IPL 2026 powerplay openers Impact Query analysis — every batter on that list has been ranked by combining all three numbers.

---

When format conversion misleads

A batter who averages 50 in Tests does not, in any meaningful sense, also average 50 in T20s. The roles are different.

The trap: someone takes Virat Kohli's Test average (50+) and Hardik Pandya's T20 strike rate (150+) and treats them as the same kind of stat. They are different stats produced under different mandates.

A clean way to understand this: in Tests, you bat as long as you can. In T20s, you bat as fast as you can. The metric that matters is the metric the format demands.

For the deeper history of how these formats co-existed and evolved, see our Indian cricket history 1928 to 2026 timeline. The shift from a Test-only world to a multi-format world is also a shift in which metrics dominate.

---

What about boundary percentage and dot percentage?

Two derived metrics worth knowing:

• Boundary percentage: percentage of total runs scored in fours and sixes. Higher = more boundary-dependent.
• Dot percentage: percentage of balls faced that did not score a run. Lower = more rotational.

A T20 batter with 70% boundary and 35% dots is a high-volatility hitter (think a death-overs power-hitter). A T20 batter with 50% boundary and 25% dots is a high-control rotational batter (think a middle-order anchor).

Both can be valuable; they fit different roles.

---

When to use which metric

• Comparing across Tests and Tests: average is fine.
• Comparing within T20s: strike rate, then average, then boundary percentage.
• Comparing across formats: roles, then strike rate, then average. Never average alone.
• Tournament-level standings: NRR for tiebreakers, total points first.
• Player-of-the-match arguments: Impact stat (with context), then runs/wickets.

For the wider WTC 2025-27 cycle context and how Test averages drive PCT calculations, see our explainer pieces. And for the late-April 2026 ICC Test rankings analysis, the underlying metric is Test runs scored — but adjusted by Test pedigree of the bowling attacks faced.

---

Frequently Asked Questions

What is a good batting average in Test cricket? A Test average above 50 is great; above 40 is good; above 30 is serviceable. Cricket history's greats — Bradman (99.94), Tendulkar (53.78), Lara (52.88), Smith (56-plus) — all sit above 50.

What is a good strike rate in T20 cricket? A T20 strike rate above 150 is aggressive and good for a powerplay opener; above 130 is standard; above 110 is slow and only acceptable for an anchor role. Top finishers strike at 180-plus.

How is Net Run Rate calculated? NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled). A team with NRR +0.89 has scored 0.89 runs per over more than they have conceded across the tournament.

Why can batting average mislead in T20 cricket? Because T20 is about scoring rate, not dismissal rate. A batter averaging 35 at strike rate 170 is more valuable than a batter averaging 50 at strike rate 110. The dismissal rate matters less when the goal is to score fast.

Are not-outs included in batting average? No. Not-out innings count for runs but not for the dismissal count. This means a batter with multiple not-outs has a higher average than a batter who scored the same total runs and was dismissed every innings.

---

Cricket statistics are not difficult, but they are easy to use carelessly. Average tells you about dismissal rate. Strike rate tells you about scoring tempo. NRR tells you about tournament margins. Impact tells you about contribution. Use the right metric for the right question, and the numbers stop misleading.