The Mullanpur Ledger: A 352 Chase Ended in 48.2 Overs, Yet Four Overs Stayed Missing — India Fined 20%, West Indies 10% for Slow Over-Rate

The Mullanpur Ledger: A 352 Chase Ended in 48.2 Overs, Yet Four Overs Stayed Missing

It was half past seven in the evening. The floodlights at the Maharaja Yadavindra Singh International Cricket Stadium were still on, but nobody was watching the last digit on the scoreboard anymore. West Indies had chased down 352 in 48.2 overs — the match was over, ten balls to spare. And right at that moment, a separate calculation began at the match referee's desk, one that never appears on the scoreboard, never shows up in a television graphic, but stays in the ledger of the game forever.

The result of that calculation arrived on Wednesday evening. Article 2.22 of the ICC Code of Conduct for Players and Player Support Personnel — slow over-rate — was applied against two captains. India's Shubman Gill, West Indies' Shai Hope. Five percent of the match fee for every over short. India bowled four overs short — a 20 percent fine. West Indies bowled two overs short — ten percent.

The ledger remembers what the highlight reel forgets.

The highlight reel will remember the 352 chase — sixes on a flat deck, boundaries, half-centuries and a century clip. A 700-run match. West Indies' batters never let go, and the crowd stood up in the final overs. That is the reel version. But the slow over-rate sanction is a different layer hidden inside that story — a sediment layer. I went looking for a score and found a sediment layer.

I have seen this same scene many times on Chattogram grounds. The match ends in the evening, but the over count does not add up. The coach's face then carries one line — "part of the process." I never believe that line. Because the clock does not understand jokes. If a chase ends in 48.2 overs, it means 290 legal deliveries were bowled, yet more than five hours were consumed. The name of that gap is the most neglected crime in modern cricket — the crime of time.

This piece is about that crime of time. And I begin not with the scorecard but with a blank column kept beside it — the column nobody fills, yet the one that holds the most truth in every match.

---

First, the context of a match

The venue needs to be recognised first. Mullanpur — New Chandigarh, the soil of Punjab. High scores have come here before, but an aggregate of 700 runs sends a message: the wicket was made for batting. The ball does not seam, the spinners get no grip, and runs come through the drive. On this kind of deck, fast bowlers look for alternatives, captains change bowlers every three overs, and field placements shift again and again. And every change costs time.

West Indies' second-innings chase was the product of a precise plan. A 352 target is not small in modern cricket. Chasing that on an Indian home deck, against a spin-heavy Indian attack, means knowing the boundary rope well. To finish it in 48.2 overs means the West Indies batting unit could not breathe until the final over, but it did not stop. That is a big signal for a mid-tier side.

But the question here is not about batting. The question is this — how did India, in a match that ended with ten balls to spare, bowl four overs short?

That is the real puzzle. And that is the heart of this news.

---

The over-rate calculation: brutally simple arithmetic

I always suspect a number until it matches in two places. Here it matched.

Article 2.22 of the ICC Code sets the penalty for a slow over-rate — five percent of the match fee for every over a team fails to bowl within the allotted time, after time allowances. There is no discretion, no room for interpretation.

India four overs short. Four times five equals twenty percent. West Indies two overs short. Two times five equals ten percent.

These two numbers did not come from the match referee's mind, they came from the rule. That is the most important feature of the sanction. If the fine were discretionary, questions of bias would arise. But here the arithmetic says — India was, on paper, twice the offender of West Indies.

In my notebook this fact will be written in large letters, because this is where the story turns. The home team, in familiar conditions, with familiar umpires, with everything familiar — yet it was the one with the bigger shortfall.

The tape does not lie; it only waits to be excavated.

---

The umpiring chain: who saw, who reported

The weight of a sanction depends on the weight of its documentation. Here the documentation is clear.

The charges were levelled by the two on-field umpires — Jayaraman Madanagopal and Sam Nogajski. Third umpire Sharfuddoula. Fourth umpire Virender Sharma. And the sanction was levied by match referee Prakash Bhatt.

I want to remember these names. Because cricket's memory usually remembers batters and bowlers, but forgets the officials. Yet the structure of the record is built in their hands. When a match referee places the five-percent calculation on the table, it is not just a fine — it is a precedent. A future youth player, who will one day rise to the national team, will read this precedent and learn that the clock does not forgive.

I keep a ledger for a youth side in Chattogram. Every match records how many minutes each player stood in the field, how many times a bowler changed ends. Because if that habit is not built young, at the big stage it gets deducted from the match fee. This India-West Indies sanction is therefore not just about two teams — it is a lesson for the whole system.

---

The captain's burden: not skill, but discipline

