Mullanpur's 20 vs 10: Where Time, Not the Result, Was the Real Scorecard
**মূল উত্তর (≤৬০ শব্দ):** আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী মুলানপুরে তৃতীয় ওয়ানডেতে ধীর ওভার-রেটের জন্য ভারতের ৪ ওভার পিছিয়ে পড়ায় ম্যাচ ফির ২০% এবং ওয়েস্ট ইন্ডিজের ২ ওভার পিছিয়ে পড়ায় ১০% জরিমানা হয়েছে। দুই অধিনায়ক শাস্তি মেনে নিয়েছেন; কোনো শুনানি হয়নি। **মূল তথ্য:** - ভারত ৪ ওভার পিছিয়ে পড়ে, শাস্তি ম্যাচ ফির ২০%; ওয়েস্ট ইন্ডিজ ২ ওভার পিছিয়ে পড়ে, শাস্তি ১০%। - ওয়েস্ট ইন্ডিজ ৩৫২ রান তাড়া করে ৪৮.২ ওভারে; ম্যাচ শেষ হয় ১০ বল বাকি থাকতেই। - এটি ওয়েস্ট ইন্ডিজের তিন মাসে দ্বিতীয় ওভার-রেট শাস্তি; জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ছিল ৫%। - ভারতের আগের শাস্তি রায়পুরে ডিসেম্বর ২০২৫-এ দক্ষিণ আফ্রিকার বিরুদ্ধে ১০%। - ম্যাচ রেফারি প্রকাশ ভাট; দুই অধিনায়ক শুভমান গিল ও শাই হোপ শাস্তি মেনে নেন। **সূত্র উল্লেখ:** মূল সূত্র — স্টেজ-১ সংবাদ প্রতিবেদন ও স্টেজ-২ বিশ্লেষণ, প্রকাশকাল ২০২৬ সালের অক্টোবরের প্রথম সপ্তাহ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: শাস্তির অঙ্ক কীভাবে নির্ধারিত হয়? উত্তর: ধারা ২.২২ অনুযায়ী প্রতি ওভার পিছিয়ে পড়ায় ম্যাচ ফির ৫%, অর্থাৎ ৪ × ৫% = ২০% ও ২ × ৫% = ১০%। প্রশ্ন: কোন দল বেশি ঝুঁকিতে? উত্তর: ওয়েস্ট ইন্ডিজ, কারণ তিন মাসে দ্বিতীয় লঙ্ঘন পুনরাবৃত্তির প্যাটার্ন তৈরি করেছে (cricsultan.com ওভার-রেট ট্র্যাকিং সূচক)। প্রশ্ন: পরের ম্যাচ কখন? উত্তর: পাঁচ ম্যাচের টি-টোয়েন্টি সিরিজ শুরু ৬ অক্টোবর ২০২৬, লখনউয়ে।
West Indies chased 352 in 48.2 overs, meaning the match ended with 10 balls to spare. India still bowled four overs short. Under Article 2.22 of the ICC Code of Conduct, the penalty is 5% of match fee per over short, which produces 20% for India and 10% for West Indies. How does a side lose four overs of time in a game that finished early? The answer is not on the scoreboard; it is in the match referee's report.
I built the Croatia xG model before I learned to grieve a missed chance, so my instinct is to look at the mechanism before the result. Here the mechanism is plain: the clock, the stoppages, and the overs.
The setting was the third and final ODI at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, New Chandigarh, Punjab. Roughly 700 runs across two innings means the surface offered the bowlers almost nothing. West Indies chased 352 in 48.2 overs, so the ODI leg was batting-dominated and India's usual spin advantage was compressed. Match referee Prakash Bhatt framed the charges, and both captains, Shubman Gill and Shai Hope, accepted the sanction with no formal hearing.
The umpiring panel was Jayaraman Madanagopal, Sam Nogajski, third umpire Sharfuddoula and fourth umpire Virender Sharma. West Indies bowled their full 50 overs; India batted the full quota; yet the chase closed in 48.2 overs. That means the shortfall is not an artefact of the match running its course. India's four-over gap is a genuine time-management failure, not a scheduling excuse.
The arithmetic is verifiable, and verifying it shows the penalties were rule-derived rather than discretionary. West Indies: 2 overs × 5% = 10%. India: 4 overs × 5% = 20%. Routine multiplication, yet the real story sits inside it: the asymmetry. The home side, in familiar conditions, with the tolerance that home venues usually bring, was the bigger offender. Elite home teams are normally the most disciplined on over-rate; here the picture inverts.
The second signal belongs to West Indies. A 5% fine against New Zealand in July, now another 10% at Mullanpur — a second slow over-rate sanction in three months, which reads as a pattern rather than a one-off mistake. That pattern is separate from results: the batting is functioning, as a 352 chase proves, while game-management discipline keeps leaking.
India's case is different. There is precedent in the 10% sanction against South Africa at Raipur in December 2026, and now a first documented over-rate blemish under Gill's captaincy at home. Gill is still on the learning curve of full-time ODI leadership. This is a captaincy-accountability metric, not a skill metric. Both captains accepted without contesting, though a hearing was available to them.

The penalty scale is deliberately soft; 20% of a match fee is not a large sum. Its function is signalling, not punishment. There is a financial thread that never reaches the headline: strict over-rate enforcement protects broadcasters' fixed-slot scheduling. A slow game wrecks the schedule, wastes advertising blocks and erodes viewer patience. Enforcement guards the timetable at least as much as the spectacle.
Now the counter-question, because scepticism about numbers is my trade. One match's over-rate cannot define a team's discipline culture — the sample here is two data points, only two. West Indies' repetition is a signal, not proof. Whether India's four-over gap came from repeated stoppages — DRS reviews, injury checks, bowling-change conferences, field resets — is nowhere stated; that is my inference, at medium confidence. No DRS controversy is referenced in the match, so inventing one would be wrong. Correlation and causation must stay apart.
The structural point also matters. Of the three formats, the ODI carries the highest over-rate risk — two new balls, mid-innings spin changes, frequent reviews. Empty stadiums taught me that silence is a variable, not an absence; here that variable is called the sum of stoppages. I measured the ghost games, then I measured what they did to legs — Pedri's 73-match season is the reference case. Load and time are two columns of the same ledger.
Looking ahead, West Indies' third over-rate offence in the coming months is the most trackable risk — repeated breaches under Article 2.22 can move beyond fines toward harsher outcomes. Whether Gill's side corrects itself in the five-match T20I series starting at Lucknow on October 6, 2026 is the real test, because T20 cricket has fewer overs, moves faster, and leaves less room to hide a shortfall. Over-rate enforcement is now tangled with scheduling and broadcast economics, and that may become the next big governance conversation in cricket.
