The 17.3 on Cricinfo That Is Not a Decimal
That tiny dot does not mean seventeen-and-three-tenths overs. It records seventeen completed overs and three valid balls, which is a much better little story.
A live cricket score has one wonderfully stubborn bit of punctuation: the dot after the over count. I think it earns its keep. A reader arriving at a score such as 126-4 after 17.3 can be forgiven for treating it like a decimal, but cricket is not offering seventeen and three-tenths overs. It is saying that seventeen overs are complete and the next over is three valid deliveries old. Once that click happens, a Cricinfo page stops looking coded and starts keeping very tidy time.
Read the dot as an over and a remainder
An over contains six balls. The Marylebone Cricket Club's Law 17 is explicit about that, and it also makes the crucial distinction that only valid balls count toward those six. So 17.0 means seventeen completed overs. Then 17.1 is one valid ball into over eighteen, 17.2 is two, and 17.5 is five. The next valid ball produces 18.0, not 17.6.
| What the score shows | What it means | Valid balls delivered in all |
|---|---|---|
| 17.0 | Seventeen overs are complete | 102 |
| 17.3 | Seventeen overs plus three balls | 105 |
| 17.5 | Seventeen overs plus five balls | 107 |
| 18.0 | Eighteen overs are complete | 108 |
That last column is the useful conversion when you want the real amount of bowling completed. For 17.3, calculate 17 x 6 + 3 = 105 valid balls. If a page says a batter faced 37 balls, that is an ordinary ball count. If it says the innings is at 17.3, it is using the compact over-and-balls shorthand. I checked the current Laws rather than relying on the familiar convention, because this is exactly the sort of small scorecard habit that becomes misleading when repeated loosely.
Why 17.6 never arrives
The tempting decimal sequence would be .1, .2, .3, .4, .5, .6. Cricket declines the sixth decimal-style step because the figure after the dot counts balls already bowled in the current over. After five, the next valid ball completes the six-ball unit and resets the remainder to zero. It is closer to reading 17 minutes and 3 seconds than reading a price tag. The notation looks compact because it is compact, not because it is doing base-ten mathematics.
A ball can change the score without moving the over count
This is the part that makes a live feed feel briefly mischievous. A wide or a no-ball can add runs, yet it is not a valid ball for the six-ball over. MCC's Laws say a no-ball does not count as one of the over, and the same is true of a wide. A score can therefore move from 126-4 at 17.3 to 127-4 at 17.3 after a wide. The run is real. The over notation stays put until the bowler sends down a valid delivery.
The Australia-Bangladesh Test live blog captured the same logic in plain view: it described a no-ball from the sixth delivery and then a dot ball from the seventh. The apparent seventh ball was needed because the no-ball could add to the score but could not finish the over. That is the kind of entry that feels odd only until the notation is doing its job for you.
The score and the pace are separate questions
Once you can read the notation, it becomes easier to ask the right next question. A team on 126-4 at 17.3 has made 126 runs for four wickets after 105 valid balls. In a limited-overs match, you can compare that pace with the innings limit. In a Test, where an innings is not capped at 20 or 50 overs, the number is still useful as a measure of how much of that passage has been played. The England and Wales Cricket Board's beginner guide is a good reminder that Twenty20 and one-day cricket are limited-overs formats, while Test cricket is a different frame entirely.
Do not read too much mood into one number. A quiet 17.3 can follow a wicket, a careful rebuilding phase, a batting surge interrupted by rain, or simply a match at a different stage from the one you expected. The notation tells you where the innings is. The score, wickets, recent ball-by-ball entries and match format tell you what that place means.
Keep deliveries and valid balls in separate little boxes
The word delivery is usefully broader than the number printed after the dot. A bowler can send the ball down, the scorer can record what happened, and the team total can change. The over count advances only when the Law calls that ball valid. That is why an over can contain more physical deliveries than its six-ball shape suggests. Nothing has gone missing from the live page. The count is preserving a distinction that matters to the contest.
This also explains why ball-by-ball commentary is the helpful companion to a compact score. A score tells you 17.3. The sequence underneath can tell you whether that passage included a wide, a no-ball, a wicket, several singles or six quiet balls from an earlier over. I find the pair more useful together than either one alone: the small notation supplies the frame, while the entries give it texture.
A quick way to use it on a live page
- Read the whole number as completed overs.
- Read the number after the dot as valid balls in the current over, from zero through five.
- For a total ball count, multiply the first number by six and add the second.
- If the runs change but the notation does not, look for a wide, a no-ball, or another event that did not count as a valid ball.
- Use the match format before judging whether the rate feels urgent.
I like this little convention because it refuses false neatness. Cricket could have forced the display into decimals, then made everyone convert back to balls whenever the game got interesting. Instead it keeps the six-ball over visible in every score. We get a tiny dot, a quick bit of arithmetic, and the satisfying realization that the scoreboard has been speaking plainly all along.
Sources
Every factual claim above traces to one of these. Links open in a new tab.
