Can't See the Ball in the Rain: Why the Real Issue in Auckland Was Not DLS But the Umpires' 'Start-There' Mentality
**मुख्य उत्तर:** ऑकलैंड में भारत-न्यूजीलैंड पहली ODI में बारिश के बीच खेल रोके जाने पर विवाद हुआ, जब विराट कोहली और शुभमन गिल ने साइटस्क्रीन पर गेंद न दिखने की शिकायत की, जबकि अंपायरों ने ओवर पूरा करने को प्राथमिकता दी। **मुख्य तथ्य:** - 12 ओवर में भारत का स्कोर 64/1 था; DLS से लक्ष्य 167 रन पर संशोधित हुआ। - 11वें ओवर में पहली बारिश रुकी, तब भारत 29/1 था; कोहली 29 और गिल 17 रन पर थे। - दूसरी बारिश के बाद कोहली का स्कोर 29 पर ही रहा, यानी उन्होंने दोबारा गेंद नहीं खेली। - कोहली ने स्क्वायर-लेग अंपायर पॉल रीफेल से साइटस्क्रीन और विजिबिलिटी पर बात की। - ब्लेयर टिकनर ने शर्ट सिर पर लपेटकर मजाकिया इशारा किया, जिससे बल्लेबाजों की शिकायत पर सवालिया नजरिया झलका। **स्रोत:** मूल रिपोर्ट में कोई नामित स्रोत, लेखक, प्रकाशन या तारीख नहीं दी गई; तथ्य सत्यापन योग्य स्कोरकार्ड और मैच रिपोर्ट से जांच के अधीन हैं | Cross-checked: cricsultan.com **संबंधित प्रश्न:** प्रश्न: DLS ने ऑकलैंड मैच का लक्ष्य कितना बनाया? उत्तर: बारिश के बाद लक्ष्य 167 रन पर संशोधित हुआ, जिससे मुकाबला 12 ओवर का रह गया। प्रश्न: कोहली ने अंपायर से क्या शिकायत की थी? उत्तर: विराट कोहली ने बारिश और फ्लडलाइट में साइटस्क्रीन पर गेंद न दिखने की शिकायत की। प्रश्न: टिकनर का इशारा क्या दर्शाता है? उत्तर: टिकनर का शर्ट-ओवर-हेड इशारा बताता है कि फील्डिंग पक्ष बल्लेबाजों की शिकायत को खेल में देरी का बहाना मान रहा था।
The scene after the 12th over still runs frame by frame in my head. It was raining, the contrast of the white ball had dissolved under the floodlights and dew, and Virat Kohli was standing near square-leg umpire Paul Reiffel — both hands on his hips, the double teapot. With one hand he gestured towards the sightscreen. The scoreboard read 64/1 in 12 overs, the DLS-revised target was 167. I was watching the live data feed that night — India were ahead of the DLS par, meaning there was no immediate fear of defeat, yet the batters had stopped on the field. That was the moment that proved the real controversy of Auckland's first ODI was not 'how we won or lost the match' — it was that the umpires had decided to continue play in the rain before hearing the batters' objection about the sightscreen conditions.
In the seven years I have watched rain and DLS decisions, a pattern has repeated itself — and Auckland is the latest link in that chain. There was a match at Cardiff in 2026 where play continued in rain even though the bowling side had a visibility concern, but the umpires' priority was 'complete the over'. At the 2026 Asia Cup too — the gap between the batter's body language and the umpire's watch was the same. This is not just a cricket problem. The issue VAR faces in football, the limit Hawk-Eye faces in tennis, the delay TMO faces in rugby — they all wrestle with the same question: in what order does the decision-maker look at the evidence of visibility? In Auckland the order was reversed. Umpire Reiffel first chose the process of 'finish the over', and heard the visibility complaint later.