One misconception needs clearing here. An over-rate fine is not a measure of skill. It is a measure of accountability.

Shubman Gill and Shai Hope — both accepted the sanction, and neither took the path of a formal hearing. That is a mature decision. Because a hearing would have cost more time and added to team instability. Both captains wanted to signal that the delays were their own.

But here a pattern appears, which I noted separately.

Shai Hope's side took its second over-rate fine in three months. Ten percent in this match, and five percent against New Zealand in July. Two data points cannot settle a big conclusion — I say that upfront. But there is a hint of a pattern here. West Indies' ODI bowling management may have a systemic time problem, not merely a single-match lapse.

In Shubman Gill's case the calculation is different. He is a new full-time ODI captain. In December 2026 at Raipur, the team was fined ten percent against South Africa, which aligns in time with his tenure. This twenty percent at Mullanpur is the first clear ink on his home record. For a new captain it is the cost of learning leadership, but it is also a warning — a big shortfall in familiar conditions means a problem in the habit of bowling changes.

I have seen many youth captains who win a trophy and then lose the next year on the fitness column. Because nobody taught them — leadership is not only setting the field, it is also managing the clock.

---

First contrarian view: why the home team was the biggest offender

Now I come to the place where the normal expectation collapses.

The normal assumption is — the home team is the most disciplined. Familiar wicket, familiar weather, familiar umpiring environment, even the crowd. The visiting side usually wastes time — adjusting to a new environment, setting fields, changing bowlers.

But at Mullanpur it was the reverse. India fell four overs short, West Indies two. The home team was twice the offender.

Is this merely coincidence? It could be. One match cannot define a team's discipline culture — I accept that limitation. But it is a signal that cannot be ignored.

I remember 2026. The coach of Chattogram Abahani's Under-19 side suddenly introduced a 3-4-3 formation. I waited two weeks, then wrote after seeing ten matches of data. Goals rose by twelve percent, but goals conceded on the counter rose by eighteen percent. The number taught me — process and outcome are not the same thing.

The same lesson applies here. India's four-over shortfall may be behind multiple stoppages — DRS reviews, injury checks, bowling-change conferences, field resets. Not one big delay, but many small ones. And small delays are the most dangerous, because nobody notices them.

A formation is proven only when the youth team proves it. Here that youth team was India's bowling unit — and it did not prove it.

---

Second contrarian view: DRS, two new balls and spin — the ODI format's inherent flaw

A large part of the over-rate problem is not a team's fault, but the format's.

Of the three international formats, the ODI is the most at risk of a slow over-rate. Why? In ODIs two new balls are used per innings — meaning seam movement from both ends and a temptation to change bowlers repeatedly. On top of that, spin changes in the middle overs, fielding restrictions, and the number of DRS reviews in modern cricket. Every review costs minutes. Every spin change costs overs.

In T20 the problem is far smaller, because there are fewer overs and the game is faster. Tests are a separate calculation. But the ODI — this is the format that fights time the most.

One point is clear here. In a match where 352 runs are scored, bowlers can never bowl at ease. Every boundary means a sprint to fetch the ball, every big shot means a field reorganisation. When the wicket favours the batter, the over-rate naturally drops.

So the question — is it fair to fine anyone for this inherent flaw of the format?

My answer — yes, it is fair. Because everyone knows the rule. The format is hard, and in a hard format discipline is needed even more. But at the same time the question should be kept — has the ICC ever thought of going beyond this rule to change the format itself? Innings-time caps, stricter in-match penalties — these may come into discussion in the future.

Every academy pitch is an archaeological site with floodlights. Dig into the layers there, and you see that a time problem is never built in a day. In the ODI format that layer has been accumulating for years.

---

Third contrarian view: broadcast interest and the game's interest are not the same

One angle few write about. Who is the biggest loser from a slow over-rate?

Not the viewer. The viewer rather enjoys it — more game, more time. The loser is the broadcaster, with fixed slots for fixed programming. If an ODI runs half an hour beyond its scheduled time, the next programme shifts, the advertising calculation goes awry.

I moved from the radio era into the television era. I have seen how a schedule is not a journalistic document but a commercial one. So the ICC's strict over-rate policy does not only protect the game's discipline — it protects broadcasting's commercial structure.

This is a meeting of two interests. The fairness of the game and the schedule of the broadcast both gain from the same rule. This is why I believe over-rate rules will grow stricter in the future — because commercial pressure is not decreasing, it is increasing.

---

West Indies' chase: batting works, discipline does not

Now I return to the cricketing side of the match, because the ledger and the bat tell a fuller picture only when seen separately.

Chasing 352 in India is no small thing. In Indian home conditions, on spin-friendly decks, in Asian conditions — Caribbean sides have historically been uncomfortable here. But in this match West Indies' batting worked. A chase in 48.2 overs means batting to the end with breath held, not collapsing.

