The Mullanpur Fine Ledger: India Four Overs Short, West Indies Two — the Arithmetic Is Clean, the Question Isn't

The match ended in 48.2 overs. Ten balls were still in hand when the 50-over quota went unfulfilled. Yet the number that landed hardest in my notebook from Mullanpur was not 352. It was four. India bowled four overs short. In a match that finished early, the host side walked out with the largest over-rate deficit on the sheet. That is the story.

I have kept notebooks since before I was paid to. In 2026, opening the batting and keeping wicket for Udity Club in the Dhaka league, I learned that an innings never ends on the scoreboard — time, stoppages and field settings all enter the arithmetic. A statistics degree and a junior analyst's desk in Liverpool turned that habit into a profession. On 27 August 2026 I logged Liverpool's 2.6 xG against Arsenal's 0.7 and still could not call the 90 minutes settled. Over-rate in cricket is the same species of thing: a time ledger that lives outside the scoreline.

Before anything else, the format boundary. Every judgement below sits in ODI (50-over) context. No Test or T20 data is mixed in. The incoming T20I series is a separate format context and stays separate.

ODIs carry the highest over-rate risk of the three formats, and the reason is mechanical: two new balls, a mid-innings spin change, repeated DRS reviews, boundary retrievals. A 50-over innings is 50 overs on paper and more than four hours on the clock.

Mullanpur — the Maharaja Yadavindra Singh International Cricket Stadium, New Chandigarh, Punjab. Roughly 700 runs across two innings, which tells you the surface favoured batsmen. More runs means more boundary stops, more bowling changes, more conversations. There is no dew, weather or DLS data in the source, so I stay silent there; absent information cannot carry a conclusion.

In May 2026, when the stadiums were empty, I sat down with the first 40 Bundesliga matches behind closed doors. Home teams were winning 21.7% of matches, down from 43.2%. Empty stadiums were not an anomaly; they were a calibration check on every prior I had. Mullanpur asks for the same discipline: when the environment shifts, the prior shifts. The ODI format is itself an environment in which over-rate loss is built in.

West Indies chased 352 in 48.2 overs. On Indian soil, in Asian conditions, that is a large job for a side in transition. West Indies won. Then both teams' names went into the match referee's book.

The rule first, the arithmetic second. Article 2.22 of the ICC Code of Conduct for Players and Player Support Personnel: 5% of the match fee per over a team fails to bowl within the allotted time, after allowances. It is a multiplication, not a referee's mood. Apply it at Mullanpur and you get: India four overs short, 4 × 5% = 20%; West Indies two overs short, 2 × 5% = 10%. Both figures reconcile, which is why the penalties are rule-derived rather than discretionary.

The officiating chain is fully named: on-field umpires Jayaraman Madanagopal and Sam Nogajski, third umpire Sharfuddoula, fourth umpire Virender Sharma, with match referee Prakash Bhatt levying the sanction. Captains Shubman Gill and Shai Hope both accepted; no hearing was required.

Here is my first reservation. This penalty is a captaincy-accountability metric, not a skill metric. And one ODI's over-rate cannot write a team's discipline culture. I build models the way monks copy manuscripts: slowly, and with the fear of one wrong digit.

What can be written is a pattern. West Indies have now been sanctioned twice in three months — 10% here, 5% against New Zealand in July. Two marks together are no longer a single-match accident; they are the signature of an operational habit. India's earlier mark came in December 2026, 10% in the Raipur ODI against South Africa.

The larger breach by the home side is the uncomfortable part. Elite hosts are normally the most disciplined on over-rate: familiar conditions, familiar umpires, familiar routines. Here the opposite happened. India, at home, bowled twice as many overs short as the visitors. That sits badly with the professional-powerhouse picture.

My baseline says top sides usually finish within zero to one over. India four, West Indies two — both outside it. The match ended in 48.2 overs, so the deficit cannot hide behind a long game. West Indies bowled their full 50, India batted their full quota, the chase closed early. Four overs still missing. This is a genuine time-management failure, not a scheduling artefact.

Why? The source gives no cause, so I keep inference as inference. A 352 chase means bowlers were not finding work, so bowling changes multiply; DRS reviews, injury checks, field resets — small stops accumulate into lost overs. Not one delay but many. Medium confidence, not proof.

The repeatability index can score this mark. Format: maximum over-rate risk. Venue: batting-friendly, high-scoring. Match phase: chase closed early, deficit intact. Add it up and you get a format-driven failure rather than personal negligence. An old transfer-market lesson applies here: data models overrate young talent and underrate dressing-room chemistry. Over-rate is dressing-room material — the captain, the bowling coach, the fielding coach in one room.

The result ran against market priors. A West Indies chase of 352 in India is an upset. But my old line holds: Morocco was not a miracle; it was a repeatability test the market failed. The same question sits on this chase — repeatable process, or one flash?

Now the place where I argue with my own story.

First objection: a fine and discipline are not the same object. Two marks do not make a systemic West Indies problem; two data points are a pointing finger, not a series. I have a rule — no transfer writing under 900 league minutes. Over-rate deserves the same gate: no discipline verdict before five or six matches.

Second objection cuts deeper: over-rate is often not a sign of captaincy laziness but of a bowling attack without control. When bowlers cannot hit plans, the captain changes bowlers, moves fields, resets — and the clock runs. The penalty lands on the captain's record while the cause hides in the bowling unit. An innings that conceded a 352 chase does not weaken that reading.

Third: my home-advantage education is pulling the other way. The baseline at Anfield taught me that home advantage is a ledger, not a feeling — pitch, travel, crowd, umpiring, scheduling, decomposed. The natural prior is that home conditions help the host, over-rate included. Mullanpur did not deliver that.

One more thing nobody is writing: over-rate enforcement is a broadcast-interest instrument. Fixed slots hold, advertising windows do not shift. Five percent of a match fee is small money; it works as a signal more than a punishment. The market does not pay for talent; it pays for repeatable evidence of talent. Governance is no different — a fine means something only when it repeats.

Three entries for the notebook. One: a third West Indies offence inside six months moves the risk beyond money and toward captain-level exposure. Two: India's time discipline in the five-match T20I series starting Tuesday, October 6 in Lucknow will tell us whether Mullanpur's four overs were an accident or page one of a habit. Three: whether ODI's structural over-rate vulnerability — two new balls, spin changes, DRS — pushes rule reform up the agenda.

The ledger is clean today: India 20%, West Indies 10%. But a penalty that adds up is not a penalty understood. Variance is not a villain; it is the reason I keep a notebook.