The Mullanpur Ledger: India's Four Overs, West Indies' Two — and Cricket's Unwritten Clock

The floodlights at Mullanpur were still on, but the shadows on the grass had grown long. The galleries of the Maharaja Yadavindra Singh International Cricket Stadium were emptying, and the scoreboard held a single number — 352/6, 48.2 overs. West Indies had taken the match with ten balls to spare. My twenty-odd years of watching cricket have stored many such chases, but if this match had reached the white bedsheet screen I strung up at Shibbari Mor in Khulna in June 2026, in front of two hundred people, the scene would have been identical: a father lifting his child onto his shoulders, a paper cone of fried snacks in one hand, someone gripping a table and saying, “Thirteen balls were left — how?” The information that arrived after the match was written nowhere on that scoreboard. India bowled four overs short. West Indies bowled two overs short. The night's biggest story was not on the scoreboard but in the match referee's ledger.

The news itself is small, cold and administrative. After the third and final ODI of the series, the ICC sanctioned both teams for a slow over-rate under Article 2.22 of the Code of Conduct. The penalty is five percent of the match fee for every over a side falls behind the scheduled time. The arithmetic is simple: India bowled four overs short, so twenty percent of the match fee was deducted. West Indies bowled two overs short, so ten percent. Match referee Prakash Bhatt brought the charges; on-field umpires Jayaraman Madanagopal and Sam Nogajski, third umpire Sharfuddoula and fourth umpire Virender Sharma complete the chain. Captains Shubman Gill and Shai Hope accepted the sanction without requesting a hearing. Administratively, this is a clean close: clear rule, clear arithmetic, no controversy.

One point deserves separation, because the habit of blurring formats in cricket discussion is contagious. This sanction belongs to the fifty-over format, not to T20Is, not to Tests. Of the three formats, the ODI carries the highest over-rate risk, because each innings uses two new balls, spin changes arrive mid-innings, and DRS reviews stop play repeatedly. Next comes a five-match T20I series, starting in Lucknow on Tuesday, October 6 — an entirely separate context, because T20Is have fewer overs, move faster, and generate far fewer over-rate problems. Mixing conclusions across the two formats means misdiagnosing the disease.

The most honest ledger in cricket is the match-fee ledger, because there delay and profit sit on the same page. I checked the Article 2.22 arithmetic myself: India four overs behind, therefore twenty percent; West Indies two overs behind, therefore ten percent. The fine did not depend on a judge's mood; it emerged from the rule's own arithmetic. That matters, because slow over-rate usually draws two complaints — “it is the referee's whim” and “it is a conspiracy against our team.” Neither survives here. Yet an uncomfortable question hides inside this transparent arithmetic.

Here it is: how did India bowl four overs short in a match that ended before the scheduled fifty overs were complete? West Indies finished the chase in 48.2 overs, meaning ten balls remained unused. There was no persistent rain, no DLS, no broken innings. The four-over shortfall, then, is not a by-product of a long match but a failure of time management. In my experience, that is the real signal. Delay is natural in a long innings; but delay in a short match means repeated small stoppages — DRS conversations, field changes, clusters of bowling changes, injury checks, words exchanged. Four overs in one match means the time of twenty-four deliveries; that does not accumulate in one block, it accumulates drop by drop.

Still, turning this failure purely into a story about India's discipline would be wrong, because the ODI format is itself a trap. Two new balls mean two different types of bowler at two ends, and a switch of bowling ends every ten overs. When spinners arrive in the middle overs, the captain spends time on field placement. Add DRS — every review means a stopped clock, two minutes of discussion, a wait for the big screen. A seven-hundred-run match on a flat wicket means four hundred deliveries of travel, boundary retrievals, stretchers, water. Taken together, the ODI clock never runs easily. The question is why the burden of this structural risk falls entirely on the captain's shoulders.

On top of that sits a counter-intuitive argument. Home sides are usually the most disciplined on over-rate — familiar conditions, familiar umpires, familiar routines — yet here the larger offence belonged to India, at home, at the centre of its own format expertise. The visitors stopped at two overs; the hosts at four. India's 350-plus total means the batting was excellent, but the bowling phase lacked the same continuity — repeated field changes, hesitation in bowler selection. To me this is a small but clean blow to the idea that an elite side is automatically a disciplined one.

