होमAsian CricketRanji Trophy: Doseja's 78 and Mathur's Unbeaten 80 Give Delhi a 33-Run Lead Over Services
Asian Cricket
Ranji Trophy: Doseja's 78 and Mathur's Unbeaten 80 Give Delhi a 33-Run Lead Over Services
रणजी ट्रॉफी में सर्विसेज़ के खिलाफ़ दिल्ली की पहली पारी दूसरे दिन स्टंप्स तक छह विकेट पर 299 रन थी, जो सर्विसेज़ के 266 रन के जवाब में 33 रन की बढ़त है। आयुष दोशेजा ने 78 रन बनाए और मयंक माथुर 80 रन पर नाबाद हैं। छठे विकेट के लिए इन दोनों ने 144 रन की साझेदारी की, जिसके बाद दोशेजा 279/6 के स्कोर पर आउट हुए। सर्विसेज़ के लिए अर्जुन शर्मा ने 48 रन पर दो और जयंत गोयत ने 51 रन पर दो विकेट लिए। पुलकित नरांग ने दोशेजा को 42 के निजी स्कोर पर कैच छोड़ा। दिल्ली ने 267 रन पार करके पहली पारी की बढ़त के तीन अंक हासिल कर लिए हैं। दोशेजा 26 साल के हैं और पिछले सत्र में उन्होंने 949 रन बनाए थे। तीसरे दिन का मुख्य सवाल दिल्ली की घोषणा (डिक्लेरेशन) का समय और सर्विसेज़ पर दबाव बनाकर नतीजा निकालने की क्षमता है।
By the close of play on the second day of the Ranji Trophy match being played at Delhi's home ground, the host team had reached 299 for six in its first innings. Services had been bowled out for 266, which leaves Delhi 33 runs ahead with four wickets in hand. The scorecard highlights two names — Ayush Doseja's 78 and Mayank Mathur's unbeaten 80. But the real story of this innings lies in the partnership between those two figures, the stand that stopped Delhi from collapsing cheaply.
Delhi began the day at 135 for five. The top order had already stumbled. Captain Ayush Badoni had departed for seven and Anuj Rawat was back in the pavilion without scoring, out first ball. In that situation, Doseja and Mathur put on 144 for the sixth wicket. That partnership was the decisive passage of the day. Once the new ball lost its sting, neither batsman allowed the Services bowlers a way through for long stretches, and they kept the scoring rate moving through the middle overs.
Doseja was dismissed for 78. At that point Delhi were 279 for six. After his departure, Mathur added 20 more with the lower order to take the team to 299 at stumps. Mathur returned unbeaten, which is the most valuable contribution of the innings — because when no top-order batsman could hold on, he held one end.
Services' bowling figures were mixed. Left-arm spinner Arjun Sharma took two for 48, while seamer Jayant Goyat took two for 51. Goyat's contribution is not confined to the numbers — he shook Delhi's top order in the early overs, which pushed the hosts onto the back foot inside the first session. But in the second and third sessions, Services could not sustain that pressure and the partnership kept stretching.
Another key moment of the day was the life given to Doseja. Pulkit Narang dropped him on a personal score of 42, and he went on to reach 78. The effect on the scoreboard is obvious, but to claim that Delhi would have collapsed for 36 fewer runs had the catch been taken is speculation rather than analysis. Dropped catches are routine in first-class cricket, and no mathematical basis exists for predicting that one dismissal would have altered the structure of an entire innings. What can be said is that the chance gave Services another route back into the innings, and they could not take it.
Speaking after play, Doseja said he felt he had been batting well and that there was something unwanted in the manner of his dismissals. In his words, he had not been dismissed playing bad shots but rather on certain deliveries where he felt the ball did not go his way. That statement matters for the debate attached to this innings — is this a return to form, or something else?
Before answering that question, one fact needs to be stated plainly. This season, Doseja had gone four innings without a half-century, but in those four innings he had kept getting starts and had kept looking in control against the ball. That is the crux of the whole story. The problem was not that form had disappeared; the problem was converting starts into big scores. Starts kept coming, but they kept ending around 30 or 40. That is not a sign of technical decline; it is usually a sign of a psychological or strategic block.
Looking at the numbers makes this clear. Last season Doseja scored 949 runs, the second-highest in the tournament and the most for Delhi. For a batsman who has accumulated that many runs across a full season, four empty innings is not a statistical crisis. It is noise, not a trend. But there is a habit both inside and outside cricket — turning every early-season fluctuation into a crisis and then calling the recovery a comeback. Seen in the right perspective, what happened in this innings is better described as Doseja finally converting a start into a big score.
There is another important context to this innings, and it concerns his preparation. After last season he did about three months of specialised red-ball work at the National Cricket Academy. The most important part of that stint was not how many balls he faced but who guided the work — figures like Wasim Jaffer and Hrishikesh Kanitkar, men who are symbols of the long-innings culture in domestic cricket.
The direct application of that preparation was visible this season when Delhi played Bengal. That match featured Mohammed Shami, Mukesh Kumar and Akash Deep — the most hostile pace attack in domestic cricket. Doseja scored 45 in the first innings of that game. The runs were not large, but given the quality of the bowling, that innings carries far more weight than any ordinary 45. When a batsman survives three months of red-ball work in Bengaluru and then holds his own against the country's fastest domestic attack, it is not a coincidence.
It is also worth noting that Doseja is 26. In domestic cricket, that is the age at which a batsman has usually built the framework of his technique and now needs to convert it into results. The age matters because the window between domestic performance and national selection opens around this period. But it is equally true that one innings of 78 neither opens nor closes a door. It is evidence that the ability exists, not a conclusion.
Now to Mathur, the least discussed and most essential part of this report. If the batsman who made an unbeaten 80 is the largest single component of the team's total, then knowing little about him is a flaw, not a subtlety. Mathur did the hardest job in a crisis — he watched partners change at the other end, watched wickets fall, and never lost his rhythm. A large share of the credit for Doseja reaching 78 belongs to the fact that he had a settled partner at the other end.
The collapse of Delhi's top order is evidence that this was not an easy pitch. Captain Badoni could make only seven and Rawat's innings ended off the very first ball. Being out first ball is always a statement, however good the delivery. After that, Delhi's middle order rested on two men, and Services had a long time to break it but could not use a single opening.
Services' first innings had folded for 266. That is neither a small score nor a big one. For the home team it was a target that is not difficult to pass, but not so small that the game would win itself. A score of 299 for six in reply to 266 shows that Delhi has taken the advantage but has not been able to deepen it.
And this is where an understanding of the rule that confuses every second Ranji Trophy follower becomes necessary. In first-class cricket, a first-innings lead carries a separate reward. Under the competition's rules, the team that takes the first-innings lead is awarded three points even if the match ends in a draw. In other words, the moment Delhi passed 267, they secured those three points. That is why Doseja said in his post-match remarks that the team had so far taken three points. Without understanding this, none of the arithmetic that follows makes sense, because Delhi's real objective has now changed.
Now the question of strategy arises, and on this the coverage of this match has said nothing at all — even though this is the part that will decide the entire shape of the third day. Delhi must decide when to declare. If it declares early, Services will have a long time in the second innings and will settle in to try to save the match. If it bats on too long, its own chances of winning shrink. The balance is difficult and must be settled by batting arithmetic, not emotion.
Every run past 300 is insurance for Delhi, but reaching 400 is also a delay in its hopes of victory. Mathur is unbeaten at the end — meaning Delhi has a batsman who can both score quickly and hold the other end. Adding 20 with the lower order is no small thing, and it has made the declaration decision somewhat easier.
From Services' point of view, the day was not discouraging, but it was exhausting. After two early wickets they had Delhi at 135 for five and, with economical bowling, a chance to control the match. Arjun Sharma and Jayant Goyat did their jobs, but sustaining the pressure of taking wickets through the middle overs proved difficult. At the end of day two they trail by 33, and their real test now begins — in the second innings they must force Delhi to bat under pressure.
One thing should be made clear here. This report has not been written from inside the Services dressing room, and it contains no statement from their captain or coach. A one-sided story is always incomplete, and what we have in this match is a day seen from Delhi's perspective. For a balanced picture, Services' plans, their bowling changes and their intent for the second innings also need to be heard — this report is without that.
There is another irony to this match: the bulk of the entire day revolved around one batsman, even though the day's biggest partnership belonged to two people, and the second half of it is entirely absent even by name — the batsman involved in the 20 runs added after the sixth wicket is not recorded anywhere. A report that leaves a quarter of a team's total unnamed is incomplete even by the standards of data.
The third day's play will push this whole story in one of two directions. If Delhi declares early and Services dig in during the second innings, then Doseja's 78 will no longer remain the centre of this match — it will become an ordinary, useful innings. If Delhi win the match, that same innings will be called the beginning of the victory. And if Delhi collapse as well and Services save the match, then this report will itself become a lesson — how much information we leave out in our haste to make one innings into something bigger.
Whatever happens, at the end of day two Delhi has the upper hand, and the reason is not just two names. The journey from 135 for five to 299 for six was possible for three reasons — Doseja's patience, Mathur holding one end, and Services' inability to sustain pressure through the middle overs. Without any one of those three, this score does not happen.
And if one thing should come out of this report, it is that 'return to form' is a phrase we use with great generosity. Doseja converted a start into a big score, something that had not happened in his previous four attempts. Not happening in four innings is not a trend. Happening in one innings is not a comeback. What it is, is the meeting of a long season's work and one patient innings — and the real value of that meeting will be decided on the third day, not by statistics but by results.

