World CricketAt Home, India Were the Bigger Offender: Inside the Slow Over-Rate Sanctions at Mullanpur
At Home, India Were the Bigger Offender: Inside the Slow Over-Rate Sanctions at Mullanpur
**মূল উত্তর:** ভারত ও ওয়েস্ট ইন্ডিজকে মুল্লানপুরে তৃতীয় ওয়ানডেতে স্লো ওভার-রেটের জন্য জরিমানা করা হয়েছে; ভারত ২০ শতাংশ (৪ ওভার কম), ওয়েস্ট ইন্ডিজ ১০ শতাংশ (২ ওভার কম), আইসিসি কোডের আর্টিকেল ২.২২ অনুযায়ী প্রতি ওভারে ম্যাচ ফির ৫ শতাংশ। **মূল তথ্য:** - ওয়েস্ট ইন্ডিজ ৪৮.২ ওভারে ৩৫২ রান তাড়া করে জেতে, দশ বল বাকি রেখে। - ভারত চার ওভার কম বল করেছে—জরিমানা ২০ শতাংশ; ওয়েস্ট ইন্ডিজ দুই ওভার কম—১০ শতাংশ। - জরিমানা চাপিয়েছেন ম্যাচ রেফারি প্রকাশ ভাট; কোনো শুনানি ছাড়াই দুজন অধিনায়ক শাস্তি মেনে নেন। - ওয়েস্ট ইন্ডিজের গত তিন মাসে এটি দ্বিতীয় শাস্তি—জুলাইয়ে নিউজিল্যান্ডের বিপক্ষে ৫ শতাংশ। - সামনে লখনউতে ৬ অক্টোবর থেকে পাঁচ ম্যাচের টি-টোয়েন্টি সিরিজ শুরু। **সূত্র:** আইসিসি কোড অব কন্ডাক্ট আর্টিকেল ২.২২; প্রতিবেদন প্রকাশিত ২০২৬ সালের অক্টোবরের শুরুতে | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: ভারত কেন ওয়েস্ট ইন্ডিজের চেয়ে বেশি জরিমানা পেল? উত্তর: ভারত চার ওভার কম বল করায় ২০ শতাংশ, আর ওয়েস্ট ইন্ডিজ দুই ওভার কম বল করায় ১০ শতাংশ জরিমানা পেয়েছে। প্রশ্ন: ওয়েস্ট ইন্ডিজ কি আগেও এই শাস্তি পেয়েছিল? উত্তর: হ্যাঁ, জুলাইয়ে নিউজিল্যান্ডের বিপক্ষে ৫ শতাংশ জরিমানা খেয়েছিল, যা cricsultan.com Player Depth Index-এ শৃঙ্খলা-ধারা হিসেবে চিহ্নিত। প্রশ্ন: বারবার ওভার-রেট অপরাধে কী হতে পারে? উত্তর: জরিমানা বাড়তে পারে এবং গুরুতর বা পুনরাবৃত্ত ক্ষেত্রে অধিনায়কের নিষেধাজ্ঞার সম্ভাবনা তৈরি হয়।
On the Mullanpur pitch the ball rolled for 48.2 overs. The second innings finished before the scheduled 50. Yet the news after the match was that India had bowled four overs short and West Indies two. In a match that ended early, it was the home side that left the most overs unbowled. While the scoreboard was stacking up a 352-run mountain, the dressing-room clock was keeping a different ledger. I opened the half-space ledger and found that the ghost in the channel here was not runs—it was time. When the winning side does not hurry and the losing side bowls quickly, the usual logic of over-rates turns upside down. That is exactly the picture here. To me this asymmetry is the most intriguing signal—not the pressure of defeat, but the habit of slow play in comfortable home conditions.
To understand the context you have to look at the format. The ODI—50 overs a side—is the most over-rate-vulnerable of the three formats: two new balls, frequent mid-innings spin changes and long DRS review breaks all combine to make it a slow game by nature. T20 has fewer overs and moves faster; a Test counts time differently. So I have kept every judgement here anchored to the ODI format. No Test or T20 performance data is mixed in. The T20 series coming up is a separate format context and must be treated as such.
The bare facts: at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur (New Chandigarh, Punjab), in the third and final ODI, West Indies chased 352 to win in 48.2 overs, with ten balls to spare. India batted the full 50 overs. Yet India bowled four overs short, West Indies two. A near-700-run aggregate across both innings points clearly to a flat, batting-friendly surface. On such a deck innings run long, boundary-chasing means more running, and bowling changes multiply—the game naturally slows.
The arithmetic of the fine, however, is straight and mechanical. Under Article 2.22 of the ICC Code of Conduct, a team is fined five per cent of its match fee for every over it fails to bowl on time. India four overs short—four times five, i.e. 20 per cent. West Indies two overs short—two times five, i.e. 10 per cent. The maths checks out completely. The penalty is rule-derived, not the referee's whim. That clarity is rare and it makes the incident transparent.
Where does the accountability sit? An over-rate fine is never a skill metric—it is a captaincy-accountability metric. Here it landed on India captain Shubman Gill and West Indies captain Shai Hope. Both accepted the sanction and did not seek a formal hearing: a pragmatic, low-conflict resolution. Either could have demanded a hearing; not doing so means they at least implicitly conceded the delays were self-inflicted.
This is where the real story hides, and it plays in two different keys. The first is West Indies'. This is their second sanction in three months—five per cent against New Zealand in July, now 10 per cent. That is not a one-match lapse; it is a pattern. When a side repeatedly loses time it usually signals one of two things: inexperienced bowling leadership, or a pace attack so thin that bowlers must be changed often. Either way the problem is off-field, in management.
The second key is India's, and it is the more striking. Elite home sides are usually the most over-rate-disciplined—familiar conditions, familiar umpires, familiar routines. Yet here they left the most overs unbowled. Gill is relatively new to full-time ODI captaincy; India were fined 10 per cent against South Africa in Raipur in December 2026, close to his tenure. For a new captain this is a leadership-learning risk, and it should be read as a single-match settling-in, not a permanent trend. One ODI cannot define a team's discipline culture.
The surprise, of course, is elsewhere. The visiting side—historically rated weak away from the Caribbean, especially in Asian conditions—chased 352 in India to win. That is a big result against home expectation. But note that despite winning, West Indies bowled two overs short, while the losing India bowled four. Result and discipline did not walk the same road. West Indies' ODI batting is working; their game-management discipline is not.
Here is where I part with the conventional read. Everyone will naturally say: the side that chased 352 was excellent, and the side that lost was bad at everything. But I do not trust a heat map until it argues with my eyes. What my eyes see is that the biggest story of this match is not the result but a governance-and-discipline signal. West Indies won, yes—but two over-rate fines in three months since July means there is a leak off the field. India lost, but what speaks louder than the defeat is their four-overs-short at home. The gap of the winning side and the gap of the losing side must be seen separately.
Another thing many skip—over-rate control is directly tied to broadcast interest. A broadcaster has a fixed schedule; a game dragging on breaks it. So strict over-rate enforcement protects not only the game's beauty but the integrity of the commercial schedule. The link is indirect but real.
The enforcement machinery runs cleanly. Match referee Prakash Bhatt laid the charges and the fine; the on-field umpires were Jayaraman Madanagopal and Sam Nogajski, the third umpire Sharfuddoula, the fourth Virender Sharma. Charge to sanction—the whole chain is documented and named. That is why controversy here is near zero.
Yet the risk exists, and it leans toward West Indies. Under the ICC framework, repeated over-rate offences do not merely raise fines—in the most serious or repeated cases, suspension of the captain becomes possible. So if West Indies commit a third such lapse in the coming months, it will no longer be a matter of counting money. By contrast, I read India's four overs short as a single-match cautionary flag, not a structural crisis.
Looking forward, one thing is clear. The five-match T20 series begins at Lucknow on Tuesday, October 6—far less over-rate-prone than the ODI, because fewer overs move faster. Yet India enter it with a discipline blemish on the captain's record, and West Indies enter it holding both the confidence of victory and the count of a fine. My eyes will be on two places: whether Shai Hope's side lose time a third time within six months, and whether Gill's side correct themselves in the over-rate ledger at home. Everyone remembers the result; very few remember the clock's ledger. But often it is that ledger which tells you first just how ready a team really is.



