Overs to Balls Converter
Enter overs in cricket notation to get the total number of legal balls.
Cricket overs use "overs.balls" notation, not decimals — "14.3" means 14 complete overs plus 3 balls of the next one. Since every over is 6 legal balls, that's (14 × 6) + 3 = 87 balls in total.
What Is the Overs to Balls Conversion?
Cricket has one quirk that catches out almost everyone doing quick maths from a scorecard: overs look exactly like decimals, but they don't behave like them. When a scorecard shows '14.3 overs,' that's not fourteen-point-three of anything — it's 14 complete overs, plus 3 individual balls of the over currently in progress.
This converter exists purely to remove that ambiguity. Feed it an overs figure in the notation you'd see on any scorecard or in commentary, and it hands back the actual, unambiguous total of legal deliveries that figure represents — the number you'd need if you were doing any further maths, like working out a run rate or an economy rate by hand.
It's a small conversion, but it comes up constantly — anyone checking a bowler's figures against a run rate calculation, cross-referencing ball-by-ball commentary against a final scorecard, or just double-checking a stat they've seen quoted somewhere will eventually need to turn an overs figure into an exact ball count.
Formula & Worked Examples
Take the whole-number part of the overs figure and multiply it by 6, since a legal over is always 6 balls. Then add whatever digit follows the decimal point, which represents the balls bowled into the current, unfinished over — never a fraction of an over.
Why It Matters
The mistake of treating overs notation as a real decimal is one of the most common errors in amateur cricket analysis, and it's easy to see why — everywhere else in daily life, '.3' means three-tenths. In cricket, it means three balls out of six, which is a completely different fraction (0.5, not 0.3) once you actually convert it.
This matters well beyond idle curiosity. Every rate-based cricket stat — run rate, economy rate, net run rate, required run rate — depends on getting the overs figure right before any division happens. Treat 14.3 as 14.3 in a calculation instead of converting it properly (14.5 as a decimal, or 87 balls), and every downstream number comes out slightly wrong, even though the error looks tiny at first glance.
It's also useful any time you're working from raw delivery data rather than a formatted scorecard — ball-tracking systems, some broadcast graphics, and a lot of scoring software store deliveries as a plain count rather than in overs notation, so converting back and forth between the two formats comes up constantly for anyone building or checking cricket statistics.
Common Mistakes to Avoid
- Treating the number after the decimal point as a fraction of an over instead of a count of balls — '.3' is 3 balls (half an over), not 0.3 of an over.
- Writing or reading a figure like '14.6' or '9.7' as valid overs notation — since an over only ever has 6 balls, the number after the decimal should never exceed 5.
- Forgetting that wides and no-balls don't count toward the over, so the balls total from this converter reflects legal deliveries only, not every ball actually bowled.
- Mixing up overs bowled with overs remaining when doing run-rate calculations — the two numbers look similar but represent opposite things.
- Rounding an overs figure before converting it, which can silently shift the ball count by several deliveries if done carelessly.
Related Calculators
Frequently Asked Questions
Why doesn't 14.3 overs equal 14.3 in normal decimal terms?
Because an over is a fixed unit of exactly 6 legal balls, not 10 — the number after the decimal point in cricket's overs notation always represents balls out of six, never tenths of an over.
Is 20.0 overs the same as 20 overs?
Yes — a zero after the decimal point just means no partial over has been bowled yet; the innings or spell has completed exactly 20 full overs.
What does an overs figure like 9.7 mean?
Nothing valid in standard notation — since every over only has 6 balls, anything after the decimal point should be 0 through 5. A figure like 9.7 would actually represent 10.1 overs.
Does this converter count wides and no-balls as part of the total?
No — it converts legal-delivery overs into legal-delivery balls. Wides and no-balls are recorded separately and don't count toward completing an over.
Why would I need to convert overs to balls instead of just using overs directly?
Balls are the more precise unit for any calculation involving partial overs, since dividing by an overs figure like 9.4 directly, instead of its true decimal value or working in balls, gives you a slightly wrong answer every time.
Does the format of the match change how overs are converted to balls?
No — six balls make an over in every format, from Test cricket to T20s. The only thing that changes between formats is how many overs make up an innings, not the definition of an over itself.