Mullanpur ODI: India Fined 20%, West Indies 10% for Slow Over-Rate

I watched the match on a phone screen from a tea stall in Dhaka. The stream ran about three seconds behind — the people around me roared before the bowler had even released the ball, and I was still waiting for that delivery to reach my screen. At Mullanpur the ball was settling behind the stumps, and out of the West Indies dugout rose that sound: a chase of 352 completed, with ten balls to spare. On the screen: 352/6, over 48.2. My cup of tea had gone cold long before.

But the news that left the deepest mark on me that night was not written on the scoreboard. It was an empty space — the arithmetic of four overs. The match ended early, yet India's overs did not. I sat with that small inconsistency for a long while, and I understood something: cricket's strangest ledger is not kept on the field, it is kept on a clock.

It happened at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, in the third and final ODI of the India–West Indies series. More than seven hundred runs between the two sides — a pitch comfortable for batters and merely laborious for bowlers. India posted a total beyond 350, and West Indies chased it down in 48.2 overs. Applause, handshakes, the usual drift off the field.

Then came the paper. Under Article 2.22 of the ICC Code of Conduct, a team that fails to bowl its overs in the allotted time is fined five percent of its match fee for every over short. The arithmetic is ruthlessly simple. India bowled four overs short — 4 × 5% = 20%. West Indies bowled two overs short — 2 × 5% = 10%. Both captains, Shubman Gill and Shai Hope, accepted the sanction; no formal hearing was needed.

Match referee Prakash Bhatt imposed the penalties. The on-field umpires were Jayaraman Madanagopal and Sam Nogajski, with Sharfuddoula as third umpire and Virender Sharma as fourth. The charges came from the on-field umpires, the ruling from the referee — a clean process, no complications.

One thing needs to be made clear here: this is ODI cricket, not Test or T20. The ODI carries its own structural over-rate risk — two new balls, mid-innings spin changes, and long DRS review pauses. Together these three things make the ODI the slowest-moving of the three formats.

Let me say one thing first, which my twenty-four years of watching matches from the ground have taught me to believe firmly: a slow over-rate fine is not a skill metric, it is a captaincy-accountability metric. How hard the ball was bowled, how high the bat was raised — none of that has any bearing on this sanction. It bears only on one question: who wasted the time, and why?

Time was wasted in this match, that much is clear. But the most striking fact is this — the match finished early, and India still bowled four overs short. West Indies completed the chase in 48.2 overs, meaning ten balls remained. If a match ends before its allotted time, common sense says there should be no over-rate problem. Yet the problem is here — the delay did not come from the length of the match, it came from the stopping and starting. DRS reviews, injury checks, bowling-change conferences, field-reset huddles — these small pauses added up into a debt of four overs.

The second thing that caught my eye was the precision of the split. India 20%, West Indies 10% — both figures fall straight out of the rule, no referee's whim involved. The arithmetic of the punishment matches the arithmetic of the rule exactly, and in that match lies the real message: the ICC is trying to say something here, not merely collect money.

Now to the thing few are talking about. West Indies have now been sanctioned for over-rate twice in three months. In July they were fined five percent against New Zealand; this time it is ten. Two samples cannot define a culture — I accept that. But two samples can reveal a pattern, and the pattern is this: there is a recurring problem in West Indies' ODI bowling management, returning like a habit.

And India's side? As the host nation, India was the biggest offender in this match — four overs, twenty percent. This is what astonishes me most. Playing at home usually brings an advantage — umpire tolerance, familiar conditions, your own crowd. If a side still wastes the most time in the match, calling it a mere accident is hard. Shubman Gill is relatively new to full-time ODI captaincy, and this team-level sanction leaves a small mark on his record. Back in December 2026, India were fined ten percent in the Raipur ODI against South Africa — so this is not India's first over-rate episode.

