Those Four Overs at Mullanpur: The Story the Fine Arithmetic Buried

Some matches begin with a whistle; that one began with a held breath. The third ODI at Mullanpur was the second kind. At the Maharaja Yadavindra Singh International Cricket Stadium in New Chandigarh, ball-boys along the boundary rope were wiping sweat off their palms during the innings break, the scoreboard was stacking up close to seven hundred runs, and the ground clock seemed to be repaying time it had borrowed from someone. I was logging the match over by over—two pens, a backup recorder, and that small notebook from Rangpur that has sat in my pocket like a weapon since 2026.

The result was simple and brutally clean: West Indies chased 352 in 48.2 overs, with ten balls to spare. But where the result stops, the real story starts. After the match came the announcement—both teams were fined for a slow over-rate under Article 2.22 of the ICC Code of Conduct. India bowled four overs short: 20 percent of the match fee. West Indies were two overs short: 10 percent. Run the arithmetic: five percent per over, so four times five is twenty and two times five is ten. That the numbers add up is the biggest thing here—this was not a mood decision, it was a mechanical outcome of the rule.

Ground, Format and the Ledger

The 50-over format is the biggest arena of over-rate risk among the three. Two new balls at either end, spin changes through the middle overs, long waits at DRS reviews, field-setting conferences—together they make the clock run. A T20 has only 20 overs, less room for error; a Test measures time differently. The middle stretch of an ODI is the factory floor of slow over-rates.

The Mullanpur pitch was a batter's friend. Close to seven hundred runs across two innings means fours and sixes every over, long boundary retrievals, constant bowling changes. On such a surface the bowling side needs more time to finish overs—the ball keeps returning from the rope, fielders run further, the field must be reset after every boundary. And yet one thing deserves attention: West Indies finished the chase in 48.2 overs, meaning the match ended before the scheduled 50. India still bowled four overs short. This is not the excuse of a match running long; it is a pure time-management failure.

The series context matters too. This was the final ODI of a three-match series. Next comes a five-match T20I series, starting in Lucknow on Tuesday, 6 October 2026. So this over-rate sheet is not on-field drama; it is an administrative note filed before the format switches. And I learned to read administrative notes from empty grounds—the empty stadium still had a rhythm; we just had to learn its silence.

The old history of the India-West Indies rivalry hangs over this too. West Indies were the superpower of the 1970s and 80s; India own the modern era. But a visiting side chasing 352 on a flat deck means this ODI leg was not one-sided. It is equally true that both bowling attacks were almost unarmed in this match.

The Names Missing Inside the Arithmetic

The architecture of Article 2.22 worked flawlessly here, which makes it the most reliable information available. On-field umpires Jayaraman Madanagopal and Sam Nogajski raised the charges; third umpire Sharfuddoula and fourth umpire Virender Sharma were part of the process; match referee Prakash Bhatt levied the sanction. Both captains—Shubman Gill of India and Shai Hope of West Indies—accepted the sanction without a hearing. That acceptance is itself information: both sides knew the delay was self-inflicted.

The thing that matters most to me here is not the number but the ratio. Hosts India bowled four overs short, while visitors West Indies were two short. The side playing at home, in familiar conditions, within familiar tolerance, was punished more—that cuts against our default assumption about elite-side discipline. Top teams usually finish within zero to one over. One match cannot define a culture, but it can send a signal.

West Indies are a different picture. This was their second sanction in three months—five percent against New Zealand in July, now ten percent against India. That is no longer a one-off lapse; it is a pattern. My reading is that West Indies have a systemic problem in ODI bowling management—either inexperienced bowling leadership, or a pace attack thin enough that bowlers must be changed constantly, and every change burns time.

India's own record sits in my notebook: ten percent in the Raipur ODI against South Africa in December 2026. So this twenty percent did not fall from the sky; it is a new line in a running ledger.

Captaincy accountability here measures responsibility, not skill. Gill's full-time ODI captaincy is still young, and this first documented blemish at home adds a line to his learning file. For Hope the question is heavier—he is already an old name on this list.

There is a layer everyone skips—the human cost. An over finishing late does not just mean a fine; it means ball-boys eat late, the scoreboard operator gets home late, groundstaff switch on the night lights to clear the field, local organisers sit over their bonus sheets. The midfield does not ask for the spotlight; it asks for the next pass—I learned that from football, but it holds inside cricket's slow overs too: someone holds the tempo, someone else merely picks up the result. I learned to keep the beat by listening to the players nobody watches.

And there is one invisible ledger called the broadcast schedule. If a match does not finish in its fixed slot, advertising windows are lost and the next programme slides. Broadcasters have a direct commercial interest in strict over-rate enforcement—nobody says this into a microphone, but it sits inside the arithmetic.

The Misreading

The easy media read will be: India sloppy, embarrassed at home. That outside reading buries the real thing. First, the fine is so small that it is a signal, not a punishment—20 percent of a match fee is no real blow, but a pointer toward protecting the schedule.

Second, West Indies' chase of 352 will be dressed as the small side beating the giant. That story is comfortable, but the truth is drier: on a flat deck both bowling attacks were weak, and a seven-hundred-run match means there was almost nothing in the pitch for bowlers. The romantic narrative skips past financial inequality and sustainability questions; here it shows plainly in the ratio—the winning side was fined too, because management gaps do not disappear with a win.

Third, one trap must be avoided: a single match's over-rate cannot be used to write India's discipline culture. The sample is one, and it came at home. And while DRS reviews and repeated bowling changes do inflate over-rates, that is inference, not evidence—the specific causes of the delay are nowhere in the match report. Writing down what is not written is a crime in my trade.

Watching Lucknow

The eyes now turn to Lucknow. Tuesday, 6 October 2026, the first of five T20Is. Over-rate risk is far lower in T20 cricket—fewer overs, quicker rhythm—so whether over-rate becomes a headline again in this series will tell us how deep the Mullanpur episode really ran. Two lines are already in my notebook: does West Indies pick up a third sanction inside six months, and does this stain fade from Gill's captaincy page. A third line is waiting—will the 50-over format think about its own clock again? Because in the end what is true is not the result: a game that cannot keep its own time will one day be remembered for nothing else.

The first byline was not mine; it belonged to the crowd in Rangpur. But this arithmetic, these four overs and two overs, this small gap—the duty to log it for that crowd is mine.