The Ranji Scorebook and the Tape: 1,412 Overs Counted in 2026-94 and Nothing in the Record

Nine home matches were played at the Sardar Patel Stadium, Motera, Ahmedabad, during the 2026-94 Ranji Trophy season. Every innings, every over, every leg-before appeal across those nine matches was recorded by a scorer in a copy he kept. He charted 1,412 overs, drew a wagon wheel for each innings, and logged every leg-before appeal with the bowler's release point, the batter's stride length and the umpire's initials. After the season ended, no one asked to read that file. He kept it anyway, and kept adding to it for eleven more seasons.

Thirty-two years later, sitting in this same city and comparing today's data desks with that old copy, the question is the same as it was then: what does the record hold, and what does the tape show? The scorebook says one thing; the tape says another. My entire working method is built on logging that gap — not on resolving it.

Context: The Scorer's Chair Where No Camera Reached

The 2026-94 Indian domestic season was played in a peculiar kind of darkness. Not every over of Ranji cricket was on television, there was no such thing as Hawk-Eye in Indian domestic cricket, and ball-tracking was a privilege of a few international series in that decade. The scorebook was the only primary source.

Whatever happened at Motera that season partially reached the scorebook, partially the umpire's report, and partially someone's memory. I was thirty-three then, having abandoned a half-written Master's dissertation to take a Rs 1,200-a-month ball-by-ball scoring post at Motera. I thought it was a temporary job that would end in a few months. Eleven seasons later I was still there, and that copy is still with me.

Today's coverage waves this sort of thing away as "the machinery" — match referee reports, code-of-conduct hearings, pitch inspections, NRR arithmetic, review protocols. This is the layer that decides outcomes while coverage stays on the boundary. The 2026-94 Ranji matches had no match referee, no DRS, no third umpire — and precisely for that reason that season becomes a clean benchmark against today's data age: when there are no protocols, what does the record leave out?

Core Analysis: That Table of 1,412 Overs That Never Made the Newspaper

Looking at my copy of that season, it is startling that the gap between record and tape was not hidden at all. It was right there as a table. Every match in my papers had four columns: mandated over count, overs recorded, no-ball count, and number of leg-before appeals.

The third column showed the biggest discrepancy. In several matches, the no-ball count shrank in the summary line at the end of the scorebook. The scorer's habit was to count no-balls during the over and total them at the end of the innings. But when the summary was made, some deliveries went into the "extras" account and never returned to the no-ball account. No one did this deliberately. This was a procedural failure, not anyone's intent. And my anomaly log began right here — with this one column, with this one discrepancy.

The second column slipped even more quietly: the mandated over count. How many overs should be bowled in a day in a domestic match was decided by the board. But when weather was bad, a bowler injured, or an umpire cutting overs to save time, the scorebook jumped straight to the next over. The overs skipped in between left no documentary trace — only the memory that something was skipped. I came to understand years later that the arithmetic of over rates is always scrambled for this reason: the record does not count the overs that never entered the record at all.

The third anomaly point was leg-before appeals. With every appeal I wrote three things: the bowler's release point, the batter's stride, and the umpire's initials. Across the nine matches of that season I had data on eighteen different umpires, and each had their own zone — some raised the finger early on pad, some did not. This information goes nowhere in the scorebook. You cannot even find an umpire's name from the scorecard, because domestic scorecards do not carry umpire names.

This is where my method breaks first, because the question is asked in reverse. The journalist asks: why did this batter err by getting out? I ask: beyond which threshold did this umpire's decision change? For me the question is not who thought what; the question is which protocol applied at which moment, and at which moment it stopped applying. When that same logic is applied to international cricket, the pattern is clear: the system looks quicker where there is a camera, and stalls where there is only paper.

The Same Event, Two Different Systems: The 2026 Domestic Table and the 2026 Bengaluru Protocol

I have that season's copy, but 2026's protocol is also logged in my anomaly file — when Steve Smith glanced toward the Australian dressing room over a DRS call at M. Chinnaswamy Stadium, umpire Nigel Llong sent him back, and India won by seventy-five runs. Newspapers debated morality for two weeks over that incident — who was the cheat, who was the gentleman.

But watch the tape closely. There is a fifteen-year gap in protocol, yet the core problem of the decision process is the same as at Motera: when a voice comes from outside the system, the protocol has no proper way to hear it. In that video I broke down the fifteen-second clock: the time limit for deciding on DRS, the umpire's-call band, and the moment the batter looked before the strike. Beyond that, everything is conjecture.

This comparison is not merely academic. It does the same comparative work I do in every analysis: after 2026, international cricket added cameras, but did not add protocol. The DRS process still works the way an umpire's eye worked — whatever has no answer, the protocol itself declares clear. This is the machinery that people like me sit and examine through spectacles, and that coverage leaves in the commercial glitter of broadcast.

