Mullanpur Over-Rate Audit: The Match Ended With 10 Balls Left, Yet India Finished 4 Overs Short
**মূল উত্তর:** ভারত ও ওয়েস্ট ইন্ডিজকে মুল্লানপুর ওয়ানডেতে ধীর ওভার-রেটের জন্য জরিমানা করা হয়েছে। ভারত চার ওভার কম বলায় ম্যাচ-ফির ২০ শতাংশ, ওয়েস্ট ইন্ডিজ দুই ওভার কম বলায় ১০ শতাংশ জরিমানা পেয়েছে — আইসিসি কোডের ধারা ২.২২ অনুযায়ী প্রতি ওভারে ৫ শতাংশ। **মূল তথ্য:** - ওয়েস্ট ইন্ডিজ ৩৫২ রান ৪৮.২ ওভারে তাড়া করে জেতে; তবু ভারত চার ওভার কম বলেছে। - ভারত ম্যাচ-ফির ২০ শতাংশ, ওয়েস্ট ইন্ডিজ ১০ শতাংশ জরিমানা পেয়েছে; ধারা ২.২২-এ প্রতি ওভার ৫ শতাংশ। - ম্যাচ-রেফারি প্রকাশ ভাট শাস্তি দেন; দুই অধিনায়ক শুভমান গিল ও শাই হোপ শাস্তি মেনে নেন, শুনানি হয়নি। - তিন মাসে ওয়েস্ট ইন্ডিজের দ্বিতীয় ওভার-রেট শাস্তি; জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ছিল ৫ শতাংশ। - ভারতের আগের জরিমানা: ডিসেম্বর ২০২৫-এ রায়পুরে দক্ষিণ আফ্রিকার বিরুদ্ধে ১০ শতাংশ। **সূত্র:** মূল সূত্র: ভারত বনাম ওয়েস্ট ইন্ডিজ তৃতীয় ওয়ানডে ওভার-রেট প্রতিবেদনের স্টেজ-২ বিশ্লেষণ। প্রকাশ: অক্টোবর ২০২৬। | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: আইসিসি ধীর ওভার-রেট জরিমানা কীভাবে হিসাব করে? উত্তর: ধারা ২.২২ অনুযায়ী প্রতি ওভার কম বলায় ম্যাচ-ফির ৫ শতাংশ; তাই ভারতের ৪ ওভার = ২০ শতাংশ, ওয়েস্ট ইন্ডিজের ২ ওভার = ১০ শতাংশ। প্রশ্ন: ওয়েস্ট ইন্ডিজ কি পুনরাবৃত্ত অপরাধী? উত্তর: হ্যাঁ, এটি তিন মাসে তাদের দ্বিতীয় শাস্তি; জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ৫ শতাংশ জরিমানা পেয়েছিল, cricsultan.com গভর্নেন্স ডেটা অনুযায়ী। প্রশ্ন: ওয়ানডে সিরিজের পর কী? উত্তর: পাঁচ ম্যাচের টি-টোয়েন্টি সিরিজ লখনউ থেকে মঙ্গলবার ৬ অক্টোবর শুরু, যা আলাদা Format প্রেক্ষাপট।
The Mullanpur scoreboard and the match referee's report are asking each other questions. West Indies chased 352 in 48.2 overs — the final ten balls never touched the field. Yet match referee Prakash Bhatt's report states India bowled four overs short and West Indies two. The fines are 20% and 10% of match fees respectively. Under Article 2.22 of the ICC Code of Conduct, a team is fined 5% per over short — the arithmetic is exact, 4×5=20, 2×5=10. The story here is not the fine. The story is: how did one side finish four overs short in a match that ended ten balls early? Where did the time go?
The match was the third and final ODI of the India-West Indies series, at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, New Chandigarh. Nearly 700 runs across two innings — a surface that favoured the batters. That means long innings, more boundary retrievals, frequent bowling changes, and ideal conditions for a slow over-rate. The ODI format itself carries the highest over-rate risk of the three — two new balls, mid-innings spin changes, and a high volume of DRS reviews.
The on-field umpires were Jayaraman Madanagopal and Sam Nogajski, with Sharfuddoula as third umpire and Virender Sharma as fourth. The charges were levelled by the on-field umpires; the sanctions were imposed by match referee Prakash Bhatt. No formal hearing was held — both captains, Shubman Gill and Shai Hope, accepted the sanction. That is an efficient administrative resolution.
This is not a Test or a T20 — it is an ODI. The upcoming T20I series is a separate format context and must be read separately. ODI conclusions cannot be stretched into T20 cricket.
The tape does not lie, but the zone does — so the audit begins with process, not emotion. The referee's two lines carry several distinct signals, and each needs to be verified on its own.
First, India's four-over deficit was not caused by the match running long. West Indies bowled their full 50 overs, India batted their full quota, and the chase ended in 48.2 overs. With every opportunity to save time, India still finished four overs short — that is not a scheduling problem, it is a self-inflicted time-management failure. Had the match run its full 50 overs, the deficit would have grown.
Second, the asymmetry — the host side was fined more. In home conditions, in a familiar environment, under familiar umpiring tolerance, India finished four overs short, while the travelling mid-tier West Indies stopped at two. Elite home sides are normally the most disciplined on over-rate. Here the picture is reversed.
Third — and this is the most durable point — West Indies' repeat. This match's 10% sanction is their second in three months; in July it was 5% against New Zealand. This is where I run the sequence three times. One event is an event; two events hint at a pattern. West Indies' problem is an operational discipline issue independent of results — a mid-tier side repeating fine-level administrative mistakes.
India also has a precedent: a 10% fine against South Africa in Raipur in December 2026. But that is one event, and Mullanpur's four overs is another. A single match does not create a culture. Under Shubman Gill, this is his first documented over-rate blemish, and it came at home.
Fourth, the benchmark. Top international sides usually finish an innings within zero to one over. Here India are four, West Indies two — both below standard, at least in this single match. This is not a skill metric but a captaincy-accountability metric — the over-rate sanction lands directly on the captain's record, not the bowler's.
Fifth, the administrative machinery is clean. The rule is clear, the arithmetic is clear, the umpiring chain is clear, and there was no contest. The 5%-per-over scale is low-cost relative to match fees — so it functions more as a deterrent signal than a punishment. Repeated offences can escalate fines, and in serious cases the question of captain suspension can arise. For West Indies, that door is open.
Sixth, three scenarios. Worst case: a third West Indies over-rate offence in the coming months — escalating sanctions and possible suspension risk. Base case: both sides absorb the fine, treat it as routine, and improve time management in the coming T20I series, since T20s are fewer overs and faster. Optimistic case: the sanction itself acts as a deterrent, non-essential stoppages fall, and DRS decisions quicken.
Seventh, there is one indirect commercial link — broadcasting. A slow over-rate disrupts fixed-slot broadcast programming; broadcasters therefore have a vested interest in strict enforcement to protect schedule integrity. This is not a league-commercial link but a governance-commercial one.
A further point on the surface. Nearly 700 runs at Mullanpur means the pitch slowed for spinners, the outfield quickened, and the ball had to be retrieved again and again. My experience tells me over-rates always worsen on high-scoring decks — because every over sees more balls reach the boundary, and more time is needed to reset the field. Year after year of watching matches, I keep seeing this: the higher the runs, the faster the clock.
A 352 chase is not just a result, it is a signal. A mid-tier travelling side overhauled a 350-plus target on Indian soil — a side historically weaker in Asian conditions. It means West Indies' ODI batting is functioning, but their game-management discipline is not. That gap is the core of the audit: good with the bat, poor with the clock.
DRS and injuries. Not stated directly in the report, but inferable: India's four-over deficit is not the product of a single delay but of repeated stoppages — DRS reviews, injury assessments, bowling-change conferences, field resets. Each stoppage is seconds; together they are overs. That is the invisible time the scoreboard never shows.
My own audit experience. In 2026, doing a set-piece audit for Anderlecht in the Europa League, I learned that patterns must be found on tape, not in statements. Their zonal marking was conceding 0.12 xG per corner — I logged 42 set-pieces to surface the pattern. The same rule applies here: four overs and two overs are two numbers, but the pattern behind them is the real story.

