Key points

  • 19.4 overs means 19 overs and 4 balls, which is 118 balls.
  • Decimal overs are total balls divided by six.
  • Dividing runs by the scoreboard notation overstates the run rate.
  • Converting decimal overs back needs a carry rule at six balls, not ten.
In this guide

A scorecard says a side made 187 in 19.4 overs. A spreadsheet divides 187 by 19.4 and reports 9.64 runs per over. The correct rate is 9.51.

The difference is only 1.3 per cent here. Across a net run rate calculation, a projection or a chase, it is enough to make a correct number wrong.

Base six, not base ten

An over contains six legal deliveries, so the digit after the decimal point in cricket notation counts balls, not tenths. It runs from 0 to 5 and then carries:

Notation Meaning Balls Decimal overs
0.3 3 balls 3 0.500
9.4 9 overs 4 balls 58 9.667
19.4 19 overs 4 balls 118 19.667
50.0 50 completed overs 300 50.000

The notation is a compact way of writing overs and balls. It is not a decimal fraction.

Converting to balls

Balls = (overs × 6) + balls

For 19.4: (19 × 6) + 4 = 118.

Then decimal overs are 118 ÷ 6 = 19.667. A run rate uses decimal overs because it is an average per over:

Run rate = runs ÷ decimal overs

The run rate calculator does this conversion in stages and shows the intermediate ball count, so the notation never becomes a decimal by accident.

Where the mistake appears

Every figure derived from overs inherits the error:

  • Run rate. Dividing 187 by 19.4 gives 9.64 instead of 9.51.
  • Projected totals. The wrong rate projects to 482 over 50 overs instead of 476.
  • Net run rate. If every innings is parsed as a decimal, totals with different ball counts are weighted incorrectly.
  • Required rate. Remaining overs such as 8.3 become 8.3 decimal overs instead of 8.5, making the chase look harder than it is.

The error is not random. Dividing by a smaller denominator than the true workload always inflates the rate.

Converting decimal overs back

Going the other way is rarer but useful when a data source supplies decimal overs. Take 19.667:

  1. Whole overs: 19.
  2. Fractional part: 0.667.
  3. Balls: 0.667 × 6 = 4.002 → 4.
  4. Result: 19.4.

Rounding can produce six balls, which must be carried into the next over. 19.999 decimal overs is 20.0, not 19.6. The safe route is to convert to total balls first, round to the nearest ball, then split into overs and balls:

totalBalls = round(decimalOvers × 6)
overs = floor(totalBalls ÷ 6)
balls = totalBalls mod 6

That is the same function the site uses when it formats a ball count back into notation.

A quick habit

Before dividing, ask: how many balls is that? Multiply the completed overs by six and add the balls. Once the workload is in balls, every rate calculation becomes ordinary division.

It is a small step. It is also the difference between an answer that matches the scorecard and one that only looks plausible.

Use the run rate calculator to check a single innings, or net run rate calculator when you need to aggregate several.

All guides