Ranji Trophy: Delhi vs Services — Doseja's 78 Is Not a Story, It's Three Unfinished Questions

The sixth-wicket partnership was 144 runs when the score read 135/5. At stumps, it read 299/6. Do the arithmetic: 279, not 299. Twenty runs have gone missing — scored by a batter whose name appears nowhere in this entire report. That gap is where the real story of this match begins, and it is also where old-school match reporting repeats its oldest habit: treating one good innings as the whole story, and leaving the other end of the partnership nameless.

I was tracking this match on my laptop through scorecards and Ranji feeds — from my room in Ahmedabad, where for years the first hour of every Ranji knockout day has been my hour for hunting the second XI. The first thing a Ranji scorecard shows you is not a total, it's a name. The thing it doesn't show you is the selection system.

First, the facts, without any dressing: Delhi reached 299/6 at Day 2 stumps in reply to Services' 266. First-innings lead is secured — three points banked. A 144-run stand for the sixth wicket. Ayush Doseja 78, Mayank Mathur 80* unbeaten. For Services, left-arm spinner Arjun Sharma took 2/48 and seamer Jayant Goyat 2/51. Those four or five numbers are what actually describe the state of the match. The rest — and this is my first disagreement — is a personal narrative wrapped around those numbers.

The Partnership Math Doesn't Add Up, and Nobody Said So

A 144-run stand from 135/5 means the sixth wicket fell at 279. But stumps were 299/6. So after Doseja's dismissal, the seventh-wicket pair added 20 more. Who was that batter? The report doesn't say. This is no small omission. *Mayank Mathur's 80 is incomplete until we know who he made those 80 runs with, against which bowling, and on what morale.**

When I was writing 'The Second XI Thesis' in my lockdown bedroom, I set one rule: never treat a partnership as complete until both names and both contributions are visible. Because partnership is the part of cricket where personal stories most easily erase the other person. That is exactly what happened here. One batter made 78 and got the whole coverage; the other made 80 and was left as 'the partner.' If that 80 had been made by anyone else, the headline would have carried their name.

'Regains Touch' — When the Headline Fights Its Own Text

Now the part I object to most. The headline says Doseja 'regained touch.' Regaining touch implies something was lost. But the report's own quote says otherwise: in Doseja's words, he 'felt he was batting well and was getting unlucky dismissals.' The text goes on to say he went four innings without a half-century 'despite getting starts and looking in touch.'

So the report itself proves the touch was never lost. The problem was not form, it was conversion — the rate at which starts of 20-30 were being turned into big scores. These are two entirely different diseases with two entirely different cures. 'Losing form' is a matter of the head; 'failing to convert starts' is about technique and patience. When a writer collapses both into one word, he hides the cricketer's actual problem.

And the biggest thing: what is a four-innings drought statistically? 949 runs last season. In a tournament like the Ranji Trophy, four innings is noise, not pattern. In my spreadsheet I have logged every Indian top-order collapse of that era — and I learned one thing clearly: to call an innings a 'comeback,' there must be a career crisis before it; otherwise, it is just a good innings. 78 runs is one day's good work. Calling it a 'regained touch' becomes a claim that could be falsified in any one of the next four innings — and that claim has no timestamp, no grading, no receipt.

Doseja's Age of 26: The Fact Left Useless on the Table

The report says Doseja is 26. It just says it and moves on. This could have been the biggest missed connection. In Indian domestic cricket, 26 sits at a very specific door. By that age, if you haven't built at least one solid IPL season, you move from 'prospect' to 'domestic performer' — and that category gets scouted differently. 949 runs last season — first in the team, second in the tournament — and still no name in a big auction? That could have been the most interesting part of the whole story, and it appears nowhere in this report.

My experience tells me — and I hold to this in every big take I file — that the real news in domestic cricket is not the score, it's the map of 'who gets trusted.' When a 26-year-old batter who was the tournament's second-highest scorer last season is still in a 'maybe next auction' position, that score tells you less about him than about the selection system's faith. The report wrote the age and moved on — that is burying the story rather than opening it.

