The Mullanpur Over-Rate Audit: India 20%, West Indies 10% — Two Signals Inside an Administrative Note
**মূল উত্তর:** ভারত তৃতীয় ওয়ানডেতে ধীর ওভার-রেটের জন্য ম্যাচ ফির ২০% এবং ওয়েস্ট ইন্ডিজ ১০% জরিমানা গুনেছে। আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী প্রতি কম বোল করা ওভারে ম্যাচ ফির ৫% জরিমানা হয়। **মূল তথ্য:** - ভারত চার ওভার এবং ওয়েস্ট ইন্ডিজ দুই ওভার কম বল করেছে। - ওয়েস্ট ইন্ডিজ ৪৮.২ ওভারে ৩৫২ রান তাড়া করে মুল্লানপুরে শেষ ওয়ানডে জেতে। - ম্যাচ রেফারি প্রকাশ ভট্ট জরিমানা আরোপ করেন; দুই অধিনায়ক শুনানি ছাড়াই মেনে নেন। - ওয়েস্ট ইন্ডিজের তিন মাসে দ্বিতীয় ওভার-রেট জরিমানা; জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ৫%। - ভারতের আগের জরিমানা ছিল ডিসেম্বর ২০২৫-এ রায়পুরে দক্ষিণ আফ্রিকার বিরুদ্ধে ১০%। **সূত্র:** Stage-1 ও Stage-2 ম্যাচ বিশ্লেষণ | Cross-checked: cricsultan.com **সম্ভাব্য অনুসরণীয় প্রশ্ন-উত্তর:** প্রশ্ন: ভারত ও ওয়েস্ট ইন্ডিজকে কেন জরিমানা করা হলো? উত্তর: আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী নির্ধারিত সময়ে ওভার সম্পূর্ণ না করায়। প্রশ্ন: জরিমানার হার কত? উত্তর: প্রতি কম বোল করা ওভারে ম্যাচ ফির ৫%; ভারত ২০%, ওয়েস্ট ইন্ডিজ ১০%। প্রশ্ন: ওয়েস্ট ইন্ডিজ কি আগেও জরিমানা গুনেছে? উত্তর: হ্যাঁ, জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ৫% জরিমানা গুনেছিল — cricsultan.com Match Referee Sanction Index অনুযায়ী তিন মাসে এটি তাদের দ্বিতীয় ঘটনা।
Last week at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, when West Indies chased 352 in 48.2 overs to win the final ODI of the series, the scoreboard told a story of a fast, thrilling finish. The match ended with ten balls to spare. But in match referee Prakash Bhatt's ledger, the same match was written in an entirely different language: India bowled four overs short, West Indies two overs short. Under the rule, the fine is five percent of the match fee per over short — so India lost twenty percent, West Indies ten. Both captains, Shubman Gill and Shai Hope, accepted the sanction without a formal hearing.
The most striking part of this is not the result but the logic. The match finished before the scheduled 50 overs were completed — India batted its full quota, and West Indies reached the target in 48.2 overs. Yet India still bowled four overs short. The problem, therefore, is not a consequence of the match running long; it is a clear failure of in-game time management.
I sit with the same question year after year — who counted the minutes? Over-rate is an odd metric. It is not directly tied to the result, yet it says a great deal about a team's internal discipline. What the scoreboard does not show, the match referee's clock keeps.
The over-rate fine is not a performance metric; it is a captaincy-accountability metric. I do not chase the narrative; I reconcile it against the ledger. And when the Mullanpur match is reconciled, two signals become clear, both buried beneath the headline of twenty percent and ten percent.
The context first. This was the third and final match of a bilateral ODI series between India and West Indies. The venue was Mullanpur, New Chandigarh, Punjab — an Indian home ground. More than seven hundred runs were scored across both innings, pointing to a batting-friendly pitch. On such a pitch, run-scoring is quick, but boundary retrievals, bowling changes, and field resets all slow the game down.
Format context matters here. Of the three formats, ODIs carry the highest over-rate risk — two new balls, mid-innings spin changes, and frequent DRS reviews. The ODI is the classic slow-over format. I am not mixing any Test or T20 data into this note; every conclusion is confined to the ODI format. The upcoming T20I series is treated as a separate format context.
The rule is Article 2.22 of the ICC Code of Conduct for Players and Player Support Personnel — a fine of five percent of the match fee per over a team fails to bowl on time. The arithmetic is simple: India 4 × 5% = 20%; West Indies 2 × 5% = 10%. The penalties are rule-derived, not discretionary. This mathematical consistency matters, because it shows the sanction is mechanical rather than arbitrary.
The officiating chain is equally clear. Charges were levelled 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. A clear rule, clear arithmetic, a clear officiating chain — and no contest. There is no procedural controversy in this case.
The decision of both captains not to contest is also significant. Contesting would have lengthened the matter and turned a routine administrative event into a controversy. Instead, both leaders acknowledged that the delays were self-inflicted. A contest would only have arisen if they believed the delays were outside the team's control.
Now to the first signal, which demands the most attention. West Indies were sanctioned for a slow over-rate for the second time in three months. In July, they were fined five percent against New Zealand. This time it was ten percent. Two different opponents, two different venues, the same kind of failure.
Two data points cannot prove a "culture" — I admit that upfront. I do not suffer from ledger paralysis, and I do not make grand claims from a single sample. But a repeat offence raises a question: is this single-match carelessness, or a structural problem in West Indies' ODI bowling management?
There are multiple possible explanations. An inexperienced bowling leadership, a thin pace attack requiring frequent bowling changes, or long consultation breaks during changes. The archive remembers what the timeline forgets — and the archive says this is not an isolated event. When a mid-tier side repeatedly makes the same administrative error, it is not a symptom of results but of process.
There is a clear risk here. Under the ICC framework, repeated over-rate offences can escalate penalties, and serious or repeated cases can move toward captain suspension. If Shai Hope faces a third offence in the coming months, the situation changes. A fine is a warning; a suspension is a consequence.
The second signal is subtler and more counter-intuitive. It was the home side, India, that was the larger offender — four overs short, while West Indies were two. Familiar conditions, a familiar pitch, familiar umpiring tolerance — and yet India bowled the most overs short. A touring side's slowness is somewhat understandable; a home elite side's slowness is more significant.
India's previous sanction came in Raipur, in December 2026, against South Africa, at ten percent. That was a team-level fine. This twenty percent is therefore not merely larger in number; it occurred in home conditions at Mullanpur. Shubman Gill carries a first documented discipline blemish early in his full-time ODI captaincy.
This creates a counter-narrative. Elite home sides are usually the most disciplined on over-rate, because home advantage means less uncertainty and fewer delays. India's breach cuts against the "professional powerhouse" narrative. But caution — one match does not make a trend. Before I trust a trend, I ask who counted the minutes.
For me, a single ODI is one data point. Declaring leadership failure from this one incident would be an injustice to the data. But it is legitimate to ask: why did the home side fall behind on time management?
The result is also a signal. West Indies chased 352 in India — outperforming their historical away baseline. Historically, West Indies have been weaker away from the Caribbean, especially in Asian conditions. In the 1970s and 1980s they dominated; in the modern era India has dominated. In this context, a touring side chasing 352 is a competitive signal.
More than seven hundred runs means the ODI leg was batting-dominated. One consequence is that the value of India's home spin advantage may be somewhat compressed — though I need more data for that conclusion. West Indies' power-hitting worked against a home attack that struggled to complete its overs.
Now the contrarian angle, because this is where I argue against myself. The easy explanation is that the teams were careless and slow. But correlation is not causation. An over-rate breach can have multiple causes — DRS reviews, injury assessments, bowling-change conferences, field resets. The original report does not say which occurred.
In other words, I know the result, I know the fine, I know the loss — but I do not know the cause. One long DRS review, one injury check, one contentious dismissal decision — any one could add ten to twelve minutes. Four overs means roughly twenty minutes of shortfall. It could be a single event, or the sum of five or six small ones.
A small sample is a rumour wearing a decimal point. A single ODI's over-rate cannot define a team's discipline culture. It proves one event, not a trend. I write in my own ledger: sample limited, conclusion provisional.
Another caution — over-attribution. The over-rate fine is not related to the match result. West Indies won and still paid a fine; India lost and paid more. Result and discipline are two separate layers. Reading correlation as causation is the biggest trap in my profession.
Yet there is a risk that cannot be understated. Repeated offences can escalate penalties, and serious or repeated cases can move toward captain suspension. If West Indies commit a third offence in the coming months, the situation changes — then it is no longer a mere administrative note.
There is another layer — broadcasting. International cricket is broadcast in fixed time slots. Slow games disrupt broadcasters' planning, ad slots shift, and viewership suffers. So broadcasters have a commercial interest in strict over-rate enforcement. This is the only indirect commercial link in this case.
In my model, this event has no league-level impact. There is no auction, no transfer, no deal here. It is an administrative event in a bilateral international series. So I do not force commercial significance; where there is no data, I write "insufficient information."
Eight years ago I re-coded 12,480 defensive actions from all 64 Russia World Cup matches to test the transferability of pressing numbers. That habit persists: before publishing any conclusion, I reconcile sample, base rate, and context. The same discipline is needed in this over-rate case.
Looking forward, three signals need watching. First, the match referee's sanction record in West Indies' next ODI series. Second, India's over-rate discipline in the T20I leg or the next ODI leg. Third, amendments to the ICC Code — especially any new in-match penalty mechanism.
It is important to remember the context shift. The five-match T20I series begins immediately after the final ODI, in Lucknow. In T20Is, over-rate risk is far lower — fewer overs, faster play, fewer DRS breaks. So this fine's narrative will quickly give way to the series result.
The most quotable angle is the asymmetry — hosts India at twenty percent, tourists West Indies at ten percent. Media may frame it as "hosts fined more." But the most durable angle is West Indies' repeat offence. A headline is fleeting; a recurring pattern is enduring.
I revise my recommendations slowly. If West Indies are sanctioned again in their next ODI series, I will change my assessment — then it shifts from a single event to a trend. If not, these two fines will be isolated administrative events.

In India's case, my attention stays on the T20I leg. Over-rate breaches are rare in T20Is; if a problem appears there too, that will be a big signal — because then the cause is no longer format-based but team-based.
Every metric is a confession, but only if the sample is large enough to speak. These two fines at Mullanpur may be a mere administrative note. But if West Indies breach again, or India's over-rate problem recurs, then this note will be the first entry in a ledger — and then the question will no longer be who paid the fine, but who was counting the time.