A memory of my own surfaces here. In 2026, covering the Abahani–Mohammedan derby at Bangabandhu Stadium in Dhaka, I learned that the biggest story of a match sometimes hides in the smallest pause. That day I ignored the scoreline for thirty seconds to describe an old man in the gallery wiping his glasses. In exactly that spirit, this over-rate story taught me that beyond what we call the result of a game, there is another ledger that the spectator never sees. The clock is that eleventh player no captain picks, yet it takes the field in every match.

A larger question follows — whose interest does the over-rate sanction really protect? The interest of the game on the field, or the interest of the broadcasters? An ODI must finish within a set time because television slots are fixed in advance. If a match drags, the next programme slips, advertising arithmetic goes haywire. Which means a large part of this sanction is really the clock's commercial ledger, not the game's aesthetic one. I am not blaming the broadcasters by saying this — I am only saying that where the rule is made, off-field arithmetic is present too.

Now to the pitch. Chasing 352 means the surface gave the bowlers almost nothing. And when a pitch turns against the bowlers, play slows down — more time to fetch the ball from the boundary, more time to change bowlers, more time to set fields. The ICC itself knows this structural weakness of the ODI — two new balls, mid-innings spin changes, and DRS — and together they make the over-rate problem a trait of the format, not of one team.

Another memory is relevant. In 2026, when COVID emptied the stadiums, I made a radio documentary called The Silent 90 for Dhaka FM. When the Bundesliga restarted, I covered Borussia Dortmund versus Schalke from a distance, and I spent my goal commentary describing the echo of the ball and the absent Yellow Wall. I learned then that time has its own weight inside a match, something we rarely notice. This over-rate fine is exactly the accounting of that weight — a ledger the spectator never sees on the scoreboard, yet it is counted in every match.

I covered the 2026 Russia World Cup from a Dhaka studio. That memory matters here, because I learned then that a game keeps running even where no one can see it. On final night, during France–Croatia, I spoke very little about the score, and a producer warned me about it. But the Mullanpur over-rate incident is exactly that kind of football — one that rolls off the field of play, and no one notices.

The comparison between the two formats matters here. The ODI carries the highest over-rate risk — two new balls, mid-innings spin, and DRS all together. The T20 has fewer overs and faster play, so the risk is lower. Seen that way, the Mullanpur incident is a structural gap in the format, not an individual failure.

While everyone says the two teams were fined because they were sloppy, I want to look elsewhere. Our collective memory frames this news one way — two careless teams, two small fines, story over. But that very reading hides the real thing.

First — the fine is not tied to the result. West Indies won the match and were still fined; India lost the match and were still fined. The sanction is a ledger standing outside win and loss. A spectator who watches only the result will never understand this story.

Second, and more important to me — we are talking about India's twenty percent, but the story worth tracking is actually West Indies'. Twice in three months — that is a pattern. If the Caribbean side commits this error a third time in the coming months, the punishment will not be settled by money alone; under ICC rules, repeated offences can escalate, and in serious cases even the question of a captain's suspension can arise. Nobody is watching that risk right now.

Third — we assume home ground means discipline. Here the opposite happened. Host India was the biggest offender. That fact sits awkwardly with the story we carry about a professional powerhouse. I think this very inconsistency is the news's real information gain, something nobody has said before.

And one more — how big is the fine? Twenty percent of the match fee. Against an international cricketer's earnings, that is almost nothing. That small figure itself says the purpose of the sanction is not punishment but warning. It is like a traffic signal — the light turns red, but no one stops. Until the on-field time management changes, that red light will keep glowing every match.

Ahead lies a five-match T20I series, the opener in Lucknow on Tuesday, October 6. In T20 cricket the over-rate risk is lower than in the ODI — fewer overs, faster play. So the realistic prospect is that both sides swallow the fine and become slightly more careful about time management.

But my question sits elsewhere. On that night in Mullanpur, as the sound of victory rose from the West Indies dugout, a clock in the corner of the ground was silently writing its own ledger. No one saw it, no one counted it. The question is this — if the Caribbean side loses to the clock again next series, will we still say it was only a fine? Or will we then understand that cricket's most patient opponent is no bowler at all, but the clock?