Audited ·Last updated 28 Jul 2026·7 citations·Tier 1·0 uses

Cricket Batting Average Calculator

Cricket batting average = runs divided by dismissals, with not-outs excluded from the denominator. Solve for average, runs needed, or dismissals.

Cricket Batting Average Calculator

What do you want to work out?
Every run credited to the batter: runs off the bat plus any runs the striker is credited with from a no ball. Byes and leg byes go to the team, not the batter (MCC Law 23), so leave them out.
runs
Count every innings in which the batter went to the crease, including the not-out ones. Innings where the batter did not bat at all are not counted. Ignored when you solve for dismissals.
inns
Innings that ended with the batter undismissed. A batter recorded 'Retired – not out' under MCC Law 25.4.2 belongs here; 'Retired – out' under Law 25.4.3 does not, because that counts as a dismissal.
n.o.
Only used by the 'runs needed' and 'dismissals affordable' modes. An average of 50 is the traditional Test-class benchmark; 40 is a strong first-class career.
runs/out
Batting average
44.5714
Runs scored per dismissal — total runs divided by innings minus not outs. This is the figure printed in the 'Ave' column of every scorecard and career record.
Dismissals
28
Runs per innings
36.7059
Not-out rate
17.65%
Total runs
1,248 runs
Innings
34 inns
Not outs
6 n.o.

Background.

A cricket batting average is total runs divided by the number of times the batter has been **dismissed** — not by the number of innings played. Not-out innings are removed from the denominator entirely. That single convention is what separates the cricket average from every other batting average in sport, and it is the reason a middle-order finisher who is stranded unbeaten twice a season carries a materially higher average than a top-order batter who scores exactly the same runs off exactly the same number of trips to the crease.

The International Cricket Council states the denominator plainly on its own rankings page: a team rating, it explains, "can be compared with a batting average, but with points instead of total runs scored and a match/series total instead of number of times dismissed." The peer-reviewed literature writes it in symbols the same way — Lemmer, in the Journal of Sports Science & Medicine, defines it as AVE = R/out, "where R is the total number of runs scored and 'out' the number of times the batsman was out." This calculator implements exactly that identity, Average = Runs ÷ (Innings − Not outs), and nothing else.

If you have arrived here from baseball, note carefully that this is a different statistic wearing the same name. A baseball batting average is hits divided by at-bats, a proportion bounded between .000 and 1.000, and a .300 season is excellent. A cricket batting average is runs per dismissal, an unbounded quantity where 40 is a fine career, 50 is the traditional mark of a great, and the all-time Test record sits at 99.94. The two numbers cannot be compared, converted, or averaged together, and Quanta keeps them on separate pages for that reason.

The not-out rule creates the one real judgement call in the arithmetic, and the Laws of Cricket settle it. Under MCC Law 25.4.2, a batter who retires because of "illness, injury or any other unavoidable cause" and cannot resume is recorded as "Retired – not out", so no dismissal is added. Under Law 25.4.3, a batter who retires for any other reason and does not resume is recorded as "Retired – out", and that counts as a dismissal in the denominator even though no bowler took a wicket and no fielder made a catch. Get those two rows the wrong way round in a season book and every average in the column moves.

The calculator runs in three modes, all rearrangements of the same identity. The default mode takes runs, innings and not outs and returns the average. The second mode inverts it: give it a target average and your innings and not-out counts, and it returns the aggregate of runs you would need. The third mode asks the selection-committee question — at a given average, how many dismissals can a stated pile of runs absorb before the average drops below the line? Every mode returns the same seven figures, including the deliberately unflattering "runs per innings" number, which is what your average would be if the not-outs were counted as dismissals. Comparing the two tells you how much of a batting average is scoring and how much of it is survival.

Below the widget you will find the derivation, a fully worked season, the statistical objection to the not-out convention and why no governing body has replaced it, the way the average interacts with strike rate in limited-overs cricket, and the specific scorebook cases — retirements, runners, abandoned innings, a batter who did not bat — that decide whether a row enters the denominator at all.

What is cricket batting average calculator?