NCA or CoE: One Institution, Two Names, and a Reader Misled

Doseja has said he did three months of red-ball training in Bengaluru — under the supervision of Wasim Jaffer and Hrishikesh Kanitkar. In one place it is called NCA, in another CoE. Technically it is the same place — the BCCI's Bengaluru centre, renamed the Centre of Excellence in 2026. But the reader doesn't know that. Two names for one institution read like two different places.

This seems small, but it is a symptom of a bigger problem I write about in every numbers column: domestic cricket reporting often writes data without attribution. In this report, scores, ages, last season's runs, bowling figures — none has a source. This is common in PTI-style copy, but that doesn't make it right. When a 949 vs 950 discrepancy appears in two places in the same report, the reader's trust takes a hit not just on the prose but on the numbers.

'Three Points' — The Rule That Was Never Explained

Doseja's quote mentions Delhi 'had taken three points so far.' This is the most important piece of the story — it signals the first-innings lead is secured, and Delhi's real target now is to bowl the opposition out again and cash in. But the Ranji rule that awards points for a first-innings lead is not explained in a single line of the report.

A reader who doesn't follow domestic cricket daily stops at 'three points.' He has no idea what Delhi is playing for. A match report's job is not only to say what happened — it must say what's at stake next. If Delhi has three points, the biggest question is: when will they declare? Will they have enough time to bowl Services out on the final day? Or does this match turn into a draw? None of these questions is answered in the report, and that is why this 'Day 2 stumps' report stops being useful by Day 3.

One Sentence That Tilts the Entire Report to One Side

The only sentence about Services in the whole coverage is the author's own opinion: 'Services will rue the dropped catches.' Arjun Sharma and Jayant Goyat took four of the five wickets that fell, and yet nobody spoke to them. No Services coach, no captain, no spinner who dropped Doseja on 42.

This imbalance is old in the Indian domestic pyramid: dismissing the opposition in one vague sentence. I call it 'single-dependence reporting' — when the whole story is spun around one person, the other team ceases to be an agency. The damage isn't to this one article — it's that we never learn where Services' bowling squeezed Delhi, which ball pressured them, and where they found rhythm. Is that 144-run stand a story of Services' failure or of Delhi's technique winning? Even that question was never asked in this report.

Where I Could Be Wrong

Now the section I include in every big take, because a prediction nobody can check is just a mood, not a report.

My first error could be that I read the 135+144=279 vs 299 gap as '20 runs from the No. 8 batter' — it is possible the actual detail is that the 144-run stand was the total advance from 135/5 to stumps, and Doseja fell not on 78 but on some other score. Both readings are possible, and only the original scorecard — not provided in this report — can settle it. If I am wrong here, I should have written 'the partnership math is incomplete, confirmation from source required' instead of inventing a No. 8's name — and that is my real lesson.

My second error could be my own 'form vs conversion' take. I am applying it to a 78-run innings, but the text that says no half-century came in four innings also admits some of those were starts. If the real problem is technical — say, a specific shot against a specific bowler — then my 'conversion' framework doesn't cover it. And if Doseja scores 60+ in the next three matches consistently, my whole argument that '78 is a good innings, not a comeback' will be proven wrong — and I must write that as loudly as I have written it now.

Where This Match Will Actually Be Decided

So here is the forward-looking bit, and I am putting it as a clean, checkable claim: Delhi will declare on Day 3 within 80-90 overs, and Services will face a 250+ target or a draw-saving examination. If I am right, this report — half of which was about one batter's mindset — will fade before the match's real story the next day. If I am wrong and Delhi bat long, the real question will be: does this team not trust its bowling, or does it fear Services' batting?

I have the receipt — with date and facts. Now the ball is in Services' court, and in the court of that seventh batter whose name nobody wrote.