Cross-Sport Lesson: Hawk-Eye, Football VAR and Cricket — One Decision, Three Failure Modes

When people debate technology delays in cricket, they often bring up tennis's Hawk-Eye or football's VAR as examples. This is a decorative pastime in journalism, but I never use it as evidence. I only keep it when that comparison proves something genuine: the same decision type, three different protocols, three different failure modes.

In tennis, Hawk-Eye's decision arises from the ball's bounce — a static-geometric event, with no human causation. Football's VAR evaluates an event (offside, penalty), so protocol plays the biggest role there. Cricket's DRS is trickiest because ball, batter, umpire and the band of uncertainty all arrive together. This means there is no single thing called "technology" in cricket; there are three different types of failure, and two of them are never fully resolved by any protocol.

When Hansie Cronje's confession broke in April 2026 and Mohammad Azharuddin received a life ban that December, I stopped writing opinion and started watching tape. In sixty hours of 2026-2026 one-day internationals I logged 214 no-balls and 41 abnormally slow scoring overs. This spreadsheet was never published. But it landed me on a broadcaster's third-umpire review desk in February 2026, where at Eden Gardens I watched replays of V.V.S. Laxman's 281 instead of watching cricket. There I learned that a gathered pattern is an argument, a single clip is an anecdote. I began writing decisions as sequences: three frames before, the frame itself, three after. I stopped asking players about intent. Colleagues found I now spoke to sources only to confirm timestamps.

Contrarian: It Is Easy to Blame What You Cannot See, and That Is the Biggest Mistake

Looking at today's data age, one thing is clear: today's data desk gathers more information than 2026-94, but it is repeating a new, narrower version of it. When I open my anomaly log and scroll from the 2026-94 column to today's, I see no difference in structure. Only the filters have changed — now data operators instead of scorers, APIs instead of paper, and tracking bands instead of the umpire's eye. But the silences of the record are still structural, not accidental.

The biggest contrarian point here is that when a procedural glitch surfaces, coverage instantly turns it into a scandal. I have a clear rule for this: a pattern being weighed on the scale of intent must stop being weighed on the scale of fact. If an over is missing, a review unclear — log it, give the source, and state in plain words that the record alone does not prove cause. The principle of intent applies as much to suspicion as to praise — convicting anyone without evidence violates the same method that praises anyone without evidence.

This is my greatest weakness too, and I do not hide it. Fifty years of covering investigations and hearings has trained me to see pattern in discrepancy. When one over goes missing, my first question is who hid it. But now I suppress that question and first write which protocol was in its place at which moment, and which was not. This is the difference between an investigative journalist and a partisan reporter — both watch the same tape, but one builds an argument from it and the other a story.

On the other hand, another journalism gap always rankles me: the silences of the record are often loudest in domestic and women's cricket. In the 1990s not every over of every Ranji match was recorded on some paper, but the women's domestic matches' full scorecard was barely available even until the late 2010s. This is no coincidence. The record leaves empty space where the camera does not reach and leaves no empty space where the broadcaster's money reaches. This asymmetry is not a technical problem, it is a priority problem.

Numbers That Are Not Counted Also Make Patterns

From my experience I can say one thing that not every data analyst will like: the anomaly log ran for eleven years from 2026-94, and still runs. Some things were always the same — no-balls being undercounted, middle overs vanishing, and umpires remaining completely outside the record. All three exist today too, just in modern form. When a ball is entered as a "single" rather than a "dot ball" in a T20 today, or when the first step of a DRS review is silently removed — that is the same structure that was at Motera.

I can explain my approach in as few words as possible, and the fewer the better. I believe the biggest lie in sports journalism is not what is written — but the entire ledger that is never written at all. Why does a CEO's statement get printed and not what the scorer was writing in the same match? Why is NRR arithmetic presented like a new discovery on the last day of the season, when it went unnoticed all year? Finding answers to these questions matters no less to me than understanding the game.

Takeaway: What Is Not Recorded Is Not Forgotten — It Waits in the Log

If the 2026-94 season teaches me anything, it is that what has no newspaper account is also real — it just has fewer witnesses. The biggest question facing cricket today is not technology, not intent. The question is whether our record system is as honest as that scorer's copy was. Will every DRS review be accompanied by the public release of the protocol paper that shows what the umpire saw at which moment, and at which moment he did not get to see it?

This is an old question of my anomaly log, still open. When the next season begins, new scorers will fill new papers and no one will come to read them. But those files will remain. And on any afternoon, someone could open them and ask — where did that over go?