Overs to balls converter: cricket notation in both directions

Validate imported over notation before doing arithmetic

A spreadsheet may display twelve complete overs as 12, while another source preserves 12.0. Both can represent the same legal-ball count. An entry of 12.6, however, is not ordinary completed-overs-plus-balls notation: one more legal delivery after 12.5 becomes 13.0. Correct or clarify the source rather than silently accepting an invalid remainder.

A true decimal-over column is a different format. The mathematical value 7.5 decimal overs represents forty-five legal balls in a six-ball system, whereas the cricket string 7.5 represents forty-seven. The converter cannot resolve an unlabeled column merely by noticing a dot. Identify the storage convention first.

For reliable records, keep two fields: an integer legal-ball count for calculation and a formatted overs string for display. Add or subtract the integer values, then reconstruct complete overs and the zero-to-five remainder. For example, spells of 4.2 and 3.5 contain twenty-six and twenty-three balls; their forty-nine-ball sum is 8.1. Retaining those source spell strings alongside the count makes an import mistake easier to trace than repeatedly converting rounded decimal totals. Historical or local over lengths must be treated under their own stated basis.

Formula and input check

This conversion is exact for the stated six-ball system: forty-seven legal balls become 7.5 overs, and 7.5 converts back to forty-seven. No rounding is needed. Preserve the remainder as a ball digit rather than displaying 7.83 and then reinterpreting that decimal as cricket notation. The latter would silently replace one unit convention with another.

Convert overs to balls

Multiply the complete overs by six, then add the ball digit. For 31.4 overs, calculate 31 × 6 + 4 = 190 legal balls. The part after the dot must be from zero to five. An entry such as 12.7 is not valid standard overs notation and should be corrected rather than treated as a fraction.

Convert balls to overs

Divide the whole-number ball total by six. The quotient gives complete overs and the remainder gives the ball digit. For 47 balls, there are seven complete overs with five balls left, written 7.5. This is different from the mathematical decimal 7.8333 overs, which may be useful internally for arithmetic but is not the usual scorecard notation.

Distinguish legal balls from deliveries

A wide or no ball normally does not consume one of the six legal deliveries. The number of times a bowler released the ball may therefore exceed the legal-ball total. The converter only changes representation; it cannot infer scoring calls from a raw count of physical deliveries.

Why is 19.6 not the next score after 19.5?

One more legal ball completes the over, so the notation becomes 20.0. Six is carried into the complete-over count rather than retained as a ball digit. This makes the scorecard system resemble a mixed-unit label, much as minutes and seconds use a separate remainder instead of ordinary decimal fractions.

Can the converter be used for historical eight-ball overs?

This site’s standard conversion uses six legal balls per over. Historical and local formats can have different conventions, so do not apply it blindly to an eight-ball-over record. Use the appropriate balls-per-over basis when analysing such a match and label that basis clearly.

How should I use converted balls in formulas?

For run rate and economy, multiplying runs by six and dividing by legal balls avoids a notation mistake. For bowling strike rate, legal balls are already the required unit. Retain the full integer ball count until the final calculation, then round only the displayed ratio.

Subtract the used balls to find an innings allowance

For an ordinary twenty-over allowance, start with 120 legal balls. At 17.4 overs, 106 have been used, leaving fourteen. Convert fourteen back to overs notation and the remaining allowance is 2.2, not the decimal subtraction 20.0 − 17.4 = 2.6. The converter handles one representation at a time: convert the completed overs to balls, subtract that count from the allowance, then convert the remaining integer if an overs display is useful. This approach also makes it clear when the completed count exceeds the stated allowance and an input or match-state check is needed.

A worked example of adding several spells

A bowler’s spells of 4.2, 3.5 and 2.4 contain twenty-six, twenty-three and sixteen legal balls. The total is sixty-five, written 10.5 overs. Adding the displayed values as ordinary decimals would not preserve the six-ball carrying rule. Keep the integer total as the calculation value and create the overs string only for display. This method remains reliable as more spells are added, and it makes later economy or strike-rate calculations straightforward because the needed ball count is already available without another conversion.

A whole-number ball count cannot have a fractional remainder

Standard conversion expects a non-negative whole number of legal balls. An input such as 47.5 balls is not a conventional ball count and should be corrected. Similarly, negative overs or an unexplained extra digit after the ball part needs clarification. Validation is part of an accurate converter, not an inconvenience. If a data source stores a true decimal number of overs instead of cricket notation, identify that format before conversion. The same text, such as 7.5, can mean different quantities under different storage conventions.

Find the duration between two mid-over checkpoints

Suppose a practice passage begins at 6.4 overs and ends at 9.1. The checkpoints represent forty and fifty-five legal balls, so the passage lasted fifteen balls, written 2.3 overs. Subtracting the displayed strings as decimals would give 2.7, an invalid ball remainder. Use a defined start and end before counting a partnership window, bowling passage or scoring phase. If an event at the first checkpoint is already included in its cumulative count, do not count it again. The difference between two cumulative legal-ball totals measures deliveries completed after the first checkpoint through the second one.