World Cricket
Slow Over-Rate at Mullanpur: India 20%, West Indies 10% — What the Ledger Shows
**মূল উত্তর:** ভারত ও ওয়েস্ট ইন্ডিজকে মুলানপুরে তৃতীয় ওয়ানডেতে ধীর ওভার-রেটের জন্য জরিমানা করা হয়েছে। আইসিসি আচরণবিধির ধারা ২.২২ অনুযায়ী প্রতি ওভার পিছিয়ে পড়লে ম্যাচ ফির পাঁচ শতাংশ কাটা হয়। ভারত চার ওভার পিছিয়ে কুড়ি শতাংশ, ওয়েস্ট ইন্ডিজ দুই ওভার পিছিয়ে দশ শতাংশ জরিমানা দিয়েছে। **মূল তথ্য:** - ওয়েস্ট ইন্ডিজ ৩৫২ রান ৪৮.২ ওভারে তাড়া করে জিতে নেয়; ম্যাচে ১০ বল বাকি ছিল। - ভারত চার ওভার পিছিয়ে ম্যাচ ফির ২০% এবং ওয়েস্ট ইন্ডিজ দুই ওভার পিছিয়ে ১০% হারায়। - ম্যাচ রেফারি প্রকাশ ভাট সাজা দেন; শুভমান গিল ও শাই হোপ শুনানি ছাড়াই তা মেনে নেন। - ওয়েস্ট ইন্ডিজের এটি তিন মাসে দ্বিতীয় সাজা; জুলাইয়ে নিউজিল্যান্ডের বিপক্ষে ছিল ৫%। - ভারতের আগের সাজা রায়পুরে দক্ষিণ আফ্রিকার বিপক্ষে ডিসেম্বর ২০২৫-এ, ১০%। **সূত্র:** আইসিসি আচরণবিধি ধারা ২.২২-এর অধীনে ম্যাচ রেফারির সাজা, ভারত বনাম ওয়েস্ট ইন্ডিজ তৃতীয় ওয়ানডে, মুলানপুর; প্রকাশ: অক্টোবর ২০২৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: ধীর ওভার-রেটের জরিমানার হার কত? উত্তর: আইসিসি আচরণবিধির ধারা ২.২২ অনুযায়ী প্রতি ওভার পিছিয়ে পড়লে ম্যাচ ফির পাঁচ শতাংশ। প্রশ্ন: ওয়েস্ট ইন্ডিজের জন্য প্রধান ঝুঁকি কী? উত্তর: তিন মাসে দুইবার সাজা পাওয়ায় তৃতীয় অপরাধে জরিমানা বাড়তে পারে এবং অধিনায়ক-নিষেধাজ্ঞার আলোচনা তৈরি হতে পারে। প্রশ্ন: Next সিরিজ কবে? উত্তর: পাঁচ ম্যাচের টি-টোয়েন্টি সিরিজ শুরু লখনউতে মঙ্গলবার, ৬ অক্টোবর ২০২৬, যেখানে ওভার-রেটের ঝুঁকি ওয়ানডের চেয়ে অনেক কম।
At the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, West Indies chased 352 and finished the match in 48.2 overs — with ten balls still left in the innings. The game ended early. And yet, in that same match, India were penalised for being four overs behind the clock, West Indies for two. I opened my field-map ledger and watched the sequences twice: once for the flow of the game, once purely for the clock. The second viewing made it clear. The length of the match has no direct link to this sanction; the cause sits in the small stoppages piling up inside the innings — bowling-change conferences, field resets, reviews, injury assessments.
One thing needs stating upfront. Everything analysed here belongs strictly to the ODI, 50-over format. No Test or T20 performance data is mixed in. By long habit I do not cross format boundaries, because the format itself is a variable. And the ODI is the format with the highest over-rate risk of the three: two new balls from either end, a mandatory spin change in the middle overs, and reviews arriving again and again — all of it working against the clock. The Mullanpur surface was flat; roughly 700 runs came across both innings. A flat deck means longer boundary retrievals, more bowler changes, and a naturally slower game. Match referee Prakash Bhatt applied Article 2.22 of the ICC Code of Conduct, under which a team is fined five percent of its match fee for every over it falls short.
Chasing 352 on Indian soil is no small thing, especially where spin normally governs the tempo. West Indies' chase tells us the ODI leg was batting-dominated. And batting-dominated matches put the most pressure on a bowling side's time management — every boundary retrieval, every field reset before a bowling change, costs minutes.
The arithmetic is entirely mechanical, with no room for discretion. India four overs short, four times five — twenty percent. West Indies two overs short, two times five — ten percent. These penalties are products of a formula, not of a referee's mood. The charges were laid by on-field umpires Jayaraman Madanagopal and Sam Nogajski, third umpire Sharfuddoula and fourth umpire Virender Sharma; the sanction rests with the match referee. Both captains — Shubman Gill and Shai Hope — accepted the penalty, so no formal hearing was needed. That acceptance itself says something: the delays were not imposed from outside, they were self-made.
Here lies the real information. For West Indies, this is a second sanction in three months. After five percent against New Zealand in July, now ten. Once is an event; twice is a pattern. A single fine can describe a match accident; the same error returning within a short window points to a management problem — the rhythm of bowling changes, the experience of the bowling leadership, or the depth of the pace attack. India's previous sanction came in Raipur, against South Africa, in December 2026, at ten percent. Placed side by side, these two facts stop looking purely administrative.
This is where the conventional reading slips. The natural assumption is that playing at home makes over-rate worries lighter — familiar conditions, familiar surfaces, familiar umpires. At Mullanpur the opposite happened. The host side was the bigger offender, four overs short. The second common assumption is that a quick finish buys time. But a chase completed in 48.2 overs means ten fewer balls were actually bowled, and India were still four overs behind. The damage was not at the end of the innings; it was in the middle overs. Time that appears to be 'saved' never comes back.
The empty-stadium experiment taught me this — strip away the noise of the environment and the real variable surfaces. In 2026, watching eighteen Bundesliga matches behind closed doors, I saw how home advantage shrinks. The same method applies here. Separate over-rate from result and it becomes clear that over-rate measures discipline more than talent. The ledger does not lie — four and two, twenty and ten; none of it depends on feeling.
Bringing football's tagging habits here requires a caution. Football's half-space and cricket's corridor are not the same thing. In cricket, space means the off-side gully-point corridor, the square-leg boundary rope, the slip-gully channel. So 'slow over-rate means slow bowling' is a false equation. It is not the speed of the ball on trial; it is the gaps between the balls.
On the captaincy side, this is a metric of accountability, not of skill. Shubman Gill carries his first discipline mark at home early in his full-time ODI captaincy. Shai Hope's side has now been sanctioned twice in three months, which raises a structural question about West Indies' ODI bowling management. The decision not to contest matters too. ICC rules allow a hearing if a sanction is challenged; neither captain took that route.
A warning applies to my own method here. My old habit is to find the same decision across seven clips, proving the pattern is structural rather than anecdotal. Right now I have only two data points. So I will not make a seven-clip claim. Without a control group you cannot claim a pattern — esports taught me at least that much. A single match's over-rate cannot define a team's discipline culture.
And one point cannot be skipped. Over-rate is not purely a captain's failure; a large part of it is a design flaw in the format. Two new balls, the mandatory mid-innings spin change, a growing review culture — the rules themselves invite slowness. A rule that only increases the size of the fine, without touching the structure of the game, does not solve the problem; it merely keeps a record.
There is an indirect effect. Slow over-rates directly damage fixed broadcast slots. A fixed slot means advertising blocks are locked in advance; a delayed match scrambles the whole calculation. Broadcasters therefore have a stake in strict enforcement — a part of the story that never makes the news.
The five-match T20I series begins in Lucknow on Tuesday, October 6, 2026. Over-rate risk in T20Is is far lower — fewer overs, faster game. So the real test is this: if both sides stay clean through the T20I leg, the problem lies in the format's design rather than in team culture. And if West Indies pick up a third sanction within six months, the ten-percent figure stops being routine administrative cost and becomes a leadership question. What evidence would prove my projection wrong? A clean, quick, sanction-free T20I leg.