That is a clear signal — West Indies' ODI batting is effective even in a transition phase. Yet their game-management discipline still lags. That is, one hand of the team works, while the other leaves a stain on the ledger.

I have seen this kind of contradiction before. In youth teams it is common — the boy bats brilliantly, but is slow in the field, slow to return the ball from the boundary, and that later punishes the team. West Indies' two-over shortfall is probably the same — one or two bowlers returning slowly, repeated end changes.

More important — two offences in two to three months means this is no longer a personal mistake, it is a hint of a habit.

The silent XI are not absent; they are unindexed. Likewise, West Indies' discipline problem is not invisible; it is simply not written on the scorecard.

---

India vs West Indies: two pages of one old ledger

To understand this sanction, the series must be placed in the strata of history.

I have been reading cricket ledgers since the 1960s. In the 1970s and 80s, West Indies were the most feared side in the world. In those years they came to India and won, because their pace attack was from another planet. In my early notebooks it is written — that Caribbean side ruled both ODIs and Tests.

In the modern era the picture is reversed. India are a leading ODI power, West Indies historically sit outside the top six. In this series West Indies chased 352 to win — a fruit standing against that historical current.

But here is the real lesson. The ledger remembers not only the outcome, but how the outcome came. In this match the outcome was West Indies', but on the ledger's discipline column they lag. And India's batting depth showed a 350+ score, yet the bowling discipline left four overs blank.

Two separate truths, in one match.

---

The gap between ranking and expectation

There is a gap between expectation and reality here, which matters in analysis.

The expectation was — India win at home, West Indies struggle. The reality was — West Indies won, India lagged in time management.

The expectation was — the home side stays clean on over-rate. The reality was — India was the biggest offender.

Putting the two gaps together, one thing stands — this ODI leg was competitive, not one-sided. A 700-run match, a 352 chase, both sides under bowling pressure.

I learned past sixty that outcome and discipline are not one. A team can win and still have ink on the ledger. And a team can lose and still keep a clean ledger. At Mullanpur both sides were fined, but the batting scorecard wrote only one team's name.

---

From the youth system's view: today's fine, tomorrow's habit

Now I look from my own place — from the mine of youth cricket.

Do youth players learn from a national team's over-rate fine? The answer — rarely. They learn from the coach's scolding, from the fear of the bench, from the arithmetic of a cut match fee.

I introduced a rule at a Chattogram academy — a minute log every match. How much time went in which over, how much time a bowler change took, how much a field reset cost. At first the coaches laughed. Three months later they were asking for that log.

The reason is simple. An over-rate is not a one-day crime, it is the result of a habit. The boy who returns the ball slowly from the boundary at Under-16 will return it slowly at Under-19, and at the national team it will be cut from the match fee.

Article 2.22 of the ICC Code is therefore more to me than an administrative rule. It is a mirror that shows the whole system — discipline is taught at the lower level, and the reckoning is taken at the upper level.

---

The technical side of bowling management

Now let me descend to the technical level, because the real causes hide there.

In modern ODIs four big reasons sit behind a falling over-rate.

First, the number of bowling changes. On a flat deck a captain changes bowlers every two or three overs. Every change costs time — the new bowler walks to his end, the field is set, the captain talks to him.

Second, DRS reviews. A review means a big screen, a third umpire, a decision, then the game restarts. Two or three reviews can eat the time of one over.

Third, injuries and physio breaks. Occasionally a bowler cramps, a concussion check, or a small injury stops play. Every stoppage costs time.

Fourth, fielding restoration. A lost ball, adjusting the boundary rope, changing the wicket-keeper — each is a small gap.

Mullanpur's four-over shortfall is probably a mixture of these four. Not one single cause. And that is why it is hard to detect — because there is no single big delay, there are many small ones.

I have seen many times that coaches scold for the big delay but skip the small ones. Yet the real loss is in the small ones.

---

Format comparison: ODI, T20 and the fight with time

A comparison is needed in the context of the upcoming T20 series, because this is where we see how much the format matters.

In T20 the over-rate problem is far smaller. Because — only twenty overs, a fast game, no two new balls, fewer spin changes. So sanctions are rare in T20.

The ODI — fifty overs, two new balls, a middle spin phase, more DRS. Here the risk is highest.

The Test — a separate calculation, because time is measured there by a different method.

So we understand why this sanction came in an ODI, and why it will probably not come in the coming T20 series.

The T20 series that begins next Tuesday, October 6, in Lucknow — there this discipline question may fade into the background. But the ledger will not forget. This twenty percent will stay on the Indian captain's record, and the two-time pattern will stay on West Indies' record.

