Cricket Batting Average Guide: Meaning, Formula & Examples

The number that defines a batter, more than any other, is often just a single figure on a scorecard. It’s there in black and white, next to the runs and the asterisks that hint at stubborn resistance. Coaches use it as shorthand for reliability. Selectors lean on it when a gut call feels too risky. Fans argue over it like it’s a birthright. Cricket batting average: a simple fraction that captures a lifetime of judgment, shot selection, patience, and the occasional slice of fortune.

I’ve sat in dressing rooms where a player shielded the screen of his phone like it contained state secrets, quietly updating a notes app with his latest innings, recalculating the number that meant everything to him. I’ve watched a rookie opener realize, after a string of gritty not-outs, that his average had ballooned and suddenly expectations felt different. I’ve stared at dusty ledgers in county pavilions and seen averages inked carefully by hand, an entire season memorialized as a number to the second decimal. The statistic is as old as cricketing record-keeping, but its meaning keeps evolving with formats, roles, and the way teams approach risk.

This is a complete guide to batting average in cricket—from the formula to the nuance, from Test matches to T20 leagues, from not-out quirks to advanced, era-adjusted views. Along the way, I’ll share worked examples, give you a calculator you can copy into a spreadsheet, and lay out the benchmarks that scouts and analysts quietly use to separate the promising from the proven.

What Is Batting Average in Cricket? Meaning and intuition

Short definition: Batting average is the total runs scored divided by the number of times the player has been dismissed.
Intuition: It captures how many runs, on average, a batter scores per dismissal. Strip away formats and roles, and it’s the most faithful long-run measure of run-scoring reliability.

There’s elegance in that simplicity. In Tests and first-class cricket, where time and wickets are the hard currency of winning, batting average remains the central, trusted stat. In ODIs, with a fixed quota of overs, average maintains strong importance—especially for top-order players who anchor innings. In T20s, where intent is non-negotiable and scoring tempo dictates match scripts, average yields some ground to strike rate. Yet even in T20s, elite batters still treat their wicket like a scarce resource; the best manage to keep an above-average average while attacking.

Average is not a complete picture—no one metric is—but it is still the clearest, most stable shorthand for “How much do you usually give us before you get out?”

Batting Average Formula in Cricket: How to calculate

The formula is universal across formats.

Batting average = Total runs scored / Total dismissals

Key terms:

Runs: Sum of all runs credited to the batter across innings.
Dismissals: Occasions when the batter is out. Not-outs are not counted as dismissals.
Not out: When a batter’s innings ends without being dismissed (e.g., innings closed, target reached, partners all out).

Do not include:

Did Not Bat (DNB): No innings, no effect.
Retired hurt/ill (if the player does not return and the innings ends): Not a dismissal.
Absent hurt: Not a dismissal.

Include:

Run-outs where the striker (or non-striker) is the batter dismissed: count as a dismissal for that player.
Obstructing the field, timed out, hit wicket, etc.: dismissals.

Core example 1: Pure dismissals, no not-outs

Innings: 42, 17, 63, 4, 28
Total runs = 154
Dismissals = 5
Average = 154 / 5 = 30.80

Core example 2: With not-outs

Innings: 35*, 12, 9*, 51, 22
Total runs = 129
Not-outs = 2 (35*, 9*)
Dismissals = 3 (12, 51, 22)
Average = 129 / 3 = 43.00

Note how not-outs reduce the denominator (dismissals), inflating the average. That isn’t a bug; it reflects that the batter protected their wicket through to the end of the innings.

Core example 3: Retired hurt and return

Innings sequence: 44, retired hurt (returned later and out on 60), 10
Runs: 44 + 60 + 10 = 114
Dismissals: The 60 ended in dismissal; retired hurt is just an interruption, not an outcome by itself
Total dismissals = 2 (the 60 when out, and the 10)
Average = 114 / 2 = 57.00

Worked examples across formats (scenarios)

Scenario: Early-career Test opener

Innings: 8
Scores: 4, 29, 5, 13, 41, 0, 74, 18
Not-outs: 0
Runs: 184
Dismissals: 8
Average: 23.00

Scenario: ODI anchor batter

Innings: 7
Scores: 85*, 45, 2, 101, 37*, 12, 64
Not-outs: 2
Runs: 346
Dismissals: 5
Average: 69.20