A batting average in cricket is the mean number of runs a batter scores between dismissals. Formally, Ave = R ÷ d, where R is the batter's aggregate runs and d is the number of completed innings — innings that ended with the batter out. Because an innings can end with the batter undismissed (the side is all out at the other end, the target is reached, the declaration comes, the overs run out, or the innings is closed by rain), cricket separates innings batted (I) from dismissals (d), with d = I − N and N the number of not outs. The statistic is quoted to two decimal places and printed in the 'Ave' column of every first-class, List A and T20 career record. Three consequences follow from the choice of denominator. First, the average is unbounded above: a batter who has never been dismissed has no defined average at all, and scorecards print a dash rather than infinity — which is why this calculator refuses to compute when not outs equal innings. Second, the average is not a rate per ball or per innings, so it says nothing about scoring speed; that is the job of the strike rate. Third, the average is sensitive to how often a batter finishes an innings unbeaten, which depends heavily on batting position: a number seven in one-day cricket is not out far more often than an opener, and a tail-ender who habitually survives to the end can post an average that flatters their scoring. Statisticians describe a not-out score as a right-censored observation — the batter would have gone on to some unknown higher score had the innings continued — and several corrected estimators have been proposed in the literature. None has been adopted by the ICC or by the record books, so the conventional runs-per-dismissal figure remains the standard, and it is the only figure this calculator produces.

How to use this calculator.

  1. Choose a mode. 'Batting average' is the default and answers the ordinary question. 'Runs needed' works backwards from a target average, and 'Dismissals affordable' tells you how many outs a given pile of runs can absorb at a stated average.
  2. Enter total runs. Count runs off the bat plus any runs credited to the striker from a no ball. Byes and leg byes belong to the team, not the batter (MCC Law 23), so exclude them; so do wides, which never reach the striker's column.
  3. Enter innings batted. Include every innings in which the batter came to the crease, not-out innings included. Matches in which the batter did not bat are not innings and must not be counted — this is the most common source of a wrong average.
  4. Enter not-out innings. An innings recorded 'Retired – not out' under MCC Law 25.4.2 belongs here. An innings recorded 'Retired – out' under Law 25.4.3 does not: it is a dismissal, even though no wicket was taken.
  5. Read the batting average as the headline number, then read 'Runs per innings' directly beneath it. The gap between the two is the entire effect of the not-out convention on this record, and the 'Not-out rate' tells you how large a share of the innings produced it.
  6. If you are comparing two batters, compare their not-out rates as well as their averages. Two batters on 44 with not-out rates of 4% and 25% are not the same player, and the second one's average is doing far more work than their scoring.
  7. To set a season goal, switch to 'Runs needed', type the average you want, and keep innings and not outs at their current values — the calculator returns the aggregate you must reach across those same dismissals.

The formula.

Ave = R ⁄ (I − N)

The identity is Ave = R ÷ d with d = I − N.

Step one is the denominator. Innings batted (I) counts every trip to the crease. Not outs (N) counts the innings that ended with the batter undismissed. Subtracting gives d, the completed innings — the only innings in which the batter's scoring was actually terminated by the opposition. Step two is a plain division: total runs divided by d.

Why dismissals and not innings? Because an innings that ends not out is an incomplete measurement. The batter was still scoring when the innings closed for a reason external to them: the last wicket fell at the other end, the target was reached, the captain declared, the allotted overs were bowled, or the weather intervened. Treating that score as a finished innings would systematically understate what the batter would have made. Cricket's answer, unchanged since the nineteenth century, is to throw the incomplete innings out of the denominator while keeping its runs in the numerator. That is a deliberately generous convention, and it is why the average always sits at or above runs-per-innings, never below.

Statisticians call the not-out score right-censored: the true finished score is known only to be at least the recorded value. Kimber and Hansford's 1993 paper in the Journal of the Royal Statistical Society treated batting scores with survival-analysis machinery for exactly this reason, and later authors proposed product-limit and Bayesian corrections. This calculator does not implement any of them, and deliberately so: no governing body, record book or ranking system has adopted a corrected average, so a page that silently returned a different number from the one in the scorecard would be wrong in the only sense that matters to a user.

The two inverse modes are algebra on the same line. Solving for runs gives R = Ave × (I − N): to average 50 across 28 dismissals you need 1,400 runs. Solving for dismissals gives d = R ÷ Ave: 1,248 runs sustain an average of 40 across 31.2 dismissals, so the thirty-second time you are out, the average has dipped below 40. That fractional answer is meaningful even though a fraction of a dismissal is not — it is the point on the axis at which the line is crossed.

One edge case is genuinely undefined rather than merely awkward. If N = I, then d = 0 and the average is R ÷ 0. Scorecards print a dash. This calculator raises an error rather than returning infinity, because a page that showed '∞' next to a batter who is 12 not out in their only innings would be reporting a fact about arithmetic rather than a fact about cricket.

