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

The match was over in 48.2 overs. Ten balls were still in hand. West Indies chased down 352 on Indian soil, in Indian conditions. The scoreboard says the game was quick and thrilling, a surface made for batters. Yet in the same match India bowled four overs short, and West Indies two overs short.

That is the first contradiction. In a game that never reached the full 50 overs, how did an over-rate deficit appear at all? I have watched cricket for years, and my experience says over-rate talk usually peaks when a match drags, when rain interrupts, or when DRS reviews pile up. At Mullanpur it was the reverse. The clock and the scoreboard are giving contradictory testimony. When two truths sit together, the first job is always the same: find out where the number came from, and who verified it.

Among the three international formats, the over-rate risk is highest in ODIs. The reason is structural. Fifty overs use two new balls, one from each end. Spin comes on in the middle overs, field placements invite long conversations, and every DRS review costs time. Each of these slows the game. T20 has fewer overs and moves fast; Tests keep a separate time account. The over-rate rule and the ODI format are almost inseparable.

Now the geography and environment of this match. The venue is Mullanpur, New Chandigarh, Punjab, the Maharaja Yadavindra Singh International Cricket Stadium, an Indian home ground. An aggregate of roughly 700 runs across two innings clearly signals a batting-friendly surface. India batted first and posted more than 350; West Indies overhauled it in 48.2 overs. There is no mention of rain, dew or DLS, so I cannot speculate on those.

The venue factor deserves its own line. A batting-friendly deck means long innings, more boundaries, longer ball retrievals, constant bowling changes. The character of the pitch itself becomes a cause of slow play. I always read environment as a system: crowd absence, altitude, travel miles, rest days are not separate variables but linked ones.

Look again at the 352 chase. On a surface where the first innings produced 350-plus, bowlers' plans rarely work. Spin, pace, variation, everything is tried and runs still flow. That multiplies bowling changes and field changes, and time leaks. A plausible explanation for India's over-rate shortfall may hide here. But it is inference, not confirmed fact.

One point needs to be stated plainly. A slow over-rate penalty is not a skill metric but a match-management discipline metric. And the penalty lands mainly on the captain, because ICC rules place over-rate management in the captain's charge.

India versus West Indies is a rivalry with history. West Indies dominated the 1970s and 1980s; India leads the modern era. But a West Indies chase of 352 in this ODI leg shows the series was not one-sided. It was a competitive, high-scoring ODI leg.

I built the xG ledger in Sylhet before I trusted a single number. When the power failed, the data did not stop, either; I kept logging scores into a handwritten ledger by candlelight. The same applies here: rule first, number second.

The rule is Article 2.22 of the ICC Code of Conduct for Players and Player Support Personnel. A team that fails to bowl its overs within the allotted time, after allowances, is fined 5% of the match fee for each over it falls short.

Now the arithmetic. India four overs short: 4 × 5% = 20%. West Indies two overs short: 2 × 5% = 10%. The penalties are not a referee's discretion but a direct output of the rule. That check matters, because we often guess at the shape of a sanction without doing the sum. Here the sum is clean.

The second, more important fact: West Indies have now been sanctioned for over-rate twice in three months. In July they were fined 5% against New Zealand; at Mullanpur it rose to 10%. Put the two data points together and it is not a single-match lapse but a recurring problem in West Indies' ODI bowling management. To me this second point is the article's real information value.

Then look at India. The home side, familiar conditions, a familiar pitch, and still four overs short. Normally it is home teams that are held up as the most over-rate-disciplined. At Mullanpur that assumption flipped. So the asymmetry is the most telling data point: India 20%, West Indies 10%, and India were the hosts.

Consider the officiating chain. The charges were laid by on-field umpires Jayaraman Madanagopal and Sam Nogajski, third umpire Sharfuddoula and fourth umpire Virender Sharma. The sanction was levied by match referee Prakash Bhatt. Both captains, Shubman Gill of India and Shai Hope of West Indies, accepted the sanction without contest. No formal hearing was needed.

That acceptance is itself information. Contesting would have opened a hearing. They did not, which means the teams knew the delays were self-inflicted. For Gill it is the first documented home over-rate blemish of his full-time ODI captaincy. India had previously been fined 10% against South Africa at Raipur in December 2026.

This report carries no batting or bowling performance data for Gill or Hope, so player-level technical analysis is not possible. What can be analysed is only captaincy accountability. And that accountability is simple: whoever owns the clock on the field carries the cost.

Here is my caution. One match's over-rate cannot define a team's discipline culture. Correlation is not causation. Russia 2026 taught me that speed can sometimes be a pricing error.

India's four-over shortfall may rest on something other than pure sloppiness: repeated DRS reviews, injury checks, bowling-change conferences, field resets. With little help for bowlers, a 352 chase forced constant bowling changes and slow boundary retrievals. These are inferences, not confirmed facts. Until the root cause is clear, one match's number cannot be called a trend.

Second: at 5% per over, the scale is cheap relative to match fees. It functions mainly as a deterrent signal, not a punitive one.

Third, there is a commercial layer. Broadcasters have an interest in strict over-rate enforcement. Television runs on fixed slots; a long match scrambles the schedule and wastes advertising windows. The enforcement is about operational discipline as much as playing discipline.

I have noticed that West Indies' recurring over-rate trouble may also signal inexperienced bowling leadership or a thin pace attack that needs frequent changes. That, too, is inference.

There is a larger format-level question. The ODI structure carries delay inside it. As schedule density rises and broadcast windows tighten, over-rate enforcement is likely to get stricter, perhaps with in-match penalties. If so, over-rate management becomes a tactical skill.

Look forward. A five-match T20I series begins in Lucknow on Tuesday, October 6. T20Is have fewer overs and move fast, so over-rate risk is far lower than in ODIs. Still, two things deserve watching.

First, if West Indies are sanctioned a third time within six months, fines can escalate, and serious or repeated breaches can raise the question of captain suspension. Second, this is India's first home over-rate blemish under Shubman Gill; if it recurs, the media will turn it into a larger captaincy question.

In a match where 352 was chased in 48.2 overs, only time was left over. Who counts that time: the referee, or the team itself?