Scenario: T20 finisher

Innings: 8
Scores: 9*, 18*, 2, 27, 10, 33*, 15*, 5
Not-outs: 4
Runs: 119
Dismissals: 4
Average: 29.75

Scenario: IPL top-order aggressor

Innings: 10
Scores: 48, 7, 61, 3, 27, 39, 14, 75, 10, 0
Not-outs: 0
Runs: 284
Dismissals: 10
Average: 28.40

Cricket Batting Average Calculator (with not-out handling)

Use this quick method on any device:

Add up runs from all completed innings (include those with asterisks).
Count dismissals only from innings where the batter was out.
Divide total runs by total dismissals.
Round as needed (two decimals are common).

If you want a simple web snippet for a personal notes page, here’s pseudo-code you can adapt:

Inputs:- Runs array: [scores as numbers; enter not-out innings as numbers too]- Outs array: [true/false for each, where true = dismissed, false = not-out]Computation:- total_runs = sum(Runs)- total_outs = count of true in Outs- average = total_runs / total_outs

Excel / Google Sheets calculator:

Put runs in column A (enter 35 for 35*, just the number; stars are visual only)
Put “1” in column B if dismissed, “0” if not out
Total runs: =SUM(A:A)
Total dismissals: =SUM(B:B)
Average: =IF(SUM(B:B)=0,’—’,SUM(A:A)/SUM(B:B))

Example layout:

Row 2: A2=85, B2=0 (85*)Row 3: A3=45, B3=1Row 4: A4=2, B4=1Row 5: A5=101, B5=1Row 6: A6=37, B6=0 (37*)Row 7: A7=12, B7=1Row 8: A8=64, B8=1

Average formula in, say, C10: =IF(SUM(B2:B8)=0,’—’,SUM(A2:A8)/SUM(B2:B8))

Downloadable template (copy this into a CSV and open in a spreadsheet app):

Innings,Runs,Dismissed(1=yes,0=no)1,85,02,45,13,2,14,101,15,37,06,12,17,64,1

You’ll get the same average as the ODI anchor example above.

API-minded? If you’re building a small tool, the critical data fields are:

runs: integer
dismissed: boolean
innings_id or match_id
format (Test/ODI/T20/FC/List A/League)
position (1–11)
not_out_reason (declarative text, optional): “innings closed”, “chased target”, “partners all out”

Not-out effect on batting average: the nuance and the edge cases

Not-outs are central to how batting average behaves. They remove an innings from the denominator, often lifting the number. But the effect varies by role and format.

Openers in Tests: Fewer not-outs (they usually bat early and get a result). Their averages are less padded by not-outs and can be a stricter test of skill.
Middle-order anchors: See more not-outs when declarations or chases end innings; their averages can drift higher given similar output.
T20 finishers: Not-outs are common when they close the innings. Finisher averages can look healthy even with modest aggregate runs. Analysts often look at boundary rate and strike rate alongside average to judge impact here.

Edge cases and official handling:

Retired hurt/ill: If the batter does not return and the innings ends, it is not a dismissal. If the batter returns and is later out, count that dismissal.
Retired out: Rare; it is a dismissal and counts in the denominator.
Runner used (where permitted historically): Dismissal is credited to the striker; rules governing runners have evolved, but the dismissal attribution remains clear.
Timed out/handled the ball/obstructing the field: All are dismissals.
Did not bat (DNB): No impact on average.
Run-outs: The dismissed batter is the one out, regardless of striker/non-striker status; it counts as a dismissal for that player.

Practical takeaway: Any time your innings does not end in dismissal, it does not increase the denominator. The more often that happens—especially for finishers and anchors—the healthier the batting average looks.

Batting average in different formats: What is a good number?

Context is everything. A “good batting average” depends on format, role, and conditions. Use these ballpark ranges as practical scouting heuristics. They’re not absolutes; they’re starting points.

Benchmarks by format (career-scale; assume meaningful sample size)

Test/first-class:
- Elite: 50+
- Very good: 42–49
- Solid: 35–41
- Fringe/under par: below 35
ODI/List A:
- Elite: 50+
- Very good: 42–49
- Solid: 35–41
- Fringe/under par: below 35
T20I/T20 (including IPL and other major leagues):
- Elite: 40+
- Very good: 32–39
- Solid: 25–31
- Fringe/under par: below 25

