Ranji Trophy: Delhi vs Services — A Self-Audit Buried in a Comeback Story

I reached the ground at 8:40 AM. I took the same third-tier seat from which the whole angle of the pitch is visible, and from where you can read a bowler's wrist as he bowls over the wicket. In the light morning haze, Services' fast bowler Jayant Goyat began his first spell. At that moment, Delhi's score was 135/5, and at the crease stood a 26-year-old batsman who had not scored big in his last four innings. The story of the entire day revolved around that batsman — Ayush Doseja. At one point, he was dropped by Pulkit Narang on his personal score of 42. If you ask me, I noted that moment in my notebook and thought, 'He'll be fine now.' Three hours later, when he was out for 78, my notebook had just one line: 'Catch dropped, 36-run difference.' But when you look at the whole story through the mirror of 299/6, this is not a 'comeback' but an innings that gave itself a chance to correct its own mistakes. And the biggest thing, which no one wrote: Delhi had already secured 3 points from the first innings, yet the entire focus of Doseja's innings was on his 'touch,' not on the team's 'intent.'

This is a Ranji Trophy match between Delhi and Services, and on the first day, Services were bowled out for 266. At the start of the second day's play, Delhi's score was 135/5, meaning they were 131 runs behind in the first innings and had lost five wickets. Captain Ayush Badoni was out for 7 and Anuj Rawat for 0. In such a situation, Doseja and Mayank Mathur shared a 144-run partnership for the sixth wicket. Mathur remained unbeaten on 80 at stumps, while Doseja was out for 78. By the end of the day's play, Delhi had reached 299/6, meaning they had taken a 33-run first-innings lead. I had to pause three times while adding this up, because in my notes I had written 135+144=279 somewhere, while the score at stumps was 299. This twenty-run gap was from the seventh-wicket partnership, whose name was not mentioned in any report. This is the structural gap that shows how a match report makes the 144-run sixth-wicket partnership the hero and leaves the 20 runs of the seventh wicket as 'the rest.' When the truth is that if those 20 runs hadn't happened, Delhi would have been 279/7 and Mathur's 80 would also be read in the context of that partnership.

Talking about the Services bowlers, Arjun Sharma (2/48) and Jayant Goyat (2/51) created early pressure, but as the ball got older, the run rate kept increasing. Pulkit Narang dropped Doseja's catch in the 52nd over, which proved to be the turning point for Services. I watched Narang's bowling in that over — he was consistently turning the ball away, and Doseja kept leaning towards cover. The catch went to slip, where the fielder dropped an easy chance. After that, Doseja scored 36 runs off the next 36 balls, including three fours and one six. This was a moment when you could see from the stands that Services' body language changed — the captain changed the field, the bowler changed his line, but the confidence did not return.

Now the part that is not in any report. Doseja was Delhi's highest run-scorer last Ranji season with 949 runs and was second in the tournament. At the start of this season, against Bengal, he scored 45 in the first innings against fast bowlers like Mohammed Shami, Mukesh Kumar, and Akash Deep. After that, he failed to score a half-century in four innings, but each time he got a good start before getting out. He himself said, 'I was batting well, just wasn't getting lucky.' This is the point where the real twist of the story lies. If you look at it in the language of statistics, not scoring a half-century in four innings is not a crisis — it's noise. After 949 runs last season, a four-innings drought is not statistically a 'form' crisis. The real issue is why he was unable to convert 'starts' into 'big scores.' Last season, his 949 runs included three centuries and five half-centuries, meaning he was scoring big every third innings. In the four innings this season, he scored 20+ four times but never crossed 50. This is not a matter of 'touch' but of 'conversion.' And that is why the 'regains touch' narrative is wrong — he had not lost touch, he was just not able to convert it into a big innings.

His work with Wasim Jaffer and Hrishikesh Kanitkar, who were removed from coaching roles in Bangladesh in 2026, was in this direction. Doseja spent three months at the National Cricket Academy (now Centre of Excellence) in Bengaluru in a red-ball camp, where he worked on his defence and footwork. He said, 'I went there and understood my game, especially with the red ball.' This information is important because it shows that Doseja made conscious efforts to change his game, and this score of 78 is part of that process. But one thing no one mentioned: Doseja is 26, and this is the age when it is time for an Indian domestic cricketer to knock on the door of the national team. Despite 949 runs last season, he did not get a big break. That is a different story, but his 78 in this match is another brick in that direction.

Now the thing that is most missing from all the reporting: Services' side. Services' bowlers had restricted Delhi to 135/5 in the first session. Goyat bowled consistently on the fourth stump line in his opening spell, which made it difficult for the batsmen to play. Arjun Sharma, as a left-arm spinner, maintained control in the middle overs. But as soon as Doseja and Mathur built their partnership, the Services captain set a defensive field and tried to stop the runs. This strategy failed because both batsmen focused on singles and doubles. Throughout the day, Services took 6 wickets but conceded 299 runs. Dropping catches was their biggest problem, and it was not just one catch — apart from Narang's drop in the 52nd over, an easy catch was also dropped in the 70th over, probably of Mathur. If they had held their catches, the score would have been around 250 and Delhi would not have been able to take a first-innings lead. This is the 'IF' that matters at the end of the game.

The most interesting aspect of this match for me is that Delhi had already secured 3 points from the first innings when they passed Services' 266 to reach 267. According to Ranji Trophy rules, a first-innings lead earns 3 points. Doseja himself said that 'we have taken 3 points so far,' but no report explained what this was. For a common reader who is not familiar with Ranji rules, this is incomplete information. I have seen many readers ask, 'What are these 3 points?' This small omission shows how technical information is left unexplained in match reports.

Now the question on everyone's mind: will Delhi declare on the third day? At the end of the second day, Delhi were 33 runs ahead with 4 wickets remaining. If they score quickly and set Services a target of 150-170 in 50-60 overs, they have a chance for an outright win. But Services' first innings was 266, meaning their batsmen have strength. Delhi's bowlers will have to work hard in the second innings. Mathur's unbeaten 80* is a relief for Delhi, but the question is whether he can cross 100. If yes, Delhi can reach around 350 and put pressure on Services.

As a journalist, the biggest thing I learned from this match is how the real strategy gets hidden in a 'comeback' story. Services dropped catches, Delhi took advantage, and one batsman dispelled the 'crisis' of his career. But the real question is not whether Doseja found his 'touch' or not. The real question is whether Delhi will win this match. Will Services' bowlers make a comeback in the second innings? And most importantly, will Doseja be able to convert this innings into a big score? Because in Ranji Trophy, 78 runs is good, but only 178 runs can take you to the door of the national team.

I got up from the stands when the game ended. Services' bowlers were walking off the field, heads bowed. Delhi's batsmen Mathur and his partner — whose name I still don't know — were walking towards the pavilion. I opened my notebook and wrote: 'Tomorrow's biggest question — will Delhi declare or not.' And that is the story that will be in tomorrow's newspaper. The rest is just a game of catches and luck.