The Clock That Kept Batting After the Last Ball

The floodlights at Mullanpur had gone dark. The crowd had filed out. The camera tripods were being folded away, one after another. But a clock was still playing—alone, silent, behind the scoreboard. That evening in New Chandigarh, the third and final ODI between India and West Indies had ended in a result; the match had not ended on a piece of paper. On it were written four overs, two overs, twenty percent, ten percent. A short ICC announcement, with no runs, no wickets, no scent of a century. Only time—and the accounting of that time, which keeps running after the last ball. I have watched tape until the crowd disappeared and only rhythm remained. That day I understood that rhythm, too, is a score. Some matches end in a scoreline; others end in a silence that keeps scoring. The New Chandigarh match is the second kind. Where the scoreboard stopped, a clock began to bat. The event looks small, almost administrative. The ICC has stated that in the third and final ODI of the India–West Indies series in New Chandigarh, both teams were found guilty of slow over-rates. India bowled four overs short, West Indies two. As punishment, each India player was fined twenty percent of the match fee, and each West Indies player ten percent. The announcement clearly states that time allowances were taken into consideration. In other words, the penalty calculation is not raw—after subtracting the permitted stoppages from the total delay, the net shortfall that emerged was four and two. Here is the first lesson. When people read over-rate news, they think it is a story of one team's negligence. But if the announcement is read carefully, it shows that both teams were caught for the same offence in the same match. This coexistence is no coincidence. Almost every time two teams have been punished in the same match, the cause has been the nature of the match itself—high scoring innings, frequent reviews, a slow pitch, heat, injury breaks, umpire consultations. The story, then, is not about anyone's character; it is about the architecture of the game. I must be explicit: this announcement is an administrative notice, not a match report. It says nothing about who scored how many, who took how many wickets, what the result was. No player is named. There is no series context. So the honest scope of this piece is limited: I will not step beyond established facts to claim who played well or who was weak. Instead I want to look into a mirror that most people never see—the silence of the scorecard. ODI cricket has an almost invisible rule: fifty overs are expected to take about three and a half hours of playing time, which equals roughly fourteen point two eight overs per hour. This number is not a batsman's average or a strike rate—it is the average of a clock. The most neglected chapter of cricket statistics is probably this: we count runs, we count wickets, but we forget to count minutes. And yet in modern ODIs, minutes are the scarcest resource. I count minutes like a poet counts syllables, because the breath the game runs on is hidden inside time itself. Now let me do the arithmetic. At fourteen point two eight overs per hour, four overs means roughly seventeen minutes, and two overs means roughly eight to nine minutes. But this is the time that remained after time allowances were already deducted. So the actual on-field delay was greater still—add up all the time spent on reviews, injuries, drinks breaks and wicket changes, and part of that raw delay was forgiven by the authorities, leaving the rest punishable. This is not the accounting of a penalty; it is the accounting of a penalty's shadow—where hidden delay is always larger than the published shortfall. The second lesson concerns captaincy. Under the ICC framework, over-rate accountability rests mainly on the captain's shoulders, because on the field the captain is the biggest manager of time. The captain moves fielders, changes bowlers, decides on reviews, sets the rhythm of drinks breaks. But a captain never creates delay alone. If a review passes through five stages of appeal, consultation and decision; if a bowler's run-up is long; if a batsman cramps—all of this lies beyond the captain's control, yet it is cut from the captain's match fee. Here lies the gap between administrative justice and on-field reality. We must also be honest about the financial side. Twenty percent or ten percent of a match fee is almost negligible against an elite cricketer's income. It sends little message, being more a formality. For big stars this fine is like a weekend expense; for a young player it is somewhat felt, but not career-changing. A punishment that does not hurt only creates precedent; it does not change behaviour. The real key to controlling over-rates is therefore not financial—it is organisational and technological. The New Chandigarh or Mullanpur venue context deserves thought at one level. It is a relatively new stadium, not an old tradition-cushioned arena. At new venues, small logistical matters—gallery management, pitch preparation, umpires' familiarity—often remain somewhat unfamiliar. I am not insisting this is the cause; I am saying it is a weak signal that cannot ground any big conclusion, but that should be kept in mind once while viewing the rest of the picture. In cricket's stories the venue is often a silent character—but silent does not mean absent. Now I come to the part where my journalistic habit is most useful. For years I have watched tape with match notes, and every time I noticed the same thing: we count shots, but we do not count gestures. A bowler's pause before release, a fielder's hesitation, a decision not to go for a catch—these micro-moments are the punctuation of the game, its commas and full stops. The over-rate story is exactly this story of punctuation. A match does not slow down in ten big events; it slows down in fifty small pauses—each pause harmless alone, heavy when accumulated together. I see the stadium as a manuscript, and the crowd edits it in real time. But that editing has a cost—the cost of time. Every review, every repeat, every delayed decision cuts a little from the crowd's patience and deposits it in the hands of the clock. The over-rate penalty is really the last page of that deposit ledger. When we see only the result, this ledger becomes invisible. Now I turn to the contrarian side—the place where collective memory and evidence walk different paths. Collective memory will say slow over-rates mean indiscipline, mean a captain's neglect, mean a team's inattention. But the evidence of this match says something else: two rival teams, on the same day, in the same match, caught for the same offence. Rivals do not usually make the same mistake together unless the mistake is made for them. This coexistence suggests the problem lies not within the players, but within the game. This is where an uncomfortable question must be asked. Why do we always see slow over-rates as a punishable individual weakness, and never as a systemic symptom? DRS, review culture, frequent drinks breaks, the modern bowler's long run-up, a batsman's helmet and gear changes—all of these are time-devouring elements arising from the game's own structure. No team breaks these rules; the game itself made them. The delay that is then born is charged to the captain's personal account. This is not fair, because it is a letter sent to the wrong address. The contrarian reading can go one step further. Suppose the real enemy of the over rate is not time, but our interference with time. When every decision is made reviewable, when every moment is given the chance to be examined slowly, the game will slow down—this is the game's inevitable outcome, not negligence. From this viewpoint the over-rate fine is not a solution but a symptom treatment. Just as reducing fever with medicine does not cure an infection, so a fine does not cure delay. A memory surfaces from my own experience. Many years ago, writing a short match diary for a small Czech sports outlet, I noticed that the pace of a game should really be measured not by the number of goals but by the number of interruptions. Since that day I began writing gestures in my notebook, not just shots. Today's over-rate news is another page of that notebook—where I write time as a character, not as a number. How many minutes a match lasted matters less than which moment time stopped, and who wrote that stop. There is also a layer of broadcast economics here, though secondary. Television broadcasters prefer the predictability of time, because a match of fixed length means fixed advertising windows. When a match runs long, advertising calculations become muddled, programming schedules shift, even the next programme suffers. A persistent over-rate problem is therefore not only a question of the game but a commercial nuisance. This is a weak signal, yet not negligible—because administrative strictness often comes from broadcasting interests, not from the game's interests. I say again clearly: this announcement names no player and contains no team performance data. So if anyone concludes from it that India played badly or that West Indies were undisciplined, that would be baseless speculation. What is known is only the size of the shortfall and the rate of the penalty. The rest is my inference, and I want to keep inference as inference. The greatest honesty of journalism is to admit the unknown as unknown. One notable point is that this was the third and final ODI of the series. That is, this is not an event from the middle of a series, but an administrative footnote closing a series. Over-rate announcements often arrive after the heat of the match, in a calm tone, as if they were not the real memory of the game but its administrative shadow. And yet here is a strange truth: some matches live in the memory of runs, while others live on a silent sheet no one reads. The second kind of memory lasts longer, because it repeats—each time anew, in a new match, under a new name. My second personal experience works beneath this piece. For some years I have written about the fine statistics of cricket, and one thought keeps returning: the scorecard never speaks of time. Over rates, the true length of a match, lost minutes, the crowd's waiting—none of this appears in any statistic. And yet these silences are a large part of the experience of the game. The cricket writer who reads only runs and wickets reads half the game; the one who also reads the accounting of time sees the full picture. Here is a place to add one factual note. My long habit of writing about over rates tells me this announcement works like a warning—especially for captains. Because if violations repeat within a specific twelve-month window, the punishment does not stop at a fine; the possibility of suspension arises. Today's twenty percent may be negligible, but the arithmetic of repetition is not negligible. Administration never changes in one blow; it changes step by step, and each step begins with small sheets like today's. Now I come to the concluding question, where one should look only forward, not at the accounting of the past. The over-rate story is really the small shadow of a big question: will cricket think about its clock again, or keep treating the symptom? Today's fines on two teams are a symptom treatment. The real cure may lie in technology—automated time management, shorter reviews, smart scheduling. The day cricket learns to govern the clock, these small sheets will move into the archive of history. A final word. A match ends in a result, but the game never ends. Because the game's most honest record is not on paper—it is on the clock of our memory, where even after the last ball a time keeps batting. Some matches end in a scoreline; others end in a silence that keeps scoring. And the accounting of that silence must be kept by us—because cricket's clock never stops; only the will to keep its account does.