Slow Overs in New Chandigarh: The Clock That Ticks Behind the Fine

It was half past ten at night. Under the floodlights of the Mullanpur stadium in New Chandigarh, dew was settling on the grass, and the crowd was draining out of the stands a little at a time — as if someone were counting water through a pierced pot. Out in the middle, work was still going on. Fielders were shifting positions, a bowler was pacing out his run-up mark with a finger, and there was a two-minute whisper with the keeper. In my notebook I wrote a single word: late.

I had pressed record, and the stands answered me in three languages — Hindi, Punjabi, English. But the real dialogue that night was wordless: the silent forward crawl of a clock's hands. A stadium is a notebook I read with my feet and my ears. Tonight my feet said the grass was wet; my ears said the murmur was thinning.

The news that arrived after the game was not a big scoreline. In the third ODI of the series, India and West Indies — both teams were fined for slow over-rates. India bowled four overs short; West Indies, two. That is the whole record. No result, no scorecard, no individual player named. This is not a match report; it is a receipt.

To understand the matter, you first have to hold the format in mind. An ODI means fifty overs a side, two new balls, two ends, and an innings that drags on for roughly three and a half hours. In a T20, twenty overs are done in an hour and a half; over fifty overs, the arithmetic of time is far more fragile. That is why ODI slow over-rate rules differ too — the tolerance is wider, and therefore the cost of breaching it is higher.

Under the International Cricket Council's minimum over-rate provision, a fielding side is fined for each over it falls short of the required rate. The largest share of the fine falls on the fielding captain; the rest of the players split the remainder. The figure is calculated as a percentage of the match fee. So four overs short produces a bigger number than two overs short — simple multiplication. It also matters who lays the charge and who decides: the match referee is the chief adjudicator of this sanction. This report names no referee and gives no exact percentage; I am deliberately leaving that gap open, because a wrong number corrupts everything built on top of it.

The rule is not new. A few years ago, the ICC opened a path to penalise teams inside the match itself — once the allotted time lapsed, an extra fielder had to be brought inside the circle. The intent was clear: force players to finish overs quickly, so that both the spectator and the broadcaster get a guarantee of time. The fine was the second tier; the in-match penalty was the first. This report mentions only the fine, so whether the in-match penalty was applied is unknown.

Two things here deserve separate attention. First, both teams were fined; the delay was not confined to one innings but ran through the whole match. Second, the host nation's punishment was larger than the visitor's. New Chandigarh is India's home ground, a place of dew and humidity — yet the rules did not spare the home side. West Indies' two-over shortfall looks small but matters: it means their bowling innings lost time too. The match was the third ODI of the series; the length or state of the series is not in the report, so I will not speculate about it.

My writing habit shows itself right here. In 2026, at a spectator-less match at the Bangabandhu National Stadium in Dhaka, I heard the sound of the ball hitting the net and the goalkeeper's shouts echoing off concrete. That evening taught me: the sound of the ground first, the analysis after. A stadium is never truly silent; it is either the murmur of a crowd or the breathing of a clock.

On why over-rates slip, my notebooks hold some old observations. Watching from the ground and the screen over many years, I keep returning to three causes.

The first is the review. A DRS decision takes time — the third umpire studies the ball's path frame by frame, the bounce, the order of bat and pad. One review eats a minute or two. Four or five reviews in an ODI mean eight to ten minutes, which is two or three overs. Nobody on the field counts those minutes, but the clock does.

The second is dew. On Indian night ODIs, the ball gets wet; bowlers want to wipe it again and again, umpires change it, the keeper asks for a towel. These small pauses do not catch the eye individually, but together they build a whole hour.

The third is the shape of the bowling attack. If a side fields a pace-heavy attack, the over-rate slows almost by itself — seamers take long run-ups, switch the strike, take time to set the field; spinners get through their overs far faster. That explanation is my inference, not evidence — the report carries no team sheet, so I will not claim who bowled what.

What this report really speaks to is the rule of time. The ICC's rule here is less about protecting the quality of the game than about protecting the boundary of the product. Broadcasters buy slots by the clock; if an ODI does not finish on time, the next programme slips and the advertising arithmetic wobbles. The over-rate is therefore not only a question of discipline but of business. The market is a weather system; I still pack for rain.

One thing is worth holding on to: the heavier sanction on host India is a small proof that the rule is applied neutrally. Many assume that big teams, or home teams, escape these fine-grained punishments. This episode shows the opposite picture. And yet neutrality in one match is not a trend — it is a data point, not a verdict.

There is another layer beyond the report. Over-rate management is, in truth, a captaincy skill — who bowls when, how quickly the field is set, how much time is spent talking to the umpire. A good captain holds the rhythm of the match; weak management loses to the clock. The side that loses time has really lost its focus.

Now the question nobody asks. Do fines actually work?

My suspicion is that this fine behaves like a tax — small, regular, and unfelt. Against the earnings of international cricketers, a fine set as a percentage of the match fee is effectively dust. A punishment nobody feels is not a punishment; it is a receipt.

The real teeth are not in the fine; they hide in two places. One, the in-match fielding penalty — once the allotted time lapses, a side must keep six fielders inside the circle instead of four, handing the batter an extra run or two. Two, demerit points — repeat the same offence often enough and the points pile up until, one day, the captain faces a suspension. Those two are the genuine fear, because they reach directly into the result. This report does not mention demerit points, so I cannot confirm whether any have accumulated.

Here a blind spot of collective memory is plain. We remember the last-over six, the last-ball thriller, the hero's face. We forget the twenty minutes before it — fielders shifting, the keeper fixing his gloves, the bowler pacing his mark. The result seizes memory; the duration loses it. I count the breath before the ball, not the ball itself — because the real story of a match is written in those seconds.

One more thing goes unsaid: the fault in an over-rate breach is not always the players'. Both teams being punished means the match's administrative management was slow too. When both innings run behind, a question opens — where did the time go in the break, in pitch preparation, even in the rule for changing the ball? That is not an accusation; it is an open question.

Looking forward, one thing is worth watching. If this is an isolated episode, it is a mere administrative note, a three-day story. But if it recurs through the series, the story changes — then questions will rise about over-rate management skill, about players' workloads, even about the time limits written into broadcast contracts.

And one account stays open: across the rest of this series, who is keeping the ledger of the two captains' demerit points? However small the punishment of the clock, the tally keeps accruing — and a tally never forgets.