---

Risk map: which is small, which is big

I always divide risk into layers. There are three layers here.

First layer, minor — this match's fine itself. Five percent per over is a small figure relative to the match fee. It is a signal, not a devastating punishment.

Second layer, medium — India's four-over shortfall on a home deck. This is a discipline signal, which if repeated could turn into a captaincy question.

Third layer, the most important — West Indies' repetition. Two in three months. If a third comes in the coming months, penalties can rise under the rule, and in serious repeated breaches the path to a captain's suspension can open. This is the most durable risk of this news.

Putting the three together, I will say one thing — pattern matters more than result. A result belongs to one match, a pattern belongs to months.

---

Public narrative: which story survives, which story fades

The easiest angle — "the home team was fined more." Immediate, curious, easily viral.

The most durable angle — "West Indies, two in three months." Less flashy, but more significant.

In my experience I have seen that flashy stories die in two days, but pattern stories return month after month. In 2026, when I wrote about the closure of Chattogram Abahani's Under-18 side, nobody found it flashy. But the five-year ledger was there, and that is why it survived.

Mullanpur's sanction is the same — the first day's news is small, but the ledger is big.

---

From broadcast to ecosystem: where the impact is, where it is not

Now the question — what is the economic impact of this sanction?

Honest answer — very little.

This is no league, no auction, no broadcast-rights deal. It is an administrative event of a bilateral international series.

But there is one link. Over-rate control protects the broadcast schedule. And protecting the schedule means protecting advertising slots. So indirectly the ICC's strictness serves broadcasters' interests.

And one possible long-term effect — if the over-rate problem grows in ODIs, demands for format reform will grow. Innings-time caps, in-match penalties, or other measures — these may come into discussion. Then this match will also serve as a precedent.

I do not want to bet, because betting is not my profession. But the ledger says — when commercial pressure rises, rules grow stricter.

---

ICC Code 2.22: what the rule says, and why it matters

Let me write the rule once in simple language, because it will be needed later.

Article 2.22 — slow over-rate. Definition: five percent of the match fee for every over a team fails to bowl within the allotted time (after time allowances).

Match referee — the one who levies sanctions for Code breaches. Here, Prakash Bhatt.

Over — six legal deliveries by one bowler.

Chase — the second innings' effort to overhaul the first innings' score. Here West Indies chased 352.

ODI — a 50-over per side, two-team match.

These definitions must be remembered, because the same rule will come in many more matches in the future.

---

Defensive balance: where I stay careful

I know my biggest weakness — excessive trust in documents, and suspecting every decision.

In this match I want to manage that.

On West Indies' repetition I will say — this is a hint, not a proven habit. Reaching a big conclusion from two data points is not right.

On India's four overs I will say — this is a one-match discipline caution, not a systemic failure. A big shortfall in familiar conditions catches the eye, but one match cannot judge a team.

So I will use the careful words — probably, perhaps, not proven. Because treating every ledger as a crime, like a prosecutor, leads to error.

---

A forward date: October 6, Lucknow

The next chapter of this story begins on Tuesday, October 6, in Lucknow — the first of a five-match T20 series.

In T20 the over-rate problem is smaller, so probably no new sanction will come here. But the psychological side is different. India's captain enters the series with a stain. West Indies enters with a win and a pattern-caution.

Every series is a new layer. What we saw in the ODI leg — competition, high scores, and administrative neglect. In T20 we must see whether the competition stays, and whether discipline returns.

---

Final word: the ledger stays open

I did not start reading cricket ledgers at twenty-seven. Past sixty, I still keep a separate calculation after every match — which column stayed blank.

At Mullanpur one column stayed blank. India bowled four overs short, West Indies two. Twenty and ten. Both captains accepted the sanction. No hearing took place. The match referee decided alone.

This is small news. But the ledger does not remember small news, the ledger remembers only the truth.

The truth is — in one match 352 runs were scored, 700 runs came, the crowd stood up, and yet both sides lost to time.

West Indies won the match, but a pattern was deposited in their name. India lost the match, and the biggest shortfall was deposited in their name — at home, in familiar conditions, four overs.

Keeping these two truths together shows — in cricket, the score and the discipline are two separate games. One wins one, another wins the other.

The biggest proof may come a few months later. If West Indies are caught on over-rate again, today's two overs will be marked as the first page of a pattern. And if India's four overs repeat, it will become a discipline question that enters captaincy discussion.

I will wait. Because the ledger stays open, and time always finishes its own calculation.

And yes — I will keep the scorecard of the October 6 Lucknow match separately. Whether the over-rate column stays blank there will tell whether tonight was just a small fine, or the start of a bigger habit.

The ledger remembers. We only forget.