Overs to Balls Converter

Convert cricket over notation to total balls, decimal overs & more

How to Use
1

Enter the overs in cricket notation (e.g., 12.4 = 12 complete overs and 4 balls in the 13th over).

2

Click Convert to see total balls, decimal overs, and remaining balls in the current over.

Total Balls = (Complete Overs × 6) + Partial Balls

Example: 12.4 overs → 76 total balls, 12.67 decimal overs, 2 balls remaining.

Cricket Over Notation — Quick Reference

Cricket uses a unique notation for overs that can confuse newcomers. The number before the decimal point is complete overs bowled. The number after the decimal point is the additional balls bowled in the current (incomplete) over. There are 6 balls per over, so the digit after the decimal must always be 0–5.

Cricket NotationComplete OversExtra BallsTotal BallsDecimal Overs
5.050305.00
8.383518.50
12.41247612.67
20.020012020.00
45.445427445.67
50.050030050.00

Common mistake: 8.6 is NOT valid — an over only has 6 balls (0–5). 8.6 would actually be written as 9.0 (a new complete over).

Why Does Cricket Use Dot Notation for Overs?

Cricket's over notation evolved from traditional scorebook recording, where scorers needed a compact way to indicate both the complete overs and the current delivery count. The dot notation (e.g., 14.3) is now universal across all cricket formats and broadcast graphics worldwide.

The notation causes frequent confusion because 8.3 does NOT equal 8.3 in decimal mathematics. In cricket, 8.3 = 8 complete overs + 3 balls = 8.5 decimal overs. This is why all cricket calculators — including economy rate and run rate calculators — must convert from cricket notation to decimal overs before performing any division.

This converter also shows remaining balls in the current over, which is useful for planning bowling changes, powerplay decisions, and DLS resource calculations.

FAQ

Overs to Balls FAQs

There are 6 legal deliveries in a cricket over. Wides and no-balls are not counted among the 6 legal deliveries and must be rebowled — so an over can contain more than 6 actual balls bowled if there are extras. However, for scoring and over-counting purposes, only 6 legal balls complete an over.

Total Balls = (Complete Overs × 6) + Partial Balls. For example: 12.4 overs → (12 × 6) + 4 = 72 + 4 = 76 balls. For a T20 complete innings: 20.0 overs → 20 × 6 = 120 balls. For an ODI complete innings: 50.0 overs → 50 × 6 = 300 balls.

12.4 overs means 12 complete overs have been bowled plus 4 additional legal deliveries in the 13th over. It equals 76 total balls bowled. The team is currently in the 13th over with 2 balls remaining before it's complete (since 4 + 2 = 6). In decimal form, 12.4 cricket overs = 12.67 decimal overs (12 + 4/6).

Because an over only has 6 balls — numbered 1 through 6 (or 0 through 5 in the notation after the decimal). After the 6th ball, the over is complete. 8.6 would actually mean 9.0 — a new complete over. Valid notations are 8.0, 8.1, 8.2, 8.3, 8.4, and 8.5, but 8.6 does not exist in cricket notation.

To convert balls to cricket notation: divide the total balls by 6. The quotient is complete overs, the remainder is extra balls. For example, 76 balls ÷ 6 = 12 remainder 4, so 76 balls = 12.4 overs. For 120 balls: 120 ÷ 6 = 20 remainder 0, so 120 balls = 20.0 overs (a complete T20 innings).

DLS resource tables are indexed by overs remaining, which must be a decimal number. Converting cricket notation to decimal overs (e.g., 8.3 → 8.5 decimal) is a required step before looking up DLS resource percentages. This converter handles that conversion instantly, and all our other calculators perform this conversion automatically when you enter cricket-notation overs.

In a full T20 match: 20 overs × 6 balls × 2 innings = 240 balls total (excluding extras that add deliveries). In a full ODI: 50 overs × 6 balls × 2 innings = 600 balls total. In a Test match (5 days, unlimited overs): potentially 5 days × ~90 overs/day × 6 balls × 2 innings, though Tests vary enormously based on conditions and results.

No. All calculations run entirely in your browser using JavaScript. No data is sent to any server, stored, or tracked. No cookies, no analytics, no accounts required.