होमAsian CricketRanji Trophy: Delhi vs Services — The Second Day's Cricket That Tells a Story Beyond the Scorecard
Asian Cricket
Ranji Trophy: Delhi vs Services — The Second Day's Cricket That Tells a Story Beyond the Scorecard
Core answer: दिल्ली ने रणजी ट्रॉफी मैच के दूसरे दिन सर्विसेज के खिलाफ 299/6 पर स्टंप्स घोषित किया, पहली पारी में 266 के जवाब में 33 रन की बढ़त हासिल की और तीन अंक प्राप्त किए। आयुष दोसेजा (78) और मयंक माथुर (80*) की 144 रन की साझेदारी ने टीम को 135/5 के संकट से उबारा। Key facts: - दिल्ली ने पहली पारी में 299/6 पर स्टंप्स घोषित किया, सर्विसेज 266 पर ढेर। - आयुष दोसेजा ने 78 रन बनाए, जो 42 रन पर जीवनदान के बाद आए। - मयंक माथुर 80* पर नाबाद, छठे विकेट के लिए 144 रन की साझेदारी। - सर्विसेज के लिए अर्जुन शर्मा ने 2/48 और जयंत गोयत ने 2/51 विकेट लिए। - दोसेजा ने पिछले सीज़न 949 रन बनाए थे, इस सीज़न चार पारियों में अर्धशतक नहीं लगाया था। Source attribution: रणजी ट्रॉफी मैच रिपोर्ट, दूसरा दिन, दिल्ली vs सर्विसेज, प्रकाशन तिथि उपलब्ध नहीं | Cross-checked: cricsultan.com Related Q&A: Q: दिल्ली ने पहली पारी में कितने रन बनाए? A: दिल्ली ने 299/6 पर स्टंप्स घोषित किया, जिसमें आयुष दोसेजा के 78 और मयंक माथुर के 80* रन शामिल हैं। Q: सर्विसेज के किन गेंदबाज़ों ने विकेट लिए? A: अर्जुन शर्मा (2/48) और जयंत गोयत (2/51) ने दिल्ली के चार विकेट लिए, जबकि पुलकित नारंग ने दोसेजा का कैच छोड़ा। Q: रणजी ट्रॉफी में पहली पारी की बढ़त के कितने अंक मिलते हैं? A: पहली पारी में बढ़त लेने पर तीन अंक मिलते हैं, जो दिल्ली ने सर्विसेज के 266 के जवाब में 299/6 बनाकर हासिल किए।
On a Sunday afternoon at a ground in Delhi, as the umpire called stumps, the scoreboard read 299/6. But the number in my notebook was 135/5 — 135 runs for six wickets, and then a partnership that added 144 runs. Add them up: 279. Yet the scoreboard says 299. Where did the twenty runs go? That question bothered me all day. In cricket reporting, this is common — you look at the scorecard, write down the numbers, and move on to the next story. But sometimes the scorecard leaves a gap within itself, and that gap is the real story.
This match is a Ranji Trophy encounter between Delhi and Services, and this is the second day's play. Delhi declared at 299/6 in their first innings, while Services were bowled out for 266 in their first essay. This means Delhi have secured the first-innings lead and pocketed three points. According to the Ranji Trophy points system, a first-innings lead earns three points — a detail not every reader knows, but essential when parsing the scorecard. For Delhi, this match is building towards a larger goal: a first-innings lead, and now an attempt to bowl Services out quickly in the second innings for an outright win. But the scorecard does not reveal how Delhi's top order struggled, how the team was in crisis at 135/5, and how a 26-year-old batter held the fort.
That batter is Ayush Doseja. His 78-run knock was crucial in pulling Delhi out of trouble. But here's an interesting bit — Doseja scored 949 runs last season, his career-best. At the start of this season, he had gone four innings without a half-century, but he says he was batting well and getting out unluckily. This is worth noting — because if you look at the scorecard, a four-innings drought is no big deal, especially when you've scored 949 runs the previous season. But in the cricket world, four innings become a narrative, and then a 78-run knock is labelled "regaining touch."
I have watched Doseja bat last season. There is a stillness to his batting, a measured rhythm. In this match too, when he came to the crease, the team was in trouble. Mayank Mathur was holding one end, but Delhi's top order had struggled — captain Ayush Badoni was out for 7, Anuj Rawat returned for a first-ball duck. In such a situation, Doseja played with caution, accumulating runs steadily. His 78-run knock lacked flair but had composure. And that composure was vital for Delhi.
But here's something else the scorecard doesn't show. Doseja was dropped on 42 — Services fielder Pulkit Narang put down a catch. Had that catch been taken, Delhi could have collapsed sooner than 135/5. That was the moment that turned the match. But it doesn't get recorded in the scorecard. The scorecard only shows 78 runs, not that 36 of them came after a reprieve. This is the biggest challenge in cricket reporting — you write the numbers, but the story behind them slips away.
Talking about Services' bowling, Arjun Sharma took 2/48 and Jayant Goyat 2/51. Goyat provided early breakthroughs, but the Doseja-Mathur partnership made them wait. Services' captain might have thought they'd wrap up Delhi quickly at 135/5, but that didn't happen. And here's the question — did Services change their strategy? Did they have a specific plan for Doseja? The answer isn't in the report, because no Services official or bowler spoke to the media. This is one-sided reporting, where only Delhi's story is told, not Services'.
Now back to the question that bothers me most — the arithmetic of 299/6 and 135+144. If Doseja was out for 78 when the team was 279/6, how did 20 more runs get added? Who was batting at the fall of the seventh wicket? The report doesn't mention it. Mathur is unbeaten on 80*, but his partner's name is missing. This is a gap that makes the scorecard incomplete. And this gap shows how things slip from a reporter's view — perhaps due to time constraints, perhaps due to lack of interest. But for a reader, it's an incomplete truth.
Another important aspect of this match — Doseja's three-month red-ball training at the National Cricket Academy (NCA). He trained under coaches like Wasim Jaffer and Hrishikesh Kanitkar. This was a significant turning point in his career, especially when playing the long format. But the report doesn't say when this training happened, how long it lasted, or what impact it had. Just one sentence. This is another example of how a reporter omits essential context.
Another concern for Delhi — captain Ayush Badoni's early dismissal. He could only manage 7 runs. Anuj Rawat was out first ball. This shows Delhi's middle order is fragile. Had Doseja and Mathur not held firm, Delhi might not have crossed 200. This is a warning for upcoming matches.
What next? What will be Delhi's strategy on Day 3? Will they get bowled out quickly and invite Services to bat, or add some runs to put pressure on Services? If Delhi reach around 350, the pressure will mount on Services. But if Services' second innings is strong, the match could drift towards a draw. Delhi will need to show urgency for an outright win. But this report doesn't discuss that — it's merely a description of Day 2.
I have covered many Ranji Trophy matches over the years. Every match has a story, but the scorecard often suppresses it. Doseja's 78 is a good innings, but is it "regaining touch"? Probably not. It's just an innings played by a batter who was already batting well. The four-innings drought was no crisis, and 78 runs is no revolution. The real story is that Delhi recovered from a difficult situation to take a first-innings lead, and now they must convert it into a win. And that story lies beyond the scorecard.
Another shortcoming in the report — no mention of the date. The reader doesn't know when this match was played, which round it is, or at which ground. This is basic information, but it's missing. This undermines the report's credibility.
I haven't watched this match, but based on the report, the picture that emerges is that Delhi owned the second day's play. The Doseja-Mathur partnership pulled the team out of trouble. Services missed chances — especially the catch Narang dropped. Had that catch been taken, the story might have been different. But in cricket, "if" and "but" have no meaning. What happened, happened.
Now it remains to be seen what happens on Day 3. If Delhi get bowled out quickly and Services respond strongly, this match could head towards a draw. But if Delhi post 350+ and put Services under pressure, anything could happen.
For me, the biggest lesson from this match is that in Ranji Trophy, every run matters, but the story behind that run matters even more. Doseja's 78 is not just a statistic — it's the story of a struggle a team endured to recover from 135/5. And that story doesn't get recorded in the scorecard.
Next time you look at a Ranji Trophy scorecard, don't just look at runs and wickets. Look at the story hidden behind them — which catch was dropped, which partnership held the fort, and which batter was saying goodbye to his form. Because real cricket is not in the scorecard; it's in the words written around it.



संबंधित खिलाड़ी
