Day Three at Palam: Services Lead by 202 But Their 'Control' Remains Unproven

Standing at Palam after the last ball of Day Three, I kept staring at the scoreboard—280/5, a lead of 202. From inside the ground, this does not feel like the 'command' the headline suggests. It is a strong position, not a settled result. In first-class cricket, a 202-run lead with five wickets standing is a narrow bridge, and Services' lower order has to walk it on the fourth day.

The phrase 'moving day' exists in first-class cricket for a reason—the shape of the result is set on Day Three. In Palam that is even truer, because low, slow northern-India surfaces usually open up for spinners as the match wears on. In my experience on these pitches, the pressure of a fourth-innings chase always sits on the batter, not the bowler. If Services declare in a hurry, Delhi may walk out chasing 250-300 into a surface that is turning and keeping low. But if Services fold within themselves, the arithmetic flips.

Delhi's first innings was a 'nearly' innings. Mathur fell on 99—that one-run miss often leaves the door ajar in a tight first-class game. Doseja's 78 and Lakra's 28 carried Delhi to 344, but no batter went on to a big hundred. And that is exactly where Jayant Goyat's story becomes important. The six-foot-four pacer from Bhiwani took his maiden five-wicket haul in a match where almost nobody was tracking him.

Goyat's maiden five-for is a milestone, but a single first-class five-wicket haul is dangerously high-variance data. I have seen many young seamers take five in one innings and then go six innings without a wicket. His height and the Bhiwani pipeline give him a scout-friendly profile, but one innings is not enough for projection.

On the morning of Day Three, Navdeep Saini removed two to show Delhi's pace still had teeth. Services were 50/2 at lunch, and then Chauhan and Ahlawat pulled the innings up. Chauhan's 56 was the anchor without which Services might have been bowled out below 200.

The most discussed innings of the match is obviously Mohit Ahlawat's 142 off 150 balls. The normal first-class strike rate is 45-60; 94.7 is an unusual pace. The century came off 117 balls—he accelerated after the fifty. The question is whether this is just a good day or the conscious adaptation he described as 'keeping the strike rate in mind'.

For me the second reading matters more. Ahlawat was promoted to No. 4 by accident—Dhankhar was unwell. Scoring at that tempo in an unfamiliar, higher-responsibility slot means a conscious adaptation in how he plays. But caution is needed: this is one innings of data, and Ahlawat debuted for Delhi in 2026 under Gambhir, went to the Navy in 2026, and later joined Services—a career-interrupted, older-path player. This is not a young star's coronation; it is a late-bloomer's story.

I keep saying it—academies hoard talent, but has a system like Delhi's been able to hold onto a player who left for the Navy and came back? If Goyat has crossed the road from Bhiwani to Delhi purely on personal fight, his milestone is not the system's victory, it is the individual's. We should not miss that distinction.

Now the contrarian point. The press report says 'Services in command', but nobody measures the gap between 'command' and 'strong position' when a side leads by 202 with five wickets down. The real control point of this match is how long Services bat—a 320-350 lead pulls the match their way; folding at 280-300 makes Delhi favourites.

The mental pressure is on Services, because Ahlawat is gone and Paliwal is standing at 62 off 96 like a nightwatchman. His lower order must survive the first hour, or the morning session itself can flip the result.

My watch-list for Day Four is simple: which foot Paliwal plants against spin, when Services declare, and how low Delhi set their fields against spin in the fourth innings. From beside the pitch, I want to see who errs first—the captain's declaration or the batter's footwork.