A worked example.

Example

A middle-order batter finishes a long season with 1,248 runs from 34 innings, six of them not out. Dismissals are 34 − 6 = 28, so the batting average is 1,248 ÷ 28 = 44.5714285714, printed as 44.57. Now compute the same season the wrong way, dividing by innings: 1,248 ÷ 34 = 36.7058823529, or 36.71 runs per innings. The two figures differ by 7.87 runs — a 21.4% inflation — and every point of that gap comes from six innings in which the batter was still at the crease when the innings closed. The not-out rate is 6 ÷ 34 = 17.6470588235%, high enough to flag the average for a second look: a number six or seven who is regularly stranded on 30-odd when the innings ends will bank an average well above their true scoring rate, while an opener with the same aggregate and one not out would average 1,248 ÷ 33 = 37.82. Switch the calculator to 'Runs needed' with a target of 50 and it returns 50 × 28 = 1,400 runs — 152 more than this batter managed across the same 28 dismissals, or about five and a half extra innings at their current rate. Switch to 'Dismissals affordable' with a target average of 40 and the same 1,248 runs and it returns 31.2 dismissals: this batter can be out three more times and still be averaging 40, but the thirty-second dismissal takes them below it.

not Outs6
innings34
total Runs1,248
target Average50
solve Foraverage

Frequently asked questions.

How do you calculate a batting average in cricket?
Divide total runs by the number of times you have been out: Average = Runs ÷ (Innings − Not outs). If you scored 1,248 runs in 34 innings with 6 not outs, the denominator is 28 dismissals and the average is 1,248 ÷ 28 = 44.57. The critical detail is that not-out innings are removed from the denominator but their runs stay in the numerator, which is why a cricket average is always at least as large as the batter's runs-per-innings and usually larger.
Why are not outs excluded from the batting average?
Because a not-out innings is an unfinished measurement. The batter was still scoring when the innings ended for a reason outside their control — the last partner was dismissed, the target was reached, the captain declared, the overs ran out, or rain ended play. Counting that score as a completed innings would understate what the batter would have gone on to make. Statisticians call this a right-censored observation: the true finished score is known only to be at least the recorded value. Cricket's convention, unchanged for more than a century, is to leave the runs in the numerator and drop the innings from the denominator.
How is a cricket batting average different from a baseball batting average?
They share a name and nothing else. A baseball batting average is hits ÷ at-bats — a proportion between .000 and 1.000 where .300 is an excellent season. A cricket batting average is runs ÷ dismissals — an unbounded runs-per-out figure where 40 is a strong career, 50 marks a great, and the all-time Test record is 99.94. The numerators measure different things (runs versus hits), the denominators measure different things (dismissals versus plate appearances that end in a hit, out, or error), and the scales do not overlap. There is no conversion between them. Quanta keeps a separate baseball batting average calculator for the hits ÷ at-bats formula.
What happens to the average if a batter retires?
It depends on which retirement the Laws of Cricket record. Under MCC Law 25.4.2, a batter who retires because of 'illness, injury or any other unavoidable cause' and does not resume is recorded as 'Retired – not out', which goes into the not-out column and adds no dismissal. Under Law 25.4.3, a batter who retires for any other reason and does not resume is recorded as 'Retired – out'. That counts as a dismissal in the denominator, even though no bowler is credited with a wicket and no fielder with a catch. Two rows that look identical on a scorecard therefore have opposite effects on the average.
What is a good batting average in cricket?
It depends entirely on format, era and batting position, so treat any single threshold with suspicion. In the longest formats an average above 50 has traditionally marked a batter as world class, 40 is a strong professional career, and 30 is respectable for a lower-middle-order player. In one-day cricket, averages are compressed by the batting position and the need to accelerate, so a top-order average in the 40s is very strong. In T20 the average becomes close to uninformative on its own, because the batter's job is runs per ball rather than runs per dismissal — a batter averaging 25 at a strike rate of 160 can be worth far more than one averaging 40 at 110. Always read the average alongside the strike rate and the not-out rate.
Should I count innings where the batter did not bat?
No. An innings is only counted if the batter went to the crease. A player who is in the eleven but whose side is bowled out before they are needed, or whose side wins with wickets in hand, has not batted and that match adds nothing to either the innings count or the not-out count. Getting this wrong is the single most common cause of a mismatched average: adding phantom innings inflates the denominator through the not-out column, deflating the calculated average against the official record.
Do byes, leg byes and wides count toward a batter's runs?
No. Under MCC Law 23, byes and leg byes are credited to the batting side, not to the striker, so they never enter the numerator of a batting average. Wides are credited to the batting side as extras and are debited to the bowler under Law 22.7, again never reaching the batter's column. Runs the striker actually scores off a no ball do count toward the batter, while the one-run no-ball penalty itself is an extra debited to the bowler under Law 21.16. In practice: use the number printed against the batter's name on the scorecard, which already applies all of these rules.
Can a batting average be undefined?
Yes. If every innings a batter has played ended not out, there have been zero dismissals and the average is runs ÷ 0, which is undefined. Scorecards and record books print a dash rather than a number in that case. This calculator raises an error instead of returning infinity, because reporting '∞' would be describing arithmetic rather than cricket. As soon as the batter is dismissed once, the average becomes defined — and starts very high, because the entire aggregate is divided by one.
Is the batting average a fair measure when a batter has many not outs?
It is fair by the sport's own convention, but it is easy to misread. A high not-out rate mechanically lifts the average relative to runs per innings, and batting position is the main driver: finishers and lower-middle-order players in limited-overs cricket are stranded unbeaten far more often than openers. The academic literature has proposed corrections — survival-analysis and product-limit estimators that treat a not-out score as a lower bound on the finished score — but none has been adopted by the ICC or the record books. The practical answer is to read the not-out rate this calculator returns alongside the average, and to compare the average with the runs-per-innings figure: if the two are close, the average is almost pure scoring; if they diverge sharply, a good part of the average is survival.
Does the batting average tell you anything about scoring speed?
Nothing at all. The average has dismissals in the denominator, not balls or overs, so a batter who makes 60 from 200 balls and one who makes 60 from 40 balls contribute identically to it. Scoring speed is measured by the batting strike rate, runs per 100 balls faced, defined in the sports-science literature as SR = 100R/B. In Test cricket the average dominates selection arguments; in T20 the strike rate usually does; in one-day cricket both matter and are normally quoted together. Use Quanta's cricket batting strike rate calculator for the speed half of the picture.

