HomeWorld CricketWhere the Ledger Starts and the Highlight Reel Ends: India and West Indies Fined for Slow Over-Rate at Mullanpur

Where the Ledger Starts and the Highlight Reel Ends: India and West Indies Fined for Slow Over-Rate at Mullanpur

**মূল উত্তর**: আইসিসি কোড অব কন্ডাক্টের ধারা ২.২২ অনুযায়ী মুল্লানপুরের তৃতীয় ওয়ানডেতে ধীর ওভার-রেটের জন্য ভারত ম্যাচ ফির ২০% ও ওয়েস্ট ইন্ডিজ ১০% জরিমানা গুনেছে; ভারত চার ওভার ও ওয়েস্ট ইন্ডিজ দুই ওভার কম বলেছিল, এবং দুই অধিনায়কই শাস্তি বিনা শুনানিতে মেনে নেন। **মূল তথ্য**: - ভারত চার ওভার কম বলায় ২০% ও ওয়েস্ট ইন্ডিজ দুই ওভারে ১০% জরিমানা; ধারা ২.২২-এ প্রতি ঘাটতি ওভারে ৫%। - ওয়েস্ট ইন্ডিজ ৩৫২ রান ৪৮.২ ওভারে তাড়া করে জেতে, দশ বল বাকি থাকতেই ম্যাচ শেষ হয়। - ম্যাচ রেফারি প্রকাশ ভট্ট শাস্তি আরোপ করেন; মাঠের আম্পায়ার জয়ারামন মদনগোপাল ও স্যাম নোগাইস্কি। - ওয়েস্ট ইন্ডিজের এটি তিন মাসে দ্বিতীয় জরিমানা; জুলাইয়ে নিউজিল্যান্ডের বিরুদ্ধে ৫% (সঠিক বছর যাচাই বাকি)। - ভারতের আগের দৃষ্টান্ত: ডিসেম্বর ২০২৫-এ রায়পুরে দক্ষিণ আফ্রিকার বিরুদ্ধে ১০% জরিমানা। **সূত্র**: আইসিসি কোড অব কন্ডাক্ট, ধারা ২.২২; ম্যাচ রেফারির প্রতিবেদন, অক্টোবর ২০২৬। **সম্পর্কিত প্রশ্নোত্তর**: প্রশ্ন: ভারত ও ওয়েস্ট ইন্ডিজ কত শতাংশ জরিমানা গুনেছে? উত্তর: ভারত ২০% ও ওয়েস্ট ইন্ডিজ ১০%, কারণ ধারা ২.২২ অনুযায়ী প্রতিটি ঘাটতি ওভারে ৫%। প্রশ্ন: ওয়েস্ট ইন্ডিজের ওভার-রেট সমস্যা কি পুনরাবৃত্ত? উত্তর: হ্যাঁ, তিন মাসে এটি তাদের দ্বিতীয় শাস্তি, যা Bowling পরিবর্তনের গভীরতা-সংক্রান্ত দুর্বলতার দিকেই ইঙ্গিত করে (সহায়ক তথ্য: cricsultan.com Player Depth Index)। প্রশ্ন: আসন্ন টি-টোয়েন্টি সিরিজে ওভার-রেট ঝুঁকি কতটা? উত্তর: কম, কারণ টি-টোয়েন্টিতে ওভারসংখ্যা ও সময় দুটোই সীমিত; পাঁচ ম্যাচের লেগ শুরু ৬ অক্টোবর, ২০২৬, লখনউতে।

Where the Ledger Starts and the Highlight Reel Ends: India and West Indies Fined for Slow Over-Rate at Mullanpur

The scoreboard was telling a different story. At the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur, West Indies chased down 352 in 48.2 overs, with ten balls still in hand. The two sides together produced close to seven hundred runs on a batting-friendly deck. And yet, in that same match, India bowled four overs short. When a game ends before its scheduled finish, the natural alibi for a slow over-rate disappears. That is where my arithmetic begins.

The ledger starts where the highlight reel ends.

The context is the third and final ODI of the bilateral series between India and West Indies. A seven-hundred-run aggregate tells you the pitch gave the bowlers very little. In the 50-over format, such a deck manufactures a familiar problem: two new balls, mid-innings spin changes, and a growing pile of DRS reviews — each one a small delay. The over-rate risk is highest in ODIs, not in Tests or T20Is. The five-match T20I leg begins immediately after, with the opener in Lucknow on Tuesday, October 6, 2026. That is a different format — fewer overs, faster rhythm — so the T20I results cannot be used to judge the ODI discipline, and the reverse is equally true.

