In this guide
Convert the display into valid balls firstAn original chase exampleValid balls are the counting unitDo not rebuild official net run rate from one snapshotRead runs, wickets and balls togetherIn an IPL scorecard, 17.4 overs means seventeen completed overs and four valid balls of the next over. It does not mean 17.4 decimal overs. An over contains six valid balls, so the notation uses a ball count after the point.
This distinction matters when working out balls remaining or a simple scoring rate. Treating the displayed number as an ordinary decimal quietly changes the amount of cricket that has been played.
Convert the display into valid balls first
Seventeen completed overs contain 102 valid balls. Add the four represented by .4 and the total becomes 106. To express that in decimal overs for a calculation, divide by six: 106 divided by six is approximately 17.667.
The displayed 17.4 is useful because it preserves the familiar over-and-ball structure. It is not designed for direct entry into an ordinary calculator as a decimal. The same issue appears at 12.1, 18.5 or any other incomplete over.
An original chase example
Imagine a fictional chasing side needing 21 runs after 17.4 overs of an uninterrupted 20-over innings. A full innings contains 120 valid balls. With 106 completed, 14 remain. The simple required rate is 21 divided by 14, or 1.5 runs per ball; multiplying by six gives nine runs per six-ball over.
Subtracting the decimal-looking display from 20 would produce 2.6. Calling that 2.6 ordinary overs would be wrong: the remaining 14 balls equal two complete overs and two balls. This example is arithmetic only and does not predict a match outcome.
| Quantity | Calculation | Result |
|---|---|---|
| Balls completed | 17 × 6 + 4 | 106 |
| Balls remaining | 120 − 106 | 14 |
| Required per six balls | 21 ÷ 14 × 6 | 9 runs |
Valid balls are the counting unit
The playing conditions describe overs in valid balls. A delivery that does not count as a valid ball can add to the score or create an incident without advancing the valid-ball counter in the same way. Keep the scorecard’s official ball count as the basis for this calculation.
That is also why a programme’s elapsed running time cannot reliably be converted into overs. Delays, reviews, wickets and other interruptions can change the clock without supplying the next valid ball.
Do not rebuild official net run rate from one snapshot
The IPL’s net-run-rate rules include specific treatment when a team is all out before using its full allocation. A simple rate from the live overs display is therefore not automatically the team’s official table NRR. The live chase calculation and the season ranking statistic answer different questions.
Use the ball conversion to understand the current innings, then use the published table for the official cumulative statistic. This keeps a helpful piece of arithmetic from becoming an incorrect reconstruction of the competition standings.
Read runs, wickets and balls together
A required rate describes scoring pace, while wickets in hand describe remaining batting resources. Neither guarantees success. Converting the overs correctly gives the discussion a sound denominator and makes the commentary easier to follow when the final few overs arrive.