It Was Not the DLS Target — But DLS Was Also Hiding the Dispute
Let me be clear: I am not here to curse DLS. The revised target of 167 was mathematically sound, and I have written several times over the years that DLS has become Indian fan discourse's most convenient scapegoat — while the real problems often lie in rain, light and ground conditions. But something interesting happened in Auckland: DLS reduced the target into a 12-over contest, turning the match into a T20-style shoot-out. Meaning any performance data from this match — Kohli's 29, Gill's 17, the team's 5.3 runs per over — is invalid as a standard ODI sample. I had written in my Receipts sheet, where every prediction is logged: whenever rain reduces a target to fewer than 15 overs, do not treat that match's data as a form indicator. That is the first lesson of that night, and it is the first rule I imposed on myself after the Oval thread of 2026 — but nobody noticed it that night, because Kohli's gesture and the 'can't see the ball' quote in the rain were more fun for everyone.
And here comes a second fact that almost every report buried: Kohli's score was 29 at the first stoppage, and still 29 at the second stoppage. Meaning by the time play stopped the second time, Kohli had not faced an additional ball in the rain. The batter complaining that he couldn't see the ball had not, in fact, thrown himself into that over — captain Gill was on strike at 64/1. This small-looking detail should, in my view, have been the centre of real reporting. On one side Kohli and Gill — both spoke to the umpire — on the other, Blair Tickner wrapped his shirt over his head in a mocking gesture, as if to say, 'this is just the conditions, we can play.' That moment split the reporting into two poles: the batting side's grievance, and the fielding side's incredulous smile. And I have to say, a report without Tickner's gesture does not tell the whole story. It is a one-sided file, recording only the voices of the three batters, not the umpires' 'professional' priority.
When the Camera Becomes the Umpire — And That Night It Didn't
From the 2026 Cardiff host-broadcaster dispute to the 2026 DRS calibration debates, I have consistently written that in cricket the real data on a visibility decision sits with the camera, not the umpire. Auckland was no different. If the stump camera or ball-tracking camera under the floodlights could have clearly shown that tracking the ball was difficult, the decision would at least have been 'data-based' rather than 'subjective'. But that didn't happen. The umpires trusted their experience-based judgement — and across two separate overs at that. The first time rain came in the 11th over and play stopped, India were 29/1. The second time rain returned in the 12th over, the score had reached 64/1 — meaning roughly 35 runs had come in one over. This absolutely does not mean the bowlers were careless; it means the batters tried to keep the scoring rate high even in the rain, yet their trust in the sightscreen contrast was wavering. It is a strange combination — the bat is moving, the eye is not.
Look at the numbers: India were going at 5.3 runs an over while DLS demanded 7.3. That demand itself shows the strategy of chasing in rain was risky — Gill had to rotate strike while also finding boundaries, and in rain the timing and footwork coordination deteriorates. Auckland's pitch had a known swing-seam character; cloudburst only increased the movement for bowlers like Tickner. This gives the batters' complaint a technical basis too: raindrops in the air blur the ball's path, and if the floodlights reflect off the sightscreen, separating a white ball from a white background becomes difficult. Kohli's gesture towards the sightscreen was no drama — it was a technical complaint that TV viewers cannot see, because the camera is in the broadcaster's control, not the umpire's. I once wrote in my newsletter Beyond the Score: 'A replay is just an opinion that has been to lighting school.' In Auckland there was no replay at all to send to lighting school.
Suppose I Am Wrong — Then Does Tickner Turn Out Right?
Now the part every receipts-bound analyst must write, and which I have never skipped since 2026: suppose Kohli and Gill's complaint was not entirely correct. Suppose the rain that night was not that heavy, the sightscreen contrast was not that bad, and the matter was only 'dew and mist' — which every home team has used to its advantage. Tickner's shirt gesture is an expression of exactly that suspicion. And if that suspicion is right, India's complaint can be called a 'strategic break' — aimed at buying a few seconds under the pressure of a fast run rate. But one number gives me some reassurance: India were ahead of the DLS par within 12 overs, meaning there seemed no clear need to break it. If a team is ahead of the DLS par within 12 overs, it neither needs a break nor has much to gain from lying. This is the only weak part of my main thesis: if the batters were right about their visibility complaint, then how did they score runs in the rain? The answer may be simple — runs were coming, but at that moment they felt the risk was too high.
The second possibility is that both umpire Reiffel and the square-leg umpire were right in their places, and the root of the dispute stood in the wrong place. Cricket's laws do not explicitly forbid play in rain; the ICC playing conditions give umpires the authority to stop play on grounds of 'safety and fairness', but do not say that play should stop the moment a batter says so. The gaps in this rule are the real issue, and they are bigger than that night in Auckland. Whether the BCCI or New Zealand Cricket, neither has a public, measurable, shared definition of a 'visibility threshold'. This is the empty space in which both Kohli's anger and Tickner's smile stand. And until that gap is filled, we will remain stuck in this debate every rainy night — someone will say 'they should have played', someone will say 'they should have stopped'.
The Batter Who Stopped at 29 — And Stayed Stopped on the Field
One lesson from my long journalism has not changed since the Oval thread of 2026: 12 overs of a match are not proof of a player's form — especially when those overs were played amid rain, DLS and a fight with the umpires. I decided then that no conclusion should be drawn from Kohli's 29 or Gill's 17. But I do not think the same restraint applies to the umpires. The restraint I kept about players' performance should also apply to the umpires' decisions — but the reverse is also true: when the decision-making process is not transparent, saving it by calling it 'experience' is just as wrong. Not a single official that night explained on what basis play continued, how long the rain was deemed 'stopped', and at what threshold play would be stopped. If the match referee issued a statement later, it did not reach my knowledge — and that omission is the biggest news.
When I scraped data from the IPL's first crowdless season in 2026, one thing became clear: when the evidence of the eye and the ear differ, the truth of a match must be found in the numbers, not in arguments. That night's numbers: rain came twice, both times the umpires tried to complete the over, both times the batters objected, and in the end the score stopped at 64/1. This was not a 12-over match; it was a 12-over argument, in which one side had the microphone and the other had only the rain.

What Next
I have a prediction, and I am logging it in my Receipts sheet: this debate will not end until the ICC's next playing-conditions review brings an explicit provision on a 'visibility threshold'. If such a provision comes — for instance, 'the visibility of the ball under floodlights is measured by camera reference' or 'immediate stop and review upon a batter's objection' — then that night in Auckland will become a precedent. And if it does not come, we will see the same 'can't see the ball' drama on a rain-soaked field next season, someone will fire off a sharp tweet, and everyone will forget again.
The question is not who was right that night — Kohli, Gill, Reiffel or Tickner. The question is: why has cricket so far treated 'visibility' as a feeling when it could be a measurable fact? The sport that adopted Hawk-Eye to the millimetre for DRS could not create a single standard for sightscreen contrast in rain? Until that answer comes, every rainy night will dig the same old trench between umpire and batter — and the cricket world will keep patting it and calling it 'passion'.