References& sources.

  1. [1]International Cricket Council — 'About ICC Rankings'. Explaining how a team rating is formed, the ICC writes that it "can be compared with a batting average, but with points instead of total runs scored and a match/series total instead of number of times dismissed" — the governing body's own statement that the denominator of a batting average is times dismissed, not innings played.
  2. [2]Lemmer, H. H. (2011). 'The single match approach to strike rate adjustments in batting performance measures in cricket.' Journal of Sports Science & Medicine, 10(4), 630–634. Open access. Defines the two measures used across this cluster in symbols: "AVE = R/out where R is the total number of runs scored and 'out' the number of times the batsman was out", and "SR = 100 R/B with B the total number of balls the batsman faced".
  3. [3]Marylebone Cricket Club — Laws of Cricket, Law 25 (Batter's innings; Runners). Law 25.4.2: a batter who retires through "illness, injury or any other unavoidable cause" and does not resume "is to be recorded as 'Retired – not out'". Law 25.4.3: a batter who retires for any other reason and does not resume "is to be recorded as 'Retired – out'" — the rule that decides whether a retirement enters the dismissals denominator.
  4. [4]Marylebone Cricket Club — Laws of Cricket, Law 18 (Scoring runs). Law 18.1.1 defines a run as scored "so often as the batter, at any time while the ball is in play, have crossed and made good their ground from end to end", with boundaries and penalty runs added under 18.1.2 and 18.1.3. This is the numerator of the batting average.
  5. [5]Marylebone Cricket Club — Laws of Cricket, Law 23 (Bye and Leg bye). Runs completed from a delivery that passes the striker without touching bat or person "shall be credited as Byes to the batting side", and leg byes likewise go to the side rather than the striker — which is why extras never enter a batter's run aggregate.
  6. [6]International Cricket Council — ICC Men's One-Day International Playing Conditions, effective from July 2025 (PDF). Clause 13.6.1 limits each innings to a maximum of 50 overs and clause 13.9.1 limits a bowler to 10 overs, the structural facts that shape how often a batter is left not out in the format.
  7. [7]International Cricket Council — Playing Conditions index, listing the current Test, ODI and T20I playing conditions for men's and women's international cricket with their effective dates.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 590 calculators remain free
  • No billing is enabled
Coming soon