Timed Out: The Two Minutes Nobody on the Field Could See

Hook: A piece of plastic strap

On 6 November 2026, at the Arun Jaitley Stadium in Delhi, Sri Lanka's innings was in its middle passage when Angelo Mathews walked out after Sadeera Samarawickrama's dismissal. As he lifted the helmet to his head, the strap snapped — a small plastic tab whose price appears on no scoreboard. He signalled for a replacement, a new helmet arrived from the dressing room, and the swap was made. In that window, Bangladesh captain Shakib Al Hasan appealed to the umpire: timed out. After a consultation with the third umpire, the verdict came — Mathews out, off zero balls. In 146 years of Test cricket, 52 years of one-day internationals and 18 years of T20 internationals, nothing like it had happened before.

The crowd booed. Online, the world split in two — one half saying the law is the law, the other asking where the spirit of cricket had gone. I was watching from a flat in London, and what kept striking me was simpler than either camp: nowhere in the entire episode was there a clock. We are shown ball-tracking accurate to the millimetre, yet the two minutes that ended an international batter's innings have no visible ledger at all.

Context: Three minutes became two, and the arithmetic behind it

MCC Law 40.1.1 is unambiguous — after a wicket falls or a batter retires, the incoming batter must be ready to face within two minutes, the clock running from the fall of the wicket or the incoming batter's arrival at the crease, whichever is later. For decades that window was three minutes; in 2026 MCC cut it to two, on the stated logic of speeding the game up. But pace is one thing and broadcast inventory is another. The advertising gap a broadcaster sells between overs is priced in seconds, and in the language of the law those seconds enter under the heading of "the pace of the game".

The 2026 World Cup playing conditions carried the law unchanged. They carried no visible clock and no independent timekeeper. In football, what is now routine — a named video assistant in the VAR room, a defined review protocol, defined timestamps — has no cricket equivalent for timed out. The umpire counts inside his own head while also managing fielding positions, checking the ball, and sending a fielder to square leg. In that reality, one man's memory becomes the final exhibit.

The ICC code of conduct writes slow over-rate fines as a percentage of the match fee, and every over in that calculation is on paper, in a report, with a right of appeal attached. Where the money is, the ledger exists; where the justice is, only memory. That is the referee's paper trail — and on this night it stopped somewhere short of the field.

Core: What the replay does not show

When I covered VAR's first World Cup in Russia in 2026, I watched France against Australia in Kazan, where Josh Risdon's handball produced the tournament's first VAR penalty. At least one thing was clear there: behind the decision sat a chain of frame-by-frame evidence. In 2026, during Project Restart, Hawk-Eye missed a goal in front of my eyes at Aston Villa versus Sheffield United, and I read the 92-page protocol to see how small the technology's margin of error actually was. The lesson from both was the same: I trust the replay, but I audit the frame rate. In Delhi, there was no frame to audit.

Read the law closely and three gaps open up.

First, when does the clock start? The wording is "the fall of a wicket or the arrival of the incoming batter at the wicket, whichever is later". But on a caught dismissal the outgoing batter takes time to leave the field — is that time charged to the incoming batter? No broadcast graphic showed how many seconds Mathews actually had after Samarawickrama's dismissal. In other words, there is no way for a viewer to check the time the umpire counted.

Second, who owns the duty? In football the VAR operator has a name, a title, and an audio transcript. Cricket has no designated timekeeper for timed out; the third umpire may assist but is not obliged to. So a decision that can turn a match rests on the memory of one or two people who are simultaneously juggling ten other tasks.

Third, there is no relief for equipment failure. The laws allow a new ball when the old one is damaged, but a snapped helmet strap — a failure of protective equipment — is recognised nowhere. Football provides defined stoppages for blood injuries or a broken boot. Here the batter stopped for his own safety, and in that same window he was given out. That is not deliberate delay; that is a machine failing.

The largest inconsistency, though, is the standard of proof. In the same match, DRS shows us a 3.5-centimetre margin, measures ball-tracking to the millimetre, and in tight cases protects the on-field umpire's call precisely because the evidence is not conclusive enough. Yet the two-minute count carries no margin, no umpire's call, no review. Umpire's call is not a margin; it is a confession — the system admitting the limits of its own evidence. On timed out, the system will not even make that confession.

Keep one comparison in mind. The 2026 World Cup final's boundary countback, or slow over-rate sanctions — in those cases the ICC has already written down the method of calculation: when an over starts, what allowances apply, who measures. For timed out, that document does not exist. Where a law has no paper trail, the decision becomes a person's memory — and memory is never appealable.

Contrarian: The spirit defence versus the letter of the law

I understand the outrage completely, and in its strongest form it runs like this: for the first time in 146 years, because of a torn strap, a batter who had not faced a single ball had his innings ended. A piece of plastic decided the fate of a match. For people who love the game, that is not a technicality; it leaves a bad taste.

My objection, though, is to the spirit-of-cricket argument itself. That clause was built to catch what the laws do not cover — pitch invasions, ball tampering, showing dissent. Where the law is clear, invoking the spirit makes the law optional, and then anyone can say, "this is just technical, ignore it". Shakib Al Hasan did not break the law; he used it, which is exactly what players are on the field to do. The fault lies with the administrator who turned three minutes into two in 2026 and never put a clock on the ground.

Notice one more thing. One piece of footage, three different verdicts. In Dhaka the framing was "the law is the law"; in Colombo it was the spirit losing; in the London commentary box the lean was toward the spirit. When the question is whose two minutes these are, the verdict comes from geography, not from the law book. Born in Bangladesh and writing on cricket from London, I see that gap daily — one incident, two languages, two different crimes.

Takeaway

The fix for next time is not complicated, but it is uncomfortable, because it means giving up discretion. Timed out needs a visible clock on the big screen, the way football now shows the VAR process. It needs an independent timekeeper doing only that job. And it needs a defined allowance for equipment failure — as a damaged ball brings a new ball, so a broken piece of protective gear should bring time. These are not rule changes; they are the law's arithmetic made public.

One question still hangs over all of it, larger than the incident. Cricket's calendar is now full of franchise leagues — NOCs, release clauses, central contracts, all written down to the minute — yet the minutes inside the ground still appear on nobody's sheet. A sport that can measure millimetres should be able to measure two minutes. If those two minutes matter that much, why keep the clock hidden from the ground?