The second signal matters more than India's. This is West Indies' second slow over-rate sanction in three months — five percent against New Zealand in July, ten percent now. Two incidents do not yet amount to a “culture,” but they do suggest a pattern: over-rate control is a structural weakness in Caribbean ODI bowling management. The likely causes could be inexperienced bowling leadership, a thin pace attack that demands frequent changes, or restlessness in tactical consultation. India's previous sanction, by contrast, was ten percent in the Raipur ODI against South Africa in December 2026. So for Gill, this is a first significant blemish, on home soil.

Look at the West Indies team and another layer opens. This is not a single-country side — Guyana, Trinidad, Barbados, Jamaica, Saint Lucia; separate passports, separate boards, separate schedules. Assembling bowlers out of the busy Caribbean Premier League calendar, flights from island to island, organising practice sessions — that is administrative labour. Every border I crossed taught me a new way to draw the line; the Caribbean line is drawn through passports, flights and board politics. A repeat over-rate offence may therefore be not only negligence but structural pressure — though the cause is not clear from the data of this match, so this remains an inference.

This is where the subject moves, for me, from play to labour. Twenty percent of a match fee is a small number in a headline. But to a player whose income depends largely on match fees and central contracts, it is a monthly household budget. For those grinding through domestic cricket, “a percentage of the match fee” means house rent, a father's medicine, a sister's school fees. Our cricket memory does not retain the arithmetic of fines, because we measure the game in runs, not in debts. In empty stands I learned that silence has a formation — a fines ledger is a kind of silence too, one where nobody writes down the spectator's time. Broadcasters buy matches for fixed slots; when overs run late, the next programme shifts and advertising arithmetic breaks. The spectator buys a ticket, pays for transport, stays up late — and that time is written down nowhere.

When I strung up that white bedsheet at Shibbari Mor in Khulna, I rented a generator, joined the wires, and arranged a single small speaker for two hundred people. The bedsheet screen glowed because hunger made the projector holy. Nobody there kept a ticket account, but everybody knew when the match was supposed to end. When play runs late, the diesel arithmetic of a rented generator breaks, the shopkeeper's evening sales break, the child's sleep breaks. Over-rate is not an abstract administrative concept — it is wired directly into the length of a spectator's night. If the ledger of punishment ever recorded the spectator's time as well, the clock of overs might genuinely run faster.

Now the other side deserves thought, because the easy story is usually the wrong one. The easy story: India were negligent, the captain careless, discipline has collapsed. But a single match's over-rate cannot measure a team's culture of discipline — that is the biggest trap of small samples, and our memory falls straight into it. Nobody counts how many matches India finish on time; one lapse produces a headline. West Indies' two-incident pattern is likewise only two data points. Sanctions of this kind are mainly warnings — a percentage of the match fee is so small that it signals more than it punishes. The real question, then, is not the size of the punishment but its effectiveness.

There is another blank space nobody wants to touch. We treat over-rate as a fragment of news — a three-line item, forgotten by the next day. Yet it is the only cricket rule in which the spectator's time enters the transaction directly. When the game slows, the spectator receives no compensation — no ticket refund, no offset for the broken broadcast slot. Players, meanwhile, are punished in percentages of match fees, teams pay fines, and the account closes. Curiously, in debates about format reform we argue endlessly about bat sizes, field restrictions and impact players, but we never argue about in-match time penalties. If the governance system read the match clock in the language of broadcast contracts, this fragment of news would become the biggest story of all.

A five-match T20I series begins in Lucknow on Tuesday, October 6 — and there this fine will be buried quickly, because the T20I clock runs differently. But the ledger will remain. I write to gather strangers into the same ninety-minute heartbeat, so for me the real question does not stop at the money. The question is this: if a cricket system cannot enter the spectator's ticket price, travel and sleepless night into its accounts, does it have the right to call an over-rate fine a punishment? If the two hundred people who once stood before that white sheet in Khulna ever become the answer to that question, cricket's clock will have to be reset — not only by the umpires, but by us.