Paliwal's Rescue Act and Chaudhary's Control on Slow Palam Pitch: Story of Ranji Trophy Day 1

As I looked at the scorecard after the first day's play at the Air Force Ground, Palam, there was a strange unease. Services' score appeared to be 266 all out, yet Rajat Paliwal was unbeaten on 111. This was a contradiction—unless there was a retired hurt or absent hurt situation, which seemed unlikely, or the scorecard had an error. When I opened my notebook after play stopped on the dusty Palam pitch, that was the first question that came to mind. The first day of this Ranji Trophy match is not the story of one player, but the revelation of an old truth—on slow pitches, the value of experience and control is paramount.

This was an Elite Group C encounter between Delhi and Services, and the Palam pitch traditionally assists spinners. On this slow turning track, fast bowlers get little help, and batsmen must play with patience. Services were reeling at 158/7 when 35-year-old captain Rajat Paliwal took charge. His experience of 110 first-class matches came in handy at a moment when the team needed a pillar to stand amid falling wickets. Paliwal's innings was not just a century, but a statement from a batsman who, in the twilight of his career, took on the responsibility of being a shield for his team. But the bigger story of this innings was that Services' top order was struggling on the slow Palam pitch—highlighting the fragility of the team's batting.

For Delhi, 21-year-old left-arm spinner Aman Chaudhary bowled 31 overs and took 4 wickets for 79 runs. His economy rate of 2.55 is an excellent example of control in first-class cricket. But his strike rate was 46.5 balls per wicket—meaning he was effective at taking wickets but couldn't single-handedly change the course of the match in one spell. This was his second first-class match, and such a long spell on a slow pitch like Palam made it clear that the Delhi team trusts him. For a young spinner, a 31-over spell is neither just a statistic nor just a responsibility—it is also a sign of future burden. Chaudhary's left-arm spin is a rare skill, and if he maintains such control in the next few matches, IPL scouting networks may take notice. But red-ball control and T20 wicket-taking ability are not two sides of the same coin.

On the same day, in an Elite Group A match between Madhya Pradesh and Vidarbha, Harsh Dubey's 9/53 bundled out Madhya Pradesh for 209. This was the most striking performance of the first day—14 wickets fell and the host team was reeling at 56/4. Harsh Dubey's nine-wicket haul was the rarest and least discussed performance of the entire day. While headlines were dominated by Delhi players, this Vidarbha bowler changed the entire complexion of the match. But nine wickets in one innings cannot be the benchmark for a bowler's career—it is an outlier, and it will be interesting to see in the coming matches whether he regresses to his normal bowling average or not.

After the match, Paliwal commented on players prioritising T20 cricket. His stance was not accusatory but understanding—there is money in T20 leagues, and Ranji offers the path to Test cricket. This is a structural reality that cannot be ignored. The real crisis for the Ranji Trophy is not that players are abandoning it, but that its financial value will always remain lower than that of T20 leagues. Paliwal mentioned Ayush Badoni's consecutive double centuries—evidence of the depth of domestic cricket, but it is also a separate debate how much T20 stars can endure in red-ball cricket.

As I walked out of Palam after the day's play, a question hung in the evening air—will Delhi's spin-heavy strategy work on this slow pitch, or does Services have another patient batsman like Paliwal who can hold the fort? The next day's play will answer that. But this entire day made one thing clear—in first-class cricket, statistics are often different from headlines, and the real story belongs to those players who change the course of the match without fanfare.