Related Players
Popular Reads
The Empty Archive: In the Blockchain Age, Saying Nothing Is Also a Decision2026-10-07
The Captaincy Handover: Mandhana's First Assignment and the Real Test of the Zimbabwe Series2026-10-07
The Vice-Captain's Chair at Wankhede, and a Nineteen-Year-Old's Shadow2026-10-06
One Test, One Hundred and Twelve: The Anatomy of a Single-Cap Career2026-10-06
The Manuscript of a Scoreless Match: The Royal–Thomian Heritage and the 33rd Dr. R.L. Hayman Trophy2026-10-06
Recommended
Final-Session Discipline: The Real Signal of the Regular Season2026-10-01
The Twelve Overs Before the Second New Ball: The Chapter of Bangladesh's Test Wins the Scorecard Never Writes2026-10-02
The 19-Run Margin That Lies: Where India's Asian Games Final Was Actually Decided2026-10-04
The Mullanpur Ledger: A 352 Chase Finished With 10 Balls To Spare, Yet India Were Four Overs Short — The Arithmetic of ICC Article 2.22 and Two Captains' Silent Acceptance2026-10-06
The Final Over Was Written Before the Ball Was Bowled: A Tactical Reading of the Bridgetown Final2026-10-02
Recommended
When the Record Goes Missing: Cricket's Data Crisis and the Blockchain Promise2026-10-05
A Finger, A Shield Called Jangoo, and the Math of Five Matches: West Indies' Squad Ledger Before the India T20Is2026-10-06
Integrity of the Decision Log: The Case for Blockchain-Backed Records in Cricket Officiating2026-10-07
When the Data Goes Silent: DRS, Empty Payloads and Cricket's Invisible Verdicts2026-10-06
The Contracts That Never Make Headlines: Inside the Dark Ledger of BPL Retention2026-09-29