Notes on these ranges:

Test and first-class averages align more closely because both are multi-day formats, though Test quality is higher. A 45+ first-class average suggests strong Test potential but doesn’t guarantee translation.
ODI batting average correlates strongly with top-order role; middle-order finishers often see more not-outs but fewer balls. An ODI average above 50 across a long career is rarified air.
In T20, the average must be viewed with strike rate. A top-order dasher at 30 average and 145+ strike rate can be more valuable than a 40 average at 120 strike rate, depending on team needs.

League specifics:

IPL batting average values should be interpreted with strike rate and role. A retained domestic anchor at 35 average with a strike rate around 130 can be a stabilizer, but sides increasingly prize players who sustain 140–150+ strike rates without cratering average below the solid range.

Batting average vs strike rate: The modern trade-off

In long-form cricket, average reigns. In white-ball cricket, and most dramatically in T20, strike rate tugs at the throne.

Average asks: “How many runs, per dismissal?”
Strike rate asks: “How fast are you scoring, per 100 balls?”

A batter’s overall run value in limited-overs cricket is a composite of both. You need to survive long enough to score, but you must also score quickly enough to match the tactical demands of the innings. This changes by role:

Openers in T20: Must maximize powerplay returns—value tilts toward strike rate. Still, a top-order player who averages around 30 with a strike rate above 140 is gold.
Middle-order enforcers: Higher strike rate, lower average acceptable; intent against spin and pace-off is prized.
Finishers: Will have more not-outs. A finisher who averages 25–30 with a strike rate above 150 is often ideal.
ODI anchors: Average retains stronger weight. Averages in the 40s with sustained strike rates above 90 are a premium blend.

Runs per dismissal (RPD) is just another way to say “batting average,” but analysts often combine it with:

Balls per dismissal (BPD): A durability measure.
Boundary percentage (4s+6s per balls faced).
Dot-ball percentage.
Phase splits (powerplay, middle, death).

When a batting lineup gets the balance right, average and strike rate complement each other. One-dimensional teams fixate on one and bleed on the other.

Records and leaders: highest career batting averages and context

A word of warning: records are hostage to qualification criteria. You can set a minimum innings threshold and get a radically different leaderboard. Always read the fine print.

Test cricket batting average

The Everest: Sir Don Bradman’s career batting average of 99.94. It is the sport’s defining statistic, the outlier that breaks our mental models. That number is both a ceiling and a mythos.
Modern top-tier: Sustaining a Test average above 60 is rare across a long career. Maintaining 50+ at the highest level over a substantial sample is the mark of a generational player.
Home vs away splits: Some players hover close to 60 at home but dip to the 40s away. Truly elite Test batters hold formidable numbers in both.

ODI batting average

With a low minimum innings threshold, you’ll see names like Ryan ten Doeschate top the charts thanks to extraordinary consistency over fewer matches.
With stricter thresholds (larger innings minimum), Virat Kohli’s ODI batting average sits in the high fifties across a heavy workload, standing out for both volume and class. Babar Azam’s career average in the mid-fifties over an extensive top-order role adds to the modern benchmark.

T20I batting average

T20Is are heavily role-dependent and sample sizes can be uneven. Virat Kohli has sustained an average above 50 across a long T20I career, a remarkable blend of control and chase mastery. Mohammad Rizwan has also maintained a high T20I average while opening, and several others hover in the 40s and mid-40s.
Qualification criteria distort the top list; always set minimum innings to filter short careers or cameo-heavy roles.

IPL batting average

Small-sample artifacts abound because of short seasons. Career IPL averages in the high 30s to mid-40s for top-order batters are outstanding when paired with elite strike rates. KL Rahul, Virat Kohli, David Warner, and Kane Williamson have all posted career averages that reflect their anchor or top-order roles. Among finishers, averages tend to be lower but strike rates higher.

Domestic and franchise leagues (BBL, CPL, PSL, county, Sheffield Shield, Ranji Trophy)

Conditions vary drastically. Australia’s BBL tends to reward power players with higher strike rates but leaves less room for bloated averages due to large grounds and pace-heavy attacks.
The CPL’s spin factor and slower decks can protect averages for methodical players who sweep and rotate well.
County cricket and Sheffield Shield provide fertile ground for first-class averages; sustained 40+ over seasons portends Test viability.
In Indian domestic cricket (Ranji and List A), a towering first-class average often propels national selection; translation to international runs depends on technique in higher pace and swing.

