Balls to Overs Converter
Enter a total number of legal balls to get the equivalent in cricket overs notation.
Divide total balls by 6 for the whole overs, and whatever's left over becomes the balls part in cricket notation. So 87 balls is 14 full overs with 3 balls left — written as 14.3, not 14.5.
What Is the Balls to Overs Conversion?
This converter runs the overs-to-balls logic in reverse. Instead of starting with a scorecard-style overs figure, you start with a plain count of legal deliveries — the kind of raw number you'd get from ball-tracking data or a database that logs every ball individually — and convert it into the overs.balls notation that scorecards, commentary, and cricket analysis actually use.
It sounds like a trivial bit of arithmetic, and in one sense it is, but it's also one of the easiest places to introduce a subtle error if you do the division the way you'd normally divide two numbers, rather than accounting for cricket's six-ball over.
You'll usually reach for this conversion after the fact, once a spell or innings is already over and you're working backward from a delivery count rather than watching the overs tick up live — which is exactly when the temptation to just divide normally and round the answer sneaks in.
Formula & Worked Examples
Divide the total number of balls by 6. The whole number that comes out is the number of complete overs. Whatever remains — always somewhere between 0 and 5 — becomes the digit after the decimal point in the overs notation, representing balls bowled into the next, unfinished over.
Why It Matters
The most common way this conversion goes wrong is treating the remainder as if it belongs after a normal decimal point — dividing 87 by 6 on a calculator gives 14.5, and it's tempting to just write that down as '14.5 overs.' But 14.5 overs in cricket notation would mean 14 overs and 5 balls, which is 89 balls, not 87. The actual answer, 14.3, only comes from working with the remainder directly rather than trusting the calculator's decimal output.
This distinction becomes especially important with any data pipeline or spreadsheet built around raw ball counts, since a single misconverted figure can throw off every derived statistic downstream of it — run rates, economy rates, required run rates, you name it. Getting the conversion right at the source avoids having to hunt down where an error crept in three calculations later.
It's also just the more natural way most fans and commentators actually think and talk about an innings. Nobody describes a spell as '14.5 overs' in conversation — they say '14 and 3,' or just '14.3' — because that's the format the sport has settled on, however unintuitive it looks to anyone doing the maths in their head for the first time.
Common Mistakes to Avoid
- Trusting a calculator's raw decimal output (like 14.5) instead of working out the actual remainder (3) when converting balls to overs.
- Forgetting that a remainder of exactly 6 is impossible if the division was done correctly — it should always land between 0 and 5, since 6 balls would simply be one more complete over.
- Applying this conversion to a count that already includes wides or no-balls, which will overstate the overs figure since those deliveries don't count toward a completed over.
- Rounding the balls total before converting, which can shift the resulting overs figure by a full ball or more.
- Assuming the overs notation works like a percentage or a normal fraction anywhere else in a calculation — it's specific to cricket and shouldn't be reused in unrelated maths.
Related Calculators
Frequently Asked Questions
Why isn't 87 balls equal to 14.5 overs?
Because an over is 6 balls, not 10 — dividing 87 by 6 gives 14 remainder 3, so the correct cricket notation is 14.3, not the raw decimal result you'd get from a plain calculator division.
What does a remainder of 0 mean?
It means the balls total divides evenly into complete overs, with no partial over in progress — the notation ends in '.0', like 20.0 overs.
Can the balls-part of the notation ever be 6 or higher?
No — if it reaches 6, that's actually one more complete over, so it resets to 0 and the whole-overs count increases by one instead.
Does this conversion include wides and no-balls in the ball count?
It shouldn't — this conversion is meant for legal deliveries only, matching how overs are recorded on a scorecard. Including illegal deliveries will overstate the resulting overs figure.
Where does this conversion actually get used?
Most often when working from ball-by-ball data feeds, scoring apps, or databases that log deliveries individually rather than in the overs.balls format cricket normally uses.
Is this conversion the same across every format of the game?
Yes — six balls always make an over, whether the match is a Test, an ODI, or a T20. Only the total number of overs allowed per innings changes between formats, not the definition of an over itself.