Delhi 299/6: Doseja's 78 and the Twenty Runs Missing From the Scorecard

The file landed on the wire at 11:20 pm. Two lines at the top — Delhi 299/6, Services 266. One line in the middle: a 144-run stand for the sixth wicket. Thirteen years of this job have taught me to check the arithmetic before the narrative. Five wickets had fallen at 135; a further 144 runs were added; the stumps score should have read 279. The file says 299.

Did nobody score those twenty runs, or did someone score them and lose his name somewhere in the copy?

The second version is the true one. Ayush Doseja was dismissed for 78 with Delhi on 279/6. After him, Mayank Mathur and a batsman at number seven — a man whose name does not appear even once in the entire report — added twenty more runs before stumps. This is not a team's omission but a scorecard's: the batsman who stood at the seventh wicket that Ranji afternoon could not find a single line in the press file.

The red pen and the wire — that is the desk's daily work: add the score, add the name, and quietly cut whatever will not fit.

These are the stumps numbers from the second day of the Ranji Trophy match being played in Delhi. Services were bowled out for 266 in their first innings; Delhi have reached 299 for six, a lead of 33. The three points for a first-innings lead are already in their pocket, and the contest now runs towards six.

The three-point rule needs one sentence of explanation here, because the original copy never gave it — the phrase simply arrives and the non-specialist reader stalls. In the Ranji Trophy, a first-innings lead earns three points and an outright win earns six. Delhi have banked half their profit by the close of play; the question is how they intend to collect the other half.

The skeleton of Delhi's innings is short. Captain Ayush Badoni departed for 7, Anuj Rawat was out first ball for nought. Out of that wreckage Doseja and Mathur raised 144. Doseja fell for 78; Mathur is unbeaten on 80. For Services, the left-arm spinner Arjun Sharma took two for 48 and the seamer Jayant Goyat, in a burst with the new ball, took two for 51.

Doseja's background matters. He is 26, made 949 runs last season — the most for Delhi and second in the tournament. (The copy says 949 in one place and, quoting the player, 950 in another — a small thing, but when a single file carries two figures for the same fact, trust slips a little from both.) He spent three months at a red-ball camp in Bengaluru last year under Wasim Jaffer and Hrishikesh Kanitkar. Earlier this season, against Bengal, he made 45 in the first innings facing Mohammed Shami, Mukesh Kumar and Akash Deep.

Now the thing that is the real subject of this file, and the thing the file never recognised.

The headline says Doseja has regained his touch. That sentence produces an immediate discomfort, because the evidence against it is packed inside the same report. Doseja himself said he felt he was batting well and was getting unlucky dismissals. The report itself wrote that he had gone four innings without a half-century despite getting starts and looking in touch.

This season's story is not about form; it is about conversion. Doseja is reaching the forties and stopping there — 45 against Bengal, 78 here. These are not the numbers of a batsman playing badly. They are the numbers of what coaches call getting stuck. The ball starts looking good, runs begin to come, and then one shot, one finger, one verdict.

Calling a four-innings dry spell a crisis is, statistically, absurd. A 949-run season is a large sample; the four innings after it are small noise. Every first-class batsman gets such a dry run several times in a career. From the Ranji matches I have watched from the stands over the years and the ones I have watched on a screen at night, one pattern keeps returning: a batsman's form breaks less often than his scoring range does. Doseja's range looks intact here — 78 of that 144-run stand came off his bat, which is 54 per cent of the partnership. A batsman who makes more than half the runs in a stand has not lost his touch; he simply is not reaching a hundred.

That gap shows up in the arithmetic of a season. If half of these forties become 145s and 178s over the next few innings, a man who made 949 goes towards 1200 next season. If they do not, the newspaper has to write a regained-touch headline, because 'conversion' is too technical a word for the desk.

Services' bowling detail points the same way. Goyat found his success in the new-ball burst, Sharma through the middle overs with spin. So Services had two separate splashes, not a wave. Across the middle sixty or seventy overs they found no crack at all, and when the catch went down at 42 that small fissure became the innings. In first-class cricket an innings does not fall; it is made to fall — and here the making never acquired a rhythm.

One more neglected corner: the copy says that after the dropped catch, Doseja went on to make 78, which is to say 36 runs lost. That sentence is attractive and very weak. Nobody knows what a batsman does after a life is offered; he might have been out next ball. Converting a dropped catch directly into runs is not journalism, it is calendar arithmetic. What deserved to be written was simply that Services offered a life and Delhi refused to waste it.

Mayank Mathur is unbeaten on 80 — the highest score of the innings — and the copy gives him one sentence. No background, no previous record, not even which bowling those 80 came against: the new ball, spin, or the tail. Without that, the 80 on the scorecard stays a figure and never becomes a story. The plain fact is that Mathur has scored more runs in this innings than Doseja has.

An institutional detail is buried in the same file. Doseja's three-month red-ball camp took place in Bengaluru — at the same campus we have long called the NCA and which is now the Centre of Excellence. Both names appear within ten paragraphs of one report and the reader is never told they are the same place. That is not a detail error; it is an editing error — the wire arrived and was printed as it arrived. It looks small until you consider that the work of keeping red-ball cricket alive now happens in Bengaluru, work the Ranji Trophy traditionally did, and the journalists who keep that account are printing two names for one institution without joining them.

Here I will say the thing that emerges from inside the report itself.

Every piece of evidence in the file says the touch was never lost; the headline still rests on its recovery. This is journalism's oldest disease: facts travel one way and the headline travels the other. Both are placed in the same file and the reader is left to decide which to believe. On the night desk we rewrote the truth until it fit the deadline — and here the deadline wanted the truth to fit a single shot of 78.

The second thing that makes this file incomplete: Services are entirely silent. Arjun Sharma took two wickets, Jayant Goyat broke the innings with the new ball, Narang dropped the catch — and not one word was taken from any of them. Not from the captain, not from the coach, not from Narang. When the opposition is voiceless, only one team's story survives in the file. The copy's single editorial line — that Services will rue the dropped catches — is aimed precisely at the team with no spokesperson in the file. That is not coincidence. Where nobody is standing to answer, a reporter's pen moves fastest.

The third thing is the most practical: the date of the match, the round, and the name of the ground are all absent from the report. Cut from tomorrow's newspaper and pasted on another portal, this file will not tell a reader when the match was played. In the Ranji Trophy every day's score goes stale by the next; without a date, this score could belong to any year.

Tomorrow will settle what this file is. If Delhi declare early around 400 and bowl Services out to take an outright win, the real story will be the declaration, not Doseja's 78. If Services' second innings holds, the whole regained-touch narrative becomes a file nobody reopens.

The question is whether Delhi have the time and the bowling to dismiss Services twice on this pitch. Mathur is unbeaten on 80, the tail is intact, the lead is 33. The declaration will not be decided tonight in the captain's room but tomorrow morning, after a look at the pitch. The room keeps the score long after the screen goes dark — and at this hour that room still does not have a name for the seventh wicket.