Year-by-year leaders

Leaderboards by calendar period are popular but volatile; players can post purple patches that vanish with role changes or injuries. Use them as form indicators, not career verdicts.

Home vs away batting average records

Splits by geography (Asia vs SENA—South Africa, England, New Zealand, Australia) shape reputations. Greats often show only a modest dip away from home, not a collapse.

Youngest players with 50+ batting averages

Early-career averages can be mirages. Analysts temper them using weighted or Bayesian adjustments until a player crosses a meaningful innings count.

Advanced and analytical views: beyond raw average

Median vs average in cricket batting

Average can be tugged upward by a few huge scores and frequent not-outs (particularly in T20).
Median tells you the middle score—how often a player hits a certain baseline.
Red flag: Player X averages 35 but has a median of 18; that suggests volatility—big scores with many small ones.

Adjusted batting average (era, conditions, opposition)

Era adjustment: Convert a player’s runs into a normalized scale based on the overall run-scoring environment of the time. For example, an average of 45 in a bowler-friendly era may be more valuable than 50 in a batting glut.
Opposition weighting: Runs against top-tier pace or spin units are weighted more heavily.
Venue/conditions weighting: Tricky venues (swing in England, bounce in Australia, spin in Asia) get adjustment multipliers.
Match situation weighting: High-leverage runs (pressure chases or pre-declaration accelerations) can be weighted.

Weighted batting average

Concept: Assign weights to innings based on difficulty (opposition, venue, match situation) and compute a weighted mean instead of a plain mean.
Practical use: Smoothing out easy runs against weaker attacks and rewarding tough runs in hostile conditions.

Consistency in batting average

Variation or volatility index: Standard deviation of scores or of dismissal-centered scores. Lower standard deviation = steadier contributor.
“50-to-duck” ratio: A back-of-the-notebook metric; good players minimize ducks while still converting starts into fifties.
Rolling averages: 10- or 20-innings rolling measures are better form trackers than single-season numbers.

Runs per dismissal metric

It’s just average, but watch it in conjunction with balls per dismissal. High RPD with very high BPD might indicate an anchor profile; in T20, teams now ask whether that anchor is fast enough to justify balls faced.

Qualification criteria for batting averages: why thresholds matter

Minimum innings: Most records and leaderboards demand a minimum number of innings to filter noise. For T20, that number needs to be higher than people think because variability is extreme.
Role qualification: Comparing a top-order opener’s average to a finisher’s can mislead. Some lists split by batting position.
Competition class: Combining international and domestic averages is unhelpful. Keep them separate; quality of opposition dramatically affects comparability.
Tournament-specific rules: Some leagues stipulate a minimum balls faced or innings threshold for season awards to avoid cameo-driven titles.

How is batting average calculated if not out? A fine-grained breakdown

If a batter is “not out,” that innings contributes runs to the numerator and zero to the denominator (dismissals).
If a batter retires hurt and does not return before the innings ends, it’s not a dismissal; the innings remains incomplete for batting-average purposes.
If a batter retires out (rare), it counts as a dismissal.
If a batter is a non-striker run out, the non-striker’s dismissal counts against their average.

This treatment reflects the core idea: you only add to the denominator when your wicket is taken.

Openers vs middle order, wicketkeepers, and captains: role-based batting averages

Openers

Face the new ball and highest swing/seam threat. Averages can lag slightly behind middle-order anchors, but the value of setting a platform is enormous.
Away from home in seam-friendly conditions, openers’ averages historically sag relative to middle-order contemporaries.

No. 3 and No. 4

The money positions. These batters often carry the heaviest average expectations—especially in Tests and ODIs—because they blend workload and control of the innings.

Middle-late order (Nos. 5–7)

Greater exposure to reverse swing in Tests; more high-leverage overs in ODIs; death overs in T20s. Averages can slide, but match impact may rise if they convert into quick, game-shaping cameos.

Wicketkeeper-batters

Once judged by glove work first, modern keepers must sustain batting returns. Elite wicketkeeper-batters match specialist batters’ averages in white-ball cricket and approach them in red-ball.

Captains

Some lift their batting averages while leading—clarity of role, greater responsibility. Others dip under the strain of tactics and scrutiny. The average can be a barometer of how captaincy fits their personality.