अनुशंसित
The Lahore Evening Whose Transcript Was Never Released2026-10-26
The Empty Scorecard: Where Cricket Analysis's Chain of Evidence Breaks2026-10-29
Source Information Missing for an Asian Cricket Report2026-11-11
India's Balance Without Hardik Pandya: A Captain's Hope and an All-Rounder's Fragile Tissue2026-11-04
Slot Economics: 'Sacrificing Runs for Kohli' Is a Claim That Can Be Counted — and Nobody Has Counted It2026-11-10
199 Chased in 80 Balls at Wellington: Abhishek Sharma's 35-Ball Century and the Over That Settled It First2026-10-28
Original Report on Asian Cricket Requires Source Material and Verifiable Evidence2026-11-12
अनुशंसित
The Second New Ball in Sylhet: Hasan Mahmud's Five and Bangladesh's Morning Restoration2026-11-06
Anshul Kamboj’s Success in Haryana-Like Conditions: A Useful Signal, Not a Verdict2026-11-11
The New Geography of Asian Cricket: Franchise Dominance, Calendar Pressure and the Shrinking Space for National Teams2026-11-04
214 Deliveries, 54 Balls and an 88-Run Scorecard: Who Opened the Real File on Sri Lanka's Win in Oman?2026-11-06
The New Architecture of Asian Cricket: The Triangular Politics of Format, Franchise and Data2026-11-04
Five Balls, 48 Innings: Labuschagne's Duck and the Ledger of Australia's Top Order2026-10-29
Aaryavir Sehwag's 160 Helps India U19 Beat UAE by 70 Runs, Semi-final Spot Sealed2026-11-11
अनुशंसित
An Empty Analysis, An Unfinished Story: Why Asian Cricket Reporting Needs Its Facts Back2026-11-08
From 19/2 to 328/6: Harmanpreet's Hold and Deepti's Burst in Vadodara, and the Real Story of an Innings2026-10-26
Five Days Between Sylhet and Johannesburg: Bangladesh Face a Triple Challenge of Travel, Conditions and Preparation2026-11-12
The Label Arrived, the Story Didn't: Cricket Coverage's Empty Row and the Urge to Fill It2026-11-02
Empty Payload, Halted Report: What a Null Result Teaches Asian Cricket Analytics2026-10-28
Bangladesh Women's New Challenge Under Nahida Akter: The Sharmin Akter Contradiction and Nigar Sultana's Unresolved Future2026-11-04
Zero Information Points: The Asian Cricket File That Stopped an Eight-Dimension Audit2026-11-11
