Delhi 299/6: Doseja's 78, Mathur's 80* and the Twenty Runs the Scorecard Won't Name
**मुख्य उत्तर (≤60 शब्द)**: दिल्ली ने रणजी ट्रॉफी मुक़ाबले के दिन 2 के स्टंप्स पर सर्विसेज़ के 266 के जवाब में 299/6 बना लिया, यानी 33 रन की बढ़त और पहली पारी के तीन अंक सुरक्षित। आयुष डोसेजा ने 78 और मयंक मथुर ने 80* रन बनाए; छठे विकेट के लिए 144 रन की साझेदारी हुई। **मुख्य तथ्य**: - दिल्ली 299/6, सर्विसेज़ 266 — 33 रन की बढ़त, दिन 2 स्टंप्स पर तीन अंक पक्के। - आयुष डोसेजा 78 रन, आयु 26 वर्ष; पिछले सीज़न 949 रन — रिपोर्ट में एक जगह 950 भी। - मयंक मथुर 80* नाबाद, पर सातवें विकेट के साथी का नाम रिपोर्ट में नहीं है। - सर्विसेज़: अर्जुन शर्मा 2/48, जयंत गोयत 2/51; पुलकित नारंग ने 42 पर डोसेजा का कैच छोड़ा। - 135 जोड़ 144 बराबर 279, जबकि स्टंप्स 299/6 — बीस रन का हिसाब अधूरा रह गया। **स्रोत**: मूल मैच रिपोर्ट, दिल्ली बनाम सर्विसेज़, रणजी ट्रॉफी, दिन 2 स्टंप्स; मूल रिपोर्ट में तारीख़, स्थल या राउंड दर्ज नहीं है | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर**: प्रश्न: दिल्ली को तीन अंक कैसे मिल गए? उत्तर: रणजी ट्रॉफी नियम के अनुसार पहली पारी की बढ़त पर तीन अंक मिलते हैं, और दिल्ली ने सर्विसेज़ के 266 को पार कर लिया। प्रश्न: आयुष डोसेजा की 78 रन की पारी को "लय वापसी" क्यों नहीं कहा जा सकता? उत्तर: क्योंकि रिपोर्ट स्वयं कहती है कि वे अच्छी बल्लेबाज़ी कर रहे थे और अनलकी आउट हो रहे थे, यानी मुद्दा शुरुआत को बड़े स्कोर में बदलने का था, न कि फ़ॉर्म का। प्रश्न: दिन 3 का सबसे बड़ा सवाल क्या है? उत्तर: दिल्ली किस समय घोषणा करती है और क्या सर्विसेज़ को दूसरी पारी में समेटकर छह अंक वाली जीत निकलती है, यही तय करेगा कि यह रिपोर्ट किस श्रेणी में रखी जाएगी।
Delhi's scorecard at stumps on day two carries three numbers: 135/5, a sixth-wicket stand of 144, and 299/6. Add them up. 135 plus 144 makes 279, not 299. So twenty runs arrived through a partnership nobody in the report names — the seventh-wicket pair that was still there at the close. Mayank Mathur is unbeaten on 80, which means the man at the other end was physically present all evening. He simply was not present in the story.
I do not trust a single over until the columns reconcile. Here they reconcile; the third name does not. Six wickets fell, close to three hundred runs were scored, two bowlers took two apiece, one catch went down — and the reader never learns who added the last twenty with Mathur. The reconciliation should have been finished before the form narrative was written.
This Ranji Trophy fixture is being hosted by Delhi, and by stumps on day two the home side had banked the first-innings lead. Services were bowled out for 266; Delhi are 33 ahead at 299/6. One line of housekeeping the original copy skips entirely: a first-innings lead is worth three points in the Ranji Trophy, and those three points were secured the moment Delhi passed 266. Everything left is a scheduling decision — when to declare, and whether six points for an outright win are actually reachable.

Delhi's top order wobbled first. Captain Ayush Badoni went for 7, Anuj Rawat for a first-ball nought. Jayant Goyat, with the new ball, produced the early breakthrough and finished with 2/51. Left-arm spinner Arjun Sharma held the middle overs and returned 2/48. Two wickets each to a seamer and two spinners says this was not a one-way day — Delhi needed a 144-run stand to get anywhere near 300.
That stand belongs to Ayush Doseja. His 78 has become the spine of the entire report, even though Mathur's 80 not out is the larger number and the innings that carried the close. Day two produced four hard facts — the score, the partnership, the state of the sixth wicket and the bowlers' figures. The other two-thirds of the copy belongs to one batsman. Nothing on where the match is going, when Delhi might declare, or how long Services can hold a second innings.
Doseja is 26. He made 949 runs last season — the most useful line in the piece, because that is the sample you can actually trust — the highest for his team and second in the tournament. This season he had gone four innings without a fifty, but the manner of the dismissals did not match the numbers: he was getting starts. He spent three months at the BCCI's Bengaluru academy on a red-ball camp with Wasim Jaffer and Hrishikesh Kanitkar, and made 45 in the first innings against Bengal facing Mohammed Shami, Mukesh Kumar and Akash Deep. Against Services, the first substantial deposit from that camp arrived as 78.
Two small leaks blur the ledger. First, the same article gives you 949 in one place and 950 in another — one season, one batsman, two figures. A player rounding up and a reporter being exact can coexist, but not inside one file without a note. Every column carries a discrepancy, and the job is to name it, not to file it away. Second, the same Bengaluru institution appears under two names in a single paragraph — academy and Centre of Excellence — although it is one address that was renamed in 2026. A reader would reasonably assume two different facilities.
And Mathur? Eighty not out, the team's top scorer, holding the crease through the closing overs — and one line in the whole report. That is not a rhythm problem, it is a selection problem. If the largest entry on the sheet gets the smallest note, the whole story is hung on the wrong side of the scale.
The headline insists Doseja 'regained his touch'. The copy dismantles its own premise. Doseja says he felt he was batting well and was getting unlucky, and the narrative itself records that he went four innings without a fifty 'despite getting starts and looking in touch'. The problem was conversion, not form — turning starts into scores. The headline bought a more dramatic frame at the cost of an accurate one. And the deeper point: four innings of drought against a 949-run season is noise, not signal. Seventy-eight is not proof of anything either; it is one innings.
The dropped catch deserves the same audit. Pulkit Narang put Doseja down on 42, and Doseja went on to 78. The phrasing 'went on to' converts a counterfactual into a settled cost of 36 runs. What would have happened had the catch been held is not a measured quantity anywhere, and unmeasured quantities do not go into the ledger.
Day three offers two paths, and either one decides the fate of this entire narrative. If Delhi declare early and Services bat out the second innings, the touch-regained story becomes a footnote nobody rereads. If Delhi bowl Services out and take six points, this same report gets cited as the turning point — and even then it will not tell you when or where the match was played. Rebuilds are not stories; they are sequences with dates attached. Any use of this text after day three needs a fresh scorecard, because a report that cannot state its own date cannot state its own conclusion.