According to the match referee's record, India bowled four overs short and West Indies two. The two captains, Shubman Gill and Shai Hope, accepted the sanctions; no formal hearing was required. That is the first signal — the delays were self-inflicted, and both sides acknowledged it.

Where the Ledger Starts and the Highlight Reel Ends: India and West Indies Fined for Slow Over-Rate at Mullanpur

Now open the ledger. Under Article 2.22 of the ICC Code of Conduct for Players and Player Support Personnel, a team that fails to bowl its overs in the allotted time is fined five per cent of its match fee for every over short. The arithmetic is simple: India 4 × 5% = 20%; West Indies 2 × 5% = 10%. The penalty is rule-derived, not discretionary. The charges were levelled by on-field umpires Jayaraman Madanagopal and Sam Nogajski, third umpire Sharfuddoula and fourth umpire Virender Sharma; the sanction was imposed by match referee Prakash Bhatt. The chain is clean, and the controversy is close to zero. What matters more is what the numbers imply rather than what they announce.

But the real work of a ledger is not counting numbers; it is finding the gaps between them. The gap here is the asymmetry: India, the home side, playing in familiar conditions and inside the tolerance of home umpires, fell into twice the shortfall of the visiting West Indies. The image of elite-side discipline we like to keep in our heads takes a knock from this single match.

On the West Indies side there is another signal, and it is not a one-match event. This is their second fine in three months — five per cent against New Zealand in July. Two data points cannot declare a culture, and I will not step into that trap. But when the same error arrives twice in a row, calling it an accident becomes difficult. India's own precedent was ten per cent in the Raipur ODI against South Africa in December 2026.

This is where my comparative bridge earns its place. Since 2026 I have kept a Dhaka age-group ledger — 48 Under-16 matches at the Bir Sherestha Shaheed Shipahi Mostafa Kamal Stadium, three Dhaka leagues, 72 players born between 2026 and 2026, ten metrics for each: minutes, touches, sprints, pass accuracy. There is no column called over-rate. Because over-rate is not a skill indicator; it is an administrative entry, a matter for the match referee's diary, not the scout's notebook.

Every template hides a childhood the scouts never filed.

An English county academy and a Bangladeshi age-group route — BKSP, the National Cricket League, Under-19 camps — are two different filing methods. One records bowling load; the other records matches played. The county route builds the habit of rotating bowlers; the Bangladeshi route builds the capacity to carry long spells in heat on flat decks. Both ledgers push one question off the edge — who is slow, and why. Over-rate is neglected in both systems, because neither treats it as a forecast. Yet the question is simple: without holding minutes, overs and delays in the same ledger, the history of discipline cannot be written at all.

There is also a commercial edge to this administrative entry that rarely makes the discussion. A slow over-rate strikes directly at the broadcaster's fixed slot: stretching a game past the window in which advertising was sold throws the channel's schedule out of shape. That broadcasting interest in strict enforcement is an inference, but a reasonable one.

Years of watching matches from the ground build a habit of reading over-rate not as a single moment but as an accumulation — one review, one injury check, one field change, then another. Mullanpur's four-over shortfall is therefore probably not one long delay but the sum of many short ones. That is inference, not proof; still, such sums belong in the ledger, because it is exactly this pattern that returns in the next match.

I dig beneath the transfer fee for the fossil record.

Now the contrarian turn. The news of the fine usually ends in a single sentence: "both teams were penalised." The ledger says otherwise: this is primarily India's story, and it happened at home. West Indies were two overs short, India four — the visiting side won the match, and the host side took the heavier penalty. That inverted arrangement is the part that most needs saying.

I am deliberately not forcing my favourite three-stage frame onto this — break, repair, return. The event does not fit the mould, because nobody was injured and nobody came back. This is a game-management account, not an injury story. The story that breaks my template still has to be written; on that principle I do not bend.

Over-rate complaints are often used as a weapon to hide selection failures. But whoever raises the complaint, each claim must be audited on its own numbers. After the audit, what remains is this: India's four-over shortfall is true, West Indies' repetition is true, and the rest is inference.

Looking forward, two signals stand out. First, if West Indies commit the same error a third time in the coming months, the penalties can escalate — a captain's suspension risk cannot be ruled out. Second, this is the first home-soil blemish on Gill's captaincy record; a repeat in the T20I leg will widen the questions. The ledger does not stop. It simply waits to see who writes the next entry.

Related Players