HomeWorld CricketSlow Over-Rate at Mullanpur: India Fined 20%, West Indies 10% — But the Real Signal Isn't in the Numbers
Slow Over-Rate at Mullanpur: India Fined 20%, West Indies 10% — But the Real Signal Isn't in the Numbers
**মূল উত্তর (≤৬০ শব্দ):** মুল্লানপুরে অনুষ্ঠিত ভারত-ওয়েস্ট ইন্ডিজ তৃতীয় ওয়ানডেতে ধীর ওভার-রেটের জন্য আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী ভারত ২০ শতাংশ এবং ওয়েস্ট ইন্ডিজ ১০ শতাংশ ম্যাচ ফি জরিমানা দিয়েছে; দুই অধিনায়কই বিনা শুনানিতে শাস্তি মেনে নিয়েছেন। **মূল তথ্য (৩–৫ বুলেট, প্রতিটি ≤২৫ শব্দ):** - ভারত চার ওভার পিছিয়ে ছিল, ফলে প্রতি ওভারে ৫ শতাংশ হিসেবে মোট ২০ শতাংশ জরিমানা হয়েছে। - ওয়েস্ট ইন্ডিজ দুই ওভার পিছিয়ে ছিল, ফলে মোট ১০ শতাংশ ম্যাচ ফি জরিমানা হয়েছে। - ওয়েস্ট ইন্ডিজের এটি তিন মাসে দ্বিতীয় শাস্তি; জুলাইয়ে নিউজিল্যান্ডের বিপক্ষে ৫ শতাংশ জরিমানা হয়েছিল। - ভারতের আগের শাস্তি ২০২৫ সালের ডিসেম্বরে রায়পুরে দক্ষিণ আফ্রিকার বিপক্ষে ১০ শতাংশ জরিমানা। - ম্যাচ রেফারি প্রকাশ ভাট শাস্তি দিয়েছেন; দুই অধিনায়কই আনুষ্ঠানিক শুনানি ছাড়াই দায় মেনে নিয়েছেন। **সূত্র উল্লেখ:** মূল প্রতিবেদন: 'India, West Indies sanctioned for slow over-rate in Mullanpur ODI' (ধারা ২.২২, আইসিসি কোড অব কন্ডাক্ট) | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** - প্রশ্ন: ধীর ওভার-রেটের জরিমানা কীভাবে হিসাব করা হয়? উত্তর: আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী প্রতি ওভার পিছিয়ে পড়লে ম্যাচ ফির ৫ শতাংশ জরিমানা হয়। - প্রশ্ন: ওয়েস্ট ইন্ডিজ কেন ঝুঁকিতে? উত্তর: তিন মাসে দুবার ধরা পড়ায় পুনরাবৃত্ত অপরাধে শাস্তি বাড়ার ঝুঁকি তৈরি হয়েছে, যা cricsultan.com টিম ডিসিপ্লিন ট্র্যাকারে দেখা যায়। - প্রশ্ন: পরের সিরিজ কবে শুরু? উত্তর: পাঁচ ম্যাচের টি-টোয়েন্টি সিরিজ শুরু হচ্ছে লখনউতে, মঙ্গলবার ৬ অক্টোবর।
I opened the Dhaka desk file, and the first column was already arguing with me. The match finished in 48.2 overs — ten balls before the allotted fifty. West Indies chased 352 and won. Yet in that same match, India bowled four full overs short. A home side, on a familiar pitch, in familiar conditions, with every advantage in its favour — and still, India lost to the clock. My experience says a match that ends early rarely produces a slow over-rate charge. Here it did. That is the first signal that the arithmetic has slipped off its normal track.
Slow over-rate charges usually arrive when a match is squeezed for time — rain, Duckworth-Lewis complications, innings that keep breaking apart. None of that exists here. No rain is referenced, no DLS complexity. West Indies bowled their full fifty overs; India batted their full quota. And yet, four overs short. The problem was not the length of the match; it was time management. That small distinction sits at the centre of the whole affair.
The fixture was the third and final ODI of the India–West Indies series, at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, New Chandigarh, Punjab. Roughly 700 runs were scored across both innings — a deck built for batters, offering almost nothing to bowlers. West Indies' successful 352 chase should have been the sporting story of the series. Instead, the match referee's file wrote a different story, one nobody on the field noticed.
Under Article 2.22 of the ICC Code of Conduct, failing to bowl the required overs in the allotted time triggers a fine of 5 percent of the match fee per over short. That rule was applied here. India were four overs short — 4 × 5 percent, a 20 percent fine. West Indies were two overs short — 2 × 5 percent, a 10 percent fine. The arithmetic is purely mechanical, with no room for discretion. But that mechanical arithmetic leaves two uncomfortable questions: why did the home side fall further behind, and why does the Caribbean side keep falling into this trap?
The PPDA dashboard did not shout; it quietly rearranged what I thought I saw. For years I have argued that home ground means home advantage — spin, dew, crowd, umpiring tolerance. But the over-rate column says the opposite. Elite home sides are normally the most disciplined on over-rate, because they know the conditions, they know the rhythm of bowling changes, they understand the umpires' time allowances. Here that picture flipped. India — the hosts, the paper favourites — were the worst offenders. I have learned to trust the row that refuses to fit the story. This row refuses.
And this is where West Indies' part demands even more attention. The 10 percent fine here is their second sanction in three months. In July, they were fined 5 percent against New Zealand. Join those small numbers together and a pattern forms — not a single-match lapse. When a side is caught twice in three months on time management, the question is no longer about the clock; it is about their bowling leadership, the depth of their pace attack, and the speed of their decisions in the middle overs. The Caribbean bowling unit perhaps needs frequent changes, perhaps stalls mid-innings, perhaps takes too long over set-ups. The precise cause is not written in the match report, but the repetition of the trap is written in history.
India, too, has a prior precedent. In December 2026, at Raipur against South Africa, India were fined 10 percent. So under Shubman Gill's captaincy this trap is not a first. One detail stands out: both captains accepted the sanction without contest, so no formal hearing was required. That is a clean administrative outcome — and through it, both captains indirectly concede the delays were self-inflicted. Had there been an external cause, the appeal route was open. They did not take it.
I have argued for years that in cricket, numbers never take the judge's chair. Over-rate is no exception. Four overs short in one match does not mean India is a poorly disciplined team. Judging a side's culture from one match's data is wrong — that is the first lesson I learned at the Dhaka desk in 2026. Back then I used fourteen metrics per match, but even fourteen numbers from one game never become a team's truth.
One confusion needs clearing here: slow over-rate and its cause are different things. The scorecard shows the match ended in 48.2 overs — no side was stuck beyond time. But four overs short means repeated stoppages during the bowling. Perhaps delayed boundary retrievals, perhaps repeated field resets, perhaps extra conferences over bowling changes, perhaps time taken over DRS decisions. A 352 chase means many boundaries, many runs, many ball-ups — and every ball-up means lost time. A pitch that comforts batters is a slow death for bowlers. It is ironic, but it is real.
Now to my biggest doubt. I do not read this fine as corruption or a grand crisis — and I think turning it into a crisis would be a mistake. The rule is clear, the arithmetic is clear, the chain of sanction is clear. Both captains, Shubman Gill and Shai Hope, accepted responsibility. Administratively, this is an almost perfectly executed event. But that is precisely the danger: this transparency can blind us. An administrative news item can divert us from the real question — why West Indies keep getting caught, and how batting-dominated this ODI leg actually became.
West Indies keep falling into this trap, because a further offence can escalate the punishment. In the ICC framework, repeated breaches can move beyond fines toward captain suspension in serious cases. Two offences in two months is the first step of danger. If a third arrives within six months, the picture changes. That is why West Indies' coaching staff should install a dedicated over-management protocol now — because when a team is winning, these traps stay hidden.
India's case is different. Four overs short in one match does not prove a bad over-rate culture — that would be over-interpretation. Treat it as a single-match warning. But the warning is not trivial, because it happened at home. Where an elite home side should be most disciplined, India fell furthest behind — that asymmetry is the most quotable line for media. But a quotable line is not the truth. I had a junior analyst repeatedly attack this conclusion: two data points do not prove a team's discipline culture.
The ODI format carries a structural weakness we often forget. Two new balls, the compulsion of mid-innings spin changes, and frequent DRS reviews together make the ODI the most over-rate-sensitive of the three formats. In Tests, time is looser; in T20Is, overs are fewer and play is faster. But in a 50-over match, every small pause accumulates. So part of this fine is individual fault, and part is the format's innate flaw. Failing to separate the two will make us blame the wrong people.
The broadcasting angle should not be ignored either. A slow over-rate does not just spoil the rhythm of play; it disrupts fixed-slot transmission. Television channels want to finish within a set window and schedule their advertising blocks accordingly. So broadcasters have a commercial stake in strict over-rate enforcement — although the original report does not say so directly. This is my inference, but a credible one.
The Bangladesh context is relevant here too. In South Asian cricket, complaints about over-rate are nothing new; the region's pitches, heat, humidity and long innings make time management permanently difficult. From the Dhaka desk I have seen many times how a fine quickly buries a series' bigger story. But my job is to read the rows beneath the cover. In this match, the third umpire was Bangladesh's own Sharfuddoula — a small detail that matters to us, because it shows South Asian umpires now sit at the centre of decisions on the big stage.
I do not read this event as a grand crisis, but I will not wave it away as small either. It is a quiet warning — one that may grow important in the coming months.
The dashboard was never the answer; it was the map I had to redraw. By this map, the next signal is clear: a five-match T20I series begins in Lucknow on Tuesday, October 6. In T20Is, over-rate risk is far lower, because overs are fewer and play is faster. So if the trap reappears in the T20Is, we must conclude the problem is the team, not the format. And if West Indies are caught again in the next ODI, then the question will not be the size of the fine, but the prospect of suspension.
For now, everything is calm. But one column on my desk remains empty — because when a team wins and walks off, nobody keeps the clock's accounts.

Related Players
Recommended
Recommended
Cricket's Data-Blockchain Economy: Fan Tokens, Smart Contracts and the Real Price of Scouting2026-10-01
The Murshida Khatun Selection Controversy: A Hand-Written 16th Name, and the Process Question Facing Bangladesh Women's Cricket2026-10-05
Where Did the World-Cup Boys Go? A Quiet Audit of Bangladesh's Talent Economy2026-09-26
SA20 2027 Auction: From 789 to 156 — The Stratum Hiding a Mid-Tier League's Economy2026-10-06
The Calendar That Counts Bones: Cricket's Hidden Ledger of Bowling Load2026-10-03