Left-hand vs right-hand batting average trends

Left-handers sometimes enjoy matchups against right-arm pace angled across them and can unlock gaps with natural cover and midwicket strokes. But in certain conditions—classical off-spin phases or left-arm orthodox angles—averages tighten.

Teams now engineer left-right pairs to complicate bowling plans; the impact on averages by handedness is more about matchup orchestration than innate edge.

Splits by geography and venue: how conditions sculpt averages

Asia vs SENA countries

In Asia, averages for players skilled against spin can rise. The ability to sweep (conventional and reverse), use depth of crease, and rotate with soft hands is decisive.
In SENA countries, seam movement, bounce, and carry test technique. High averages in these conditions demand a disciplined leaving game and a compact back-foot method.

Swinging conditions

Early movement punishes indecision. Openers’ averages usually trail there; middle-order players who enter against an older ball might maintain higher numbers.

Spinning tracks

Average preservation depends on scoring options off good-length spin: sweep lines, footwork both forward and back, and low-risk rotation. Batters who can hit with the spin and manipulate fields keep their averages buoyant.

Iconic venues

Lord’s: Slope and morning movement challenge the first session; good players front-load caution and grow their average later in the day.
MCG: Bounce and size reward back-foot play and fitness. Patience powers averages here.
Wankhede: True bounce and quick outfield; players with high boundary percentage can keep healthy averages without undue risk.
Subcontinental fortresses: Long spells of quality spin; conversion rates decide the day. A batter’s average can hinge on playing late and with soft hands.

Women’s cricket batting average: same principles, distinct rhythms

The fundamentals are identical. In women’s cricket, standout ODI averages often belong to top-order players who anchor with high control. In T20, the balance mirrors the men’s game—strike rate wrestles with average, but the best sustain both. Format maturity, evolving domestic structures, and improved depth mean averages are stabilizing at higher levels as more players face top-quality opposition consistently.

Analysts weigh:

Role clarity (top-order anchor vs finisher)
Spin-negotiation skills (critical across conditions)
Strike rate context (especially in powerplays and death overs)
Consistency metrics (median, volatility) alongside average

Career average vs season average: form, class, and moving windows

Season averages swing with small samples and role shifts. Career averages absorb the bumps and tell you who you are over the long ride. Smart analysis:

Use rolling windows (last 10/20 innings) to read form.
Compare season average to career average for context: a season spike might be powerplay-friendly schedules; a dip might reflect tougher venues.
For T20, a single bad run of dismissals can crater a season average. Don’t overreact without checking balls faced, boundary percentage, and role changes.

Cricket batting average in domestic pathways: first-class vs Test, List A vs ODI

First-class vs Test: A high first-class batting average signals readiness; translation to Test runs depends on handling higher pace, relentless accuracy, and elite spin. Expect a small haircut on the average when stepping up.
List A vs ODI: Similar profiles, but ODIs add pressure, planning, and top-tier bowling. A List A average in the 40s is promising; ODI sustenance in the 40s and 50s marks a cornerstone player.

Batting position and situational averages: micro-splits that matter

Powerplay vs middle vs death (white-ball): Averages vary by phase. Powerplay players can see edges behind and LBWs skew dismissals; death overs tempt big shots and risk profiles change.
Chasing vs setting: Some players’ averages inflate while chasing due to calculated tempo and more not-outs at successful finishes. Others excel at platform-setting.
Match-ups: Averages against left-arm pace or leg-spin can reveal exposures—useful for coaching plans and opposition scouting.

Common misunderstandings about batting average

“A high average means safe batting.” Not necessarily. Elite players can score quickly without sacrificing wicket control. Conversely, some accumulate low-risk runs slowly—valuable in Tests, risky in T20.
“Not-outs are cheap padding.” Finishers earn them by batting to the end; chasers earn them by winning. Context matters.
“Average alone ranks bats.” It’s the cornerstone, not the cathedral. Add strike rate, role, and conditions to complete the view.

Worked examples: calculation with tricky innings

Example A: Mixed results, declaration, and chase

Scores: 14, 66*, 0, 35, 22*, 51
Runs = 188
Not-outs = 2
Dismissals = 4
Average = 188 / 4 = 47.00

Explanation: The asterisks came from a declaration and a completed chase; both count as not-outs.

