92 Seconds: DRS, Sylhet Rain, and the Rhythm Cricket Never Gets Back

92 Seconds: DRS, Sylhet Rain, and the Rhythm Cricket Never Gets Back

On a recent afternoon I sat in row four of the western gallery at Sylhet International Cricket Stadium and started a stopwatch. On the big screen, ball-tracking was rolling. A man in front of me pulled out his phone and began taking screenshots; a girl beside him shouted that the ball was well inside the line; somewhere behind me people were laughing — not the laughter of a settled decision, but the laughter of waiting. I stopped the clock. Ninety-two seconds. Seventy-thousand people spent exactly those ninety-two seconds chasing one answer, while two umpires in the middle were chasing the last shred of their own credibility.

In Sylhet, the monsoon taught me that a pitch can hold a river. That afternoon it taught me something else: a pitch can hold a wait too. The wait pools like an irrigation channel, and one day it quietly spills over.

Context

From 3 to 6 November 2026, Sylhet International Cricket Stadium hosted its first Test match. Bangladesh against Zimbabwe. In that game Mominul Haque scored centuries in both innings — the first Bangladesh batter ever to do so, a fact the scorecard archive still preserves exactly. And yet, in my memory, that match does not arrive first through Mominul's bat. It arrives through sheets of rain, through water pooling on a dressing-room window, through the announcement: play will resume, please wait.

Based on my years of watching matches, I can say that Bengali-speaking cricket audiences file a game into two drawers: what happened, and what did not. Sylhet's ground got Test status in 2026 — the same year DRS had already become routine furniture in international cricket. What football calls VAR, cricket calls the Decision Review System. According to the International Cricket Council's record, DRS entered international cricket in July 2026 with the Sri Lanka versus India Test. Fifteen years on, the question is no longer about technology. It is about time.

Everyone knows the rules. Two unsuccessful reviews per team per innings in Tests, tighter allocation in white-ball cricket, and once a call reaches the third umpire, a three-way judgment of ball-tracking, ultra-edge and snickometer. On paper the arithmetic is clean. On the ground it is not.

The economics of waiting

Watch the ninety-two seconds from inside. The first ten belong to the crowd, who still believe the decision was right. The next ten belong to television: replay, graphic, a ball walking in slow motion over leg stump. The third ten belong to the umpire — the loneliest man on the field, standing in the shadow of his own cap, knowing his professional soul is on trial inside that black screen.

From the fourth block onward, the real work begins. The captain pleads, the bowler begs, the keeper produces his most persuasive argument. The review nobody took in the seventeenth over is now sitting heavy in someone's chest. Two reviews in a Test innings function like a timesheet: either you hoard both for a top-order batter in the final session, or you spend one with a cold head and then pull your hair out later.

I have long believed that the true tactical battle in Test cricket is now not only conditions and spin. It is a battle of time management. The better you bat, the more your captain wants a review called against you, because you mean danger. Conversely, if a number nine is given out, nobody reaches for a review — there is no 150-run innings on the table. The review system has absorbed a siege economy: teams hoard a limited resource for the point where the expected return is greatest.

The moment the review is announced, a silence falls over the ground — the most modern emotion in cricket. In March 2026 I was live-texting Barcelona's 6-1 win over PSG from a university dorm room, forty-seven frames across ninety-five minutes. I was live-texting from a dorm room when the match was becoming a memory, written in timestamps, ninety-fifth minute and all. Cricket has its own version of that timestamp now, and it arrives as a countdown on a big screen.

But here is my second conclusion after actually timing it: the real delay is not that long. Ball-tracking renders frames in seconds. Of the ninety-two seconds, technology accounts for maybe twelve to fifteen. The remaining seventy-seven are spent on communication, on finding the right channel, on managing the crowd — that is, on broadcast politics.

So the core observation stands: the pause is growing not because of ball-tracking, but because the screen at the ground now speaks for advertising more loudly than for the pitch. In the space of twenty years, cricket's commercial model changed so thoroughly that a snickometer has a sponsor. Every second of that pause is either a sponsor slot or a slow-motion replay. Blaming the review is like blaming the footballer for VAR — it mistakes a system for a person.

I think back to fourteen seconds in Kazan, when Kylian Mbappe ran forty-four metres and I timed the sound of forty-two thousand people inhaling at once. Nobody could stop those seconds, because there was no waiting in them. In cricket we choose to buy the wait. That is the question worth asking.

Rain: the bigger interruption

Here I want to be honest. In my own city, DRS's ninety-two seconds does break rhythm — but Sylhet's rain is far crueller. Technology takes a minute from you. Monsoon takes an entire session, and does not give it back. For years the conversation around Sylhet International Cricket Stadium has not been about beauty but about drainage: how fast the pitch sheds water, how quickly the outfield becomes playable, how well the super-sopper performs. These are the quiet equations of cricket's economy in north-eastern Bengal.

So I admit a hypocrisy. The loudest critics of DRS often fall silent before rain. Both are waiting — but one ends in a result, the other in a promise: play will resume tomorrow at noon. I have spent many Sylhet afternoons where the roar dissolved into conversation, umbrellas opened, and orange light floated in a cup of tea. Nobody reviews that wait. And yet those rain sessions are the deepest scars in cricket memory.

I suspect our anger at DRS is really anger looking for an address — anger about shortened matches, an overflowing calendar, Test cricket squeezed by franchise leagues. The big-screen pause is simply an easy target.

The contrarian angle

Everyone says DRS is killing celebration. My read, over five seasons of close attention, is the opposite: DRS only kills celebration in matches where the player has hidden his real expectation. If you can exhale while watching a black screen, your shot was not unlucky, it was weak. The problem is not the number of suspended seconds. The problem is that our collective memory is arrogant. We all want the review to succeed, even though everyone knows that a large share of reviews land in the grey zone of 'umpire's call' — neither wrong nor right. And that grey zone is the beauty of the game, because cricket was never binary.

In football I saw the same instinct. When a manager hides behind a back three with a sweeper, he is concealing fear, not planning progress. Likewise, a Test captain who deliberately saves both reviews for the final session is avoiding a wrong decision, not seeking a right one. Review allocation has become cautious management rather than an instrument of performance. And a captain afraid of the system slows the system. The technology is not guilty; the frightened mindset is — and that mindset did not arrive with DRS, it arrived with the insecurity of a player economy measured in goals, fifties and innings averages.

Football gives one more lens here, but only a lens. VAR takes one to two minutes, and sound, song and breathing all stop; DRS does the same. The difference is that cricket's pause is countable. Two reviews per innings, four innings per match, eight innings per season. The arithmetic is not frightening — until you do the arithmetic.

Esports showed me that a respawn is just a second chance with better lighting. Cricket's reviews are respawns too, only priced in crowd silence.

Takeaway

After Mbappe's fourteen seconds, I understood that a fragment of time can become a great memory if it is measured. Cricket does the reverse: we measure time and forget what people were doing inside it.

So my proposal is simple. Put a universal clock on the review. A third-umpire decision should be mandatory within seventy seconds — the technology finishes in twelve; the rest is etiquette. And show the replay outcome once, rather than repeating slow-motion quarterly reports. Cricket sells tension, not footage reruns.

Next season, when rain returns to Sylhet and the ground becomes a river again, I will not be counting ninety-two seconds. But the waiting will still be there. The question will remain the same: do we want a decision, or do we want to keep the moment when nothing is settled and an entire ground breathes together? Ten years from now, no one will ask the third umpire whether the batter changed his strike because he wanted to win, or only because he did not want to fail.