Cricket batting average calculator: runs per dismissal

Combine records by runs and dismissals, not by averages

Suppose a player makes one hundred runs with two dismissals in one period and three hundred with ten dismissals in another. The separate averages are fifty and thirty. Their simple mean is forty, but the combined average is 400 ÷ 12, about 33.33. Equal weighting of the two periods would overstate the influence of the smaller dismissal sample.

Keep each innings’ runs and official status so the totals can be checked. A not-out innings adds runs but no dismissal. An innings dismissed for zero adds no runs but still adds a dismissal. A did-not-bat entry is not a zero-run dismissal, and a local retirement convention needs its actual recorded treatment.

If all included appearances are not out, there is no ordinary finite average because the denominator is zero. Show the runs and status honestly rather than dividing by appearances or inventing a dismissal to make the tool return a number. For comparisons, list innings and dismissals alongside the average: a high figure with very few dismissals does not carry the same descriptive weight as a long record. The average summarises that selected record; it is not the player’s most likely score next time.

Formula and input check

Keep the dismissal count alongside the average. A player with 100 runs and three dismissals has an average of 33.333… before display rounding. Multiplying the displayed 33.33 by three gives 99.99, not the original 100. The scorebook inputs preserve the exact record; the rounded average is a readable summary, not a replacement for those inputs.

Not-outs example: find the correct denominator

The player has 130 runs and three dismissals. The average is 130 ÷ 3 = 43.33 to two decimal places. Dividing by the five appearances would give 26.00, which is runs per innings appearance rather than the conventional batting average. The zero-score dismissal still counts in the denominator.

Prepare the right totals

Add runs from the innings in the selected record. Count only innings in which the player actually batted when using an innings total, and identify not-out entries accurately. A did-not-bat entry is not an innings with a score of zero. Retirement status may require checking the official record and competition conditions.

Use dismissals as the denominator

If the tool asks for innings and not outs, dismissals = innings batted − not-out innings. Batting average = total runs ÷ dismissals. If there have been no dismissals, the ordinary average is undefined rather than zero or an invented large number. The record can show runs and not outs without forcing a numerical average.

Recalculate after a dismissal-status correction

A record of 200 runs with five dismissals gives an average of 40.00. Suppose an included innings was marked not out in the working file but the verified scorecard shows that the batter was dismissed. The runs remain 200, while dismissals become six and the corrected average is about 33.33. Correct the innings row first, then regenerate the totals. Editing only the final average leaves a contradiction that will return at the next update. Keep the original match reference with the corrected row so the status can be checked without guessing from the rounded season figure.

Does a duck count as a dismissal?

If the player is dismissed for zero, it contributes one dismissal and no runs. A not-out score of zero contributes neither runs nor a dismissal. That difference can change the average even when the runs column looks identical. Read the dismissal status rather than inferring it from the number alone.

What if a player has only not-out innings?

With no dismissals, division by zero is undefined. Do not report an average of zero because the player has not failed, and do not invent infinity as a normal performance figure. Display the runs, innings and not outs and explain why a conventional average is not yet available.

Can this compare openers with finishers?

The arithmetic is the same, but roles create different opportunities and not-out patterns. Match situation, innings length and format matter when interpreting the result. Use average alongside strike rate and a clear description of the sample instead of declaring one player better from this ratio alone.

Import a score such as 27* without losing its status

Keep the score and innings status in separate fields. For an entry of 27*, store twenty-seven runs and a not-out status; do not let a spreadsheet turn the whole cell into missing text because it contains an asterisk. For a dismissed zero, store zero runs and one dismissal. For did not bat, leave the batting innings absent rather than adding a dismissed zero. Check imported rows against the original scorecard before calculating totals. This matters when a file mixes dashes, blanks, asterisks and written retirement descriptions: visually similar cells may describe different events, so a single automatic replacement rule can corrupt the denominator.

A worked example across three innings

A player makes 45 out, 20 not out and five out. Total runs are seventy, innings batted are three and dismissals are two. The batting average is 35.00, while runs per innings are about 23.33. Both figures can be calculated, but they must have different labels. If the next appearance is did not bat, neither the run total nor the dismissal count changes. If the next innings is a dismissed zero, the total remains seventy while dismissals become three, reducing the conventional batting average.

Avoid reading average as the most likely next score

An average summarises a selected history of runs and dismissals. It is not a forecast that the next innings will end near that number, nor does it describe the distribution of scores. A record made of a few high scores and many low ones can have the same average as a steadier record. Use the actual innings list if that pattern matters. The calculator does not adjust for opposition, surface, role or innings state, so it should not be promoted as a complete measure of batting quality from one number.