Services Tighten Grip on Delhi as Mohit Ahlawat’s 142 and Jayant Goyat’s Five-for Shape Ranji Trophy Contest
Core answer: रणजी ट्रॉफी के तीसरे दिन सेवाओं ने दिल्ली के खिलाफ दूसरी पारी में 280/5 बनाकर 202 रन की बढ़त हासिल की। मोहित अहलावत ने 150 गेंदों पर 142 रन बनाए और जायंत गोयत ने दिल्ली की पहली पारी में अपना पहला पांच विकेट का हॉल लिया। Key facts: - दिल्ली की पहली पारी 344 रन पर समाप्त हुई। - सेवाएं तीसरे दिन 280/5 पर थीं और पांच विकेट शेष थे। - मोहित अहलावत ने 142 रन 150 गेंदों पर बनाए। - मोहित अहलावत ने शतक 117 गेंदों में पूरा किया। - सुमित माथुर 99 रन पर आउट हुए। Source attribution: उपलब्ध Stage-2 मैच विश्लेषण; प्रकाशन तिथि उपलब्ध नहीं। स्वतंत्र आधिकारिक स्कोरकार्ड या CricSultan डेटाबेस से सत्यापन उपलब्ध नहीं है। Related Q&A: Q: मैच में निर्णायक साझेदारी कौन-सी रही? A: मोहित अहलावत और चौहान की लगभग 230 रन की साझेदारी ने सेवाओं को 50/2 से मजबूत स्थिति में पहुंचाया। Q: दिल्ली की मुख्य कमजोरी क्या रही? A: नवदीप सैनी की शुरुआती सफलता के बाद दिल्ली के गेंदबाजी आक्रमण ने मध्य चरण में विकेट नहीं लिए। Q: क्या सेवाओं की जीत निश्चित है? A: नहीं, पिच, मौसम और चौथे दिन उपलब्ध ओवरों की जानकारी के बिना जीत और ड्रॉ दोनों संभावित हैं।
At Palam, the quiet setting of domestic cricket was being contradicted by the scoreboard. Services reached 280/5 in their second innings on Day 3, moving 202 runs ahead of Delhi with five wickets in hand. In a four-day Ranji Trophy match, that number changes the captain’s options, the bowlers’ workload and the psychology of the chasing side.
I have watched enough first-class cricket to know that erasing a first-innings deficit and converting it into pressure are separate tasks. Services have completed both. Mohit Ahlawat’s 142 from 150 balls is the headline performance, but the deeper story is the large partnership that followed an early crisis and turned a vulnerable position into match control.
Delhi made 344 in the first innings, built around Sumit Mathur’s 99 and Doseja’s 78. Those contributions kept Delhi competitive, while the lower order’s failure to extend the total left the innings looking more partnership-dependent than structurally deep. Services began their reply under pressure, reaching 50/2 by lunch. Navdeep Saini supplied Delhi with the new-ball response it needed.

The match then moved through one decisive phase. Ahlawat and Chauhan produced a partnership of roughly 230 runs, with Chauhan adding 56 and Ahlawat controlling the tempo. Services did not seize control through uninterrupted dominance; they seized it by neutralising a genuine early crisis with one substantial stand. That is classic first-class cricket: a difficult hour is absorbed, then reversed through time and partnership.
Ahlawat was promoted to No. 4 because Dhankhar was unavailable through illness. That position carries responsibility in red-ball cricket. It is where a batter is expected to rebuild after an early setback and establish the innings’ tempo. Ahlawat chose an attacking method. His 142 from 150 balls came at a strike rate of approximately 94.7, while his century arrived from 117 balls.
That speed is unusual in first-class cricket, where a batting strike rate in the mid-40s to mid-50s is often entirely functional. The figure should not be transferred mechanically from white-ball cricket. In this setting, it indicates that Ahlawat was able to place pressure back on the bowlers while sustaining a long partnership. His promotion and response make the innings more significant than an ordinary hundred.
Yet one score cannot establish a domestic elite profile. The available information does not include Ahlawat’s season average, home-away split, performance against high-quality seam or consistency against spin. The responsible reading is narrower: he produced a high-value, tempo-conscious innings for Services under changed circumstances. The next series of scorecards will decide whether it was a breakthrough pattern or a remarkable single-match peak.
Ahlawat’s career route adds context. He made his Delhi Ranji debut in 2026, later joined the Navy and then moved into the Services setup. That is a less direct pathway than the conventional state-cricket ladder. It can build resilience and professional discipline, while also limiting visibility among national selectors. The story is compelling, but the ledger still requires more entries.
Jayant Goyat supplied the other important signal. The six-foot-four pacer claimed his maiden first-class five-wicket haul as Delhi were bowled out for 344. His full figures are not available, so economy and control cannot be judged. The milestone remains meaningful: dismissing a side that has batted for a substantial total requires multiple spells and the ability to work with both the new and older ball.

Height alone does not make a fast bowler successful, but it can create a steeper release angle and extra bounce on Indian surfaces. Goyat’s most defensible early profile is that of a hit-the-deck bowler who can disturb batters through bounce. Whether his five-for came through a top-order attack or a late-innings burst will matter, and the sequence of wickets is absent from the available report.
Follow the ledger, not the highlight reel—the ledger remembers every spell. Goyat’s next test will be workload management. Tall quicks who generate bounce can place significant stress on their bodies, and a single five-for should begin monitoring rather than end it. Sustained control across several matches will tell selectors whether he is an impact enforcer or simply the beneficiary of one productive innings.

Delhi’s wider problem appeared after the new ball. Saini created early pressure, but the Ahlawat-Chauhan partnership passed through a long wicketless stretch. That suggests an attack that was front-loaded rather than complete. In first-class cricket, a captain needs a plan for the middle overs: hold the scoring rate, force errors patiently and rotate spells without allowing the batter to settle. Services won that phase.
Delhi’s batting now faces a 202-run deficit. Its immediate requirement is an opening partnership capable of absorbing the scoreboard pressure. If early wickets fall, the first-innings dependence on Mathur and Doseja will look even more important. Delhi’s historic stature matters less than its current ability to survive the second innings.
The contrarian point is that Services’ lead does not guarantee victory. With five wickets remaining, an early declaration would be tactically premature unless the lead becomes substantially larger. Services are more likely to bat Delhi out of the contest than to chase a dramatic declaration. The pitch report, weather and expected overs are unavailable, so the draw remains a live possibility if rain interrupts the final day.
The Ahlawat comeback arc and Goyat’s five-for are attractive scouting stories. They are also single-match signals. Ahlawat needs repeat runs; Goyat needs complete figures and managed spells. This match offers evidence of opportunity, not a finished verdict on either player.
The next decisive number may be the next wicket rather than 280/5. If Services move beyond a 300-run lead and leave Delhi with limited time, the match will become theirs to close. If Ahlawat sustains his tempo and Goyat repeats his bounce across the season, this Palam fixture may become the first entry in a much larger talent story.
