From the Kolkata Press Box: The Story Hidden in Delhi's 299/6 That the Scorecard Won't Tell

Nine in the morning at the stadium. Nobody has claimed a seat yet, the ground staff are stringing rope in one corner, and from another comes the dry tap of a bat — like a door being knocked on that isn't ready to open. That is the truth of Ranji Trophy's second day: the scoreboard says Delhi 299/6, but it never says from what kind of incompleteness those two hundred and ninety-nine runs were built. I have a habit of many years — the first notebook page of a match never fills with the score. First I write the sounds that remain even when the stadium empties. In this Delhi versus Services match, the thing speaking loudest at second-day stumps was the silence of a dropped catch — and then a batsman moving from around forty to eighty. This is not a number, it is a relationship: the moment between fielder and batsman when the ground tilts to one side. Stay with the name Ayush Doseja. Twenty-six, 949 runs last season — most within the team, second in the tournament. He is the batsman Delhi's setup keeps not to play one innings but to carry a season's weight. That 949 was no accident; it was the account of his red-ball work, tied to three months of special preparation at that campus in Bengaluru — once called NCA, now the Centre of Excellence. Those three months in the shadow of names like Wasim Jaffer and Hrishikesh Kanitkar were not a camp but a kind of solitude: learning to leave the ball for long stretches, breaking your own patience ceiling. But here is a trouble that has become a habit of our cricket reporting. We headline every big knock as "form returns." Doseja himself said he felt he was batting well, that his dismissals were unlucky. So the problem was not form but conversion — making starts, failing to turn them into big scores. Four innings without a fifty is not proof a batsman is lost; it is a signal that the step between his start and his big score had cracked. And this eighty is the first strong step on that stair, not a rebirth. Now the part least spoken in this whole match — Services. A team bowled out for 266. Arjun Sharma took 2/48 with left-arm spin, Jayant Goyat 2/51 with an early breakthrough. These figures say Services had not surrendered; they had held Delhi to 135 for five. That was the moment the hosts looked stuck — and from exactly there came a 144-run sixth-wicket stand. That one partnership changed the entire text of the match: Delhi took a first-innings lead and three points with it. This is the rule left unspoken in every Ranji report — a first-innings lead earns points, and the attempt at an outright win is the story after. In that stand is a name that got only one sentence in the whole story — Mayank Mathur, unbeaten on 80. This report has barely more than one sentence about him. Yet at second-day stumps, Delhi's highest score belonged to him. This is our reporting habit: the cricketer without a story gets no space. Doseja's 78 gets a full page; Mathur's 80* gets a half sentence. And the twenty runs added for the seventh wicket — their partner isn't even named in the scorecard report. An unfinished partner. This is no new disease in cricket journalism, but it is a disease. The dropped catch opens that whole moment from another angle. Doseja was reprieved on forty-two and went to seventy-eight. We always write this as "how many runs it cost," but for me the question is bigger. For a team like Services — with no names, only a system — one such reprieve meant playing the whole innings again against Delhi. It was not a catch; it was a decision that changed the match's direction, taken by the field and unrecorded by the board. Let me also be clear that no Services coach or captain quote appears anywhere in this report. How the first day went for the Services side, how they folded for 266 — that story was told from one side only. So writing "Services will rue the dropped catch" is not analysis, it is assumption. And when you are writing a match between two teams, you cannot read one team's silence as its defeat. The question ahead rises at second-day stumps itself. Delhi have three points. Services were 266; Delhi are 299/6. Will captain Ayush Badoni declare early on day three and invite Services to bat again for an outright win? Or let Mathur go from eighty to a hundred, increasing the psychological pressure on Services? This is where Ranji's real strategy hides — and where our reporting ends. Because we describe the match, we don't think its next move. When the first ball lands on the third morning, we will learn whether Doseja's seventy-eight and Mathur's eighty were two chapters of one innings or two different stories. On my second notebook page there is still just one line, and that line is not a score: what is the name of the batsman who walked out for the seventh wicket? Until we write his name, our Ranji reporting will remain not out, like an unfinished innings.