Example B: Retired hurt, returned later

Scores: 30, retired hurt on 7 (returned later, dismissed on 19), 44*
Runs = 30 + 19 + 44 = 93
Not-outs = 1 (44*)
Dismissals = 1 (the 19 ended in dismissal)
Average = 93 / 1 = 93.00

Example C: Finisher’s season in T20

Scores: 6*, 11, 28*, 2, 14, 9*, 0, 17*
Runs = 87
Not-outs = 4
Dismissals = 4
Average = 21.75

Insight: The average looks moderate, but if those not-outs coincide with wins and the strike rate is sky-high, the season can still be elite from a role perspective.

Benchmarks table: What is a good batting average in each format?

Format benchmarks (career scale, broad guidance)

Format	Elite	Very good	Solid	Below par
Test	50+	42–49	35–41	below 35
ODI	50+	42–49	35–41	below 35
T20I	40+	32–39	25–31	below 25
IPL and top T20 leagues	38–45+ (SR 140+)	32–37 (SR 135+)	25–31 (SR 130+)	below thresholds above

Remember: In T20, the strike-rate requirement rises as average falls. A player with a 30 average can be outstanding if they clear the strike-rate bar for their role and venue mix.

Adjusted and weighted average: a practical recipe you can use

If you want to create an adjusted batting average for your club or analysis project:

Define baseline difficulty by league: Assign a run-scoring index by competition/venue (100 = neutral).
Adjust each innings: adj_runs = runs * (100 / venue_index).
Opposition tiering: Multiply by a small factor (e.g., 1.05 for top-tier attacks, 0.95 for below-tier).
Weight by leverage: Add a 1.1–1.2 multiplier for high-pressure chases or crisis entries; 0.95 for low-leverage padding.
Compute adjusted average: sum(adj_runs) / dismissals.

This doesn’t produce an official number, but it’s invaluable when comparing players across varied environments.

IPL batting average: season spikes, role changes, and sample traps

A blistering six-week run can catapult a player’s season average, but career evaluation should use multi-season aggregates and role stability.
Top-order anchors can post season averages north of 40 with strike rates in the 130–140 range; teams increasingly prefer those who sustain 140+ while keeping the average healthy.
Finishers should be judged on average, strike rate, and game state conversion (how often did your not-outs come in wins or close finishes?).

County championship, Ranji, Sheffield Shield, and domestic lists: reading averages like a scout

Sustained 45+ in county first-class cricket suggests strong technique and temperament, especially if the player’s away and early-season numbers are solid.
In Ranji, huge first-class averages must be filtered by opposition quality and conditions; look at performances on seaming decks or against top domestic attacks.
In Sheffield Shield, bounce and pace harden the examination; a batter keeping averages in the 40s season after season earns selectors’ trust.

Batting average inflation and era effects

Fielding standards, bowling workloads, bat technology, and white-ball field restrictions influence scoring environments.
Some eras produce higher base averages; others are bowler-dominant. Without era adjustment, cross-era comparisons are riddled with bias.
League scheduling quirks (day-night matches, used pitches) shift year-on-year averages in subtle ways; rolling multi-season windows are safer.

How many innings are needed for a reliable batting average?

Tests: Roughly 20–30 innings before the number stabilizes to a useful baseline. Even then, splits and conditions matter.
ODIs: Around 25–35 innings for meaningful signal due to role volatility.
T20: Much more. You may need 40–60 innings to trust the baseline, given volatility and role changes. Supplement with strike rate, boundary percentage, and phase splits.

Early-career outliers abound; use shrinkage (e.g., blend with a league-average prior) to temper conclusions until the sample matures.

Cricket batting average vs batting index and other adjacent stats

Bowling average vs batting average: A bowler’s average is runs conceded per wicket—lower is better. A batter’s average is runs per dismissal—higher is better. Together, they frame team balance.
Economy rate vs average (bowling): Economy tells you how quickly runs are conceded; average tells you cost per wicket. Batters face the analogous pair with average and strike rate.
Batting index: Some proprietary models combine average and strike rate into a single value. Useful for sorting, but always decode the formula before trusting the rank.

Home vs away, by year splits, and qualification thresholds: how to use records without getting trapped