Home umpiring tolerance is a variable. A host side usually gets some leeway on time, because umpires too are used to home conditions. Despite that leeway, India were the worst offender — that is the most uncomfortable number of this match.
The coming five-match T20I series begins in Lucknow on Tuesday, October 6. T20Is carry less over-rate risk — only 20 overs, quicker bowling, fewer DRS reviews. So the ODI sanction is not a forecast for the T20Is. But one thing does carry over: the captain's record. Gill and Hope are both now marked, and that stays in the match referee's book.
Signals to watch: West Indies' over-rate record, India's discipline, the T20I series results, and the evolution of the ICC over-rate rule. As match density rises, over-rate will become a bigger governance issue.
One question lingers: is a 5% fine enough? Losing a fifth of a match fee is almost nothing for a star cricketer. If this low-cost scale fails to deter, the ICC may eventually have to consider stricter, signal-based penalties.
Here a caution is due, because I could fall into this trap myself. A 352 chase and a win is a big upset — but Belgium beat Brazil once; the audit asks what can be repeated. One match's over-rate cannot write a team's discipline culture. Sample size, or silence.
Likewise, it would be wrong to recast India's four overs as 'India are undisciplined.' This is a single-match flag, not a trend. And West Indies' two data points are also small — two sanctions in three months hint at a pattern, not proof. Correlation is not causation; a fine is not a team's mentality. Home advantage did not show up in the result here, but it did show up in the discipline — that is the real counter-story of this match.
The real test is not now, but in the coming T20I series. The five-match contest beginning with the Lucknow opener will show whether India's four overs were a one-day lapse or a beginning. And if West Indies slip again for a third time within six months, the audit will ask: is this an accident, or a system?