Related Players
Recommended
How the Asian Games Bronze Masked Sri Lanka's Fractured Top Order2026-10-04
Cricket on the Blockchain Ledger: The Price of a Six, and the Moment With No Witness2026-10-03
When the Analysis Pipeline Returns Null: A Post-Mortem of Cricket Data's Silent Failure2026-10-05
The Formation of Silence: Khulna's Cricket Ledger, the Arithmetic of BPL Money, and a Bedsheet Screen2026-10-02
From Pressing Audit to Pipeline: The Quiet Rebuild of Cricket Data in the Regular Season2026-10-03
Recommended
When Cricket's Injury Records Meet Blockchain: The Lost Transparency of Load Management2026-10-02
The Language of a Null Result: Autopsy of a Cricket Analytics Pipeline2026-10-04
The Pulse of the Dressing Room: The Stories Nobody Wrote From Sheikh Russel's 84 Sessions2026-09-30
From 21/4 to 63 Runs: Where Litton Das's 'No Point in Resigning' Breaks Down2026-10-04
The Silent Third-Innings Collapse: A Data Autopsy of Bangladesh's Test Batting Log2026-09-29
Recommended
Twenty-One Overs, Six Days, Four Knees: The Open Ledger of Bangladesh's Pace Load in the NCL2026-10-02
Blockchain in Cricket Ecosystem: A New Dimension of Transparency2026-10-01
The Auction Arithmetic: Why the Most Expensive Cricketer Is Rarely the Biggest Win2026-10-06
Waiting for the New Red Ball: Labuschagne's Century Is the Headline, Green's Strain Is the Story2026-10-05
Cricket's Economy Moves to the Blockchain Ledger: From Fan Tokens to Smart Contracts2026-09-29
The Integrity of an Empty Spreadsheet: Cricket Data Integrity, Blockchain and the Moral Duty of the Model2026-10-05
Recommended
NOC, Window and Wage Bill: Who Really Sets the Price in January's Franchise Market2026-10-03
The Testimony of a Blank Ledger: Data Integrity in Cricket Governance and the Quiet Role of Blockchain Ledgers2026-10-04
Priced in the Shadow of Drop-in Pitches: Why Anomalous-Condition Bowling Data Sells at the Wrong Price2026-10-01
Afghanistan's Night Was No Miracle — What the 240-Ball Ledger Says2026-09-30
Analysis Article Cannot Be Prepared Because the Source Article Is Missing2026-09-26
The Rise of Blockchain and Fan Tokens in World Cricket: From Club Ownership to the Era of Fans' Asset Rights2026-10-01