Always check minimum innings. Raising the bar filters noise.
When comparing across conditions (Asia vs SENA), note role stability. An opener forced to switch roles mid-tour can see splintered numbers that aren’t skill-based.
For year splits, beware schedule effects (opposition mix, home-heavy slates). A season of flat tracks can make a mid-career jump look like a skill leap when it’s schedule luck.

Frequently Asked Questions (expert answers)

How is batting average calculated in cricket?

Total runs divided by total dismissals. Not-outs add runs without adding a dismissal, lifting the average.

Do not-outs increase batting average?

Usually, yes. Because they reduce dismissals, not-outs raise average—especially common for finishers and chasers.

What is a good batting average in Tests/ODIs/T20s?

Tests: 50+ elite, 42–49 very good, 35–41 solid.
ODIs: 50+ elite, 42–49 very good, 35–41 solid.
T20s: 40+ elite, 32–39 very good, 25–31 solid. In T20, also demand strong strike rates.

Why is batting average less used in T20s?

Because run tempo wins T20 games. Average measures run volume per dismissal, but without strike rate you can’t judge impact. Teams prize players who sustain both decent average and high strike rate.

Who has the highest batting average in Test cricket?

Sir Don Bradman, at 99.94. No other player has approached that over a substantial career.

What’s the difference between batting average and strike rate?

Average measures runs per dismissal; strike rate measures runs per 100 balls. In Tests, average holds more sway; in T20s, strike rate often takes priority for top-order and middle-order hitters, though average still matters.

A tactical lens: coaching with average in mind

For openers: Train judgment outside off. Increase leave percentage early in Tests; the reward is a rising average through fewer thin edges and feathers behind.
For anchors: Practice pace modulation—start steady, expand later. Your average depends on not getting stuck and handing momentum back.
For finishers: Game the scenario tree. Two boundaries and a sprinted two can be worth more to winning than an unbeaten 22; but stack enough of those smart finishes, and your average stays sturdy anyway.
For ODI roles: Fitness and strike rotation keep your average stable on slow decks where big hits dry up.
For T20: If your average is healthy but your strike rate lags, build boundary options—slog-sweep rehearsals, pick-up over midwicket, and ramps. If your strike rate spikes while average collapses, work on “in-between” scoring—hard-run twos and late cuts that reduce dot pressure.

Home truths about batting average

It rewards resilience, not just brilliance. Four gritty 40s can weigh more than a solitary, glorious 140 if you’re building a series.
It punishes brain fades. Soft dismissals percolate through an entire season.
It respects context, silently. You want high averages that travel—across venues, across roles, across formats.

Practical tools: quick-reference formulas and templates

Universal formula: Average = SUM(Runs) / SUM(Dismissals)
Spreadsheet guide:
- Runs in column A
- Dismissed (1=yes, 0=no) in column B
- Average cell: =IF(SUM(B:B)=0,’—’,SUM(A:A)/SUM(B:B))

CSV template (copy/paste to start tracking):

Innings,Runs,Dismissed(1=yes,0=no)1,,2,,3,,4,,5,,Total,,=SUM(B2:B6)Dismissals,,=SUM(C2:C6)Average,,=IF(SUM(C2:C6)=0,'—',SUM(B2:B6)/SUM(C2:C6))

Quick mental math:
- If you’re out every time, average equals mean score.
- If you’re not out in a third of innings, your average roughly equals runs divided by two-thirds of innings (useful approximation if scores are broadly similar).

In praise of outliers and context

If batting average were a person, it would be a quietly obsessive teammate—meticulous, sometimes unforgiving, often insightful. It knows the difference between pretty 20s and match-winning 80s, between a survivor and a streaker. It understands that mistakes cost and that patience compounds. It’s old-fashioned, perhaps. But when a player walks out under a red ball and a heavy sky, there’s still no better starting point to know who you’re trusting with your day.

Yet average doesn’t travel alone anymore. The modern game insists on speed, adaptability, and matchup mastery. The best batters carry a high average into hostile conditions, then add the rocket fuel of strike rate when white-ball constraints demand it. They respect the statistic without becoming a prisoner to it.

So track your average; give it the dignity of good data. Count not-outs correctly. Separate formats. Note venues, roles, and match situations. Annotate your ledger with the things the box score forgets. Over time, that single figure will tell the truest story it can—of what you give your team each time you take guard, and how often you leave the field with your wicket, and the match, still in your hands.