Ranji Trophy: Paliwal's 111* and Dubey's 9/53 Spell, Whose Day is it on Palam's Slow Pitch?

On 31 January 2026, inside a 132,000-seat Narendra Modi Stadium holding roughly forty people, I recorded a bowler's breathing through the stump mic. That day I understood that cricket's real story is never on the scoreboard; it lives in the seam of the ball, the dust of the pitch and the breath of a 35-year-old batter. Last week, when I read the report from the slow-turning Air Force ground pitch at Palam in Delhi, that empty-stadium sound returned. Services captain Rajat Paliwal made 111, his team recovered from 158/7, and Delhi's 21-year-old left-arm spinner Aman Chaudhary took four wickets for 79 runs in 31 overs. But there was an odd gap on the scoreboard—Paliwal was unbeaten on 111 while Services were reported bowled out for 266. That arithmetic only works if there was a retired-hurt or absent-hurt event, which was nowhere mentioned. I went back to the ledger, and 248 names were still waiting.

This was an Elite Group C Ranji Trophy match, hosted by Delhi against Services, played on that Palam pitch where the ball takes its time reaching a batter's waist. This is not Test cricket, not T20—this is four-to-five-day red-ball cricket where a Day 1 score is not the final result. On the same day, in Elite Group A, Vidarbha bowled Madhya Pradesh out for 209 in 66.1 overs, Harsh Dubey took nine wickets for 53 runs, and the hosts lost four wickets by stumps at 56/4. Fourteen wickets fell in a single day. That number is a question in itself—were the pitches bowler-friendly, or was the batting foundation simply weak? In fragments of information, separating these two causes is difficult, but one thing is clear: the day belonged to bowlers, except for one veteran batter who saved his team from collapse.

Understanding the texture of the Palam pitch matters. A slow turner does not mean the ball does not turn—it means the turn is slow, and the batter has more reaction time. On such a pitch, a fast bowler's bouncer is ineffective, and a spinner's success depends more on control than on the amount of spin. Aman Chaudhary's 79 runs in 31 overs, an economy of 2.55, is the story of that control. But a strike rate of 46.5 balls per wicket shows he was not a wicket-snatching magician but a bowler building pressure through patience. This distinction matters because calling him a 'trump card' after one spell of 4/79 is premature. This was only Chaudhary's second first-class match. Bowling 31 overs in his second match at 21 tells two things—Delhi trusts him, and that trust also places a workload burden on his shoulders that should not be ignored for any young spinner. Over the past few years I have seen several young spinners bowl 30-35 over spells in domestic cricket and then lose both pace and flight the following season. Not because of injury, but because their bowling muscles were not prepared for that load.

Now the question is how sustainable Delhi's spin-heavy gamble is on this Palam pitch. If the pitch keeps turning until the fourth day, Delhi benefits, but if it breaks up early, run-scoring in the fourth innings becomes difficult. This is the same old debate repeated on domestic pitches every Ranji season—host teams prepare pitches to their advantage, and this is not a violation of BCCI playing conditions unless it breaches standard pitch requirements. No such breach is visible at Palam. But that does not mean this strategy will always work. Services' top order lost seven wickets for 158 runs—this is a question of batting depth, not the pitch. The partnership Paliwal built with the lower order is the biggest test of a captain: when your best batters are themselves struggling, you have to stand up yourself. At 35, with 110 first-class matches of experience, he did what is expected of a senior player. But here another truth hides—Services' batting structure depends on Paliwal to such an extent that without him the team's spine does not survive. This dependence is strength today, risk tomorrow.

Whenever I open Ranji scorecards, I remember the names that never made headlines. Harsh Dubey's 9/53 is the brightest number in this report, but it is not in the headline. That is no coincidence. Delhi-centric media bias is natural—a Delhi match, a Delhi young spinner, and the story of an experienced captain playing against Delhi. But taking nine wickets in an innings is one of the rarest events in first-class cricket. Madhya Pradesh collapsed for 209 in 66.1 overs, and Dubey took nine wickets for 53 runs—an average of 5.89, unprecedented for a single innings. But stop here. Nine wickets in one innings is not the measure of a bowler's season. It is an outlier, and outliers always regress. The question is what Dubey's base wicket-taking rate is. Can he take four-five wickets every match, or was this a one-day wonder? In Ranji history, many bowlers who took nine wickets have struggled in subsequent matches. I am not saying Dubey's performance was a fluke—taking so many wickets requires control, patience and correct reading of the pitch. But I will say that nine wickets in one day does not make anyone a national team contender. That requires a full-season average, performance on different pitches, and above all consistency.

The biggest story of this whole day is perhaps the one not in the headline—the crisis of priority in Ranji cricket. After the match, Rajat Paliwal said players are now prioritising T20 cricket, and he did not call it wrong. This is a statement that should not be read as an accusation against any one player, but as the truth of a structure. The IPL's economic structure is so far ahead of Ranji that for a young player, setting priorities is natural. A good IPL season can give you crores; a good Ranji season can take you to the doors of the Test team but does not guarantee it. This gap is not of one season but of structure, and therefore it will persist. Paliwal's statement matters because it comes from a player who has himself played 110 first-class matches and knows what red-ball cricket demands. His point that players like Ayush Badoni are scoring consecutive double centuries shows that domestic cricket does not lack talent—it lacks priority and incentives.

Now the turn I often return to. We treat one day's performance as the season's result. Chaudhary's 4/79 made him a 'trump card', Dubey's 9/53 brought him overnight headlines, and Paliwal's 111* made him a symbol of sacrifice and dedication. But first-class cricket's arithmetic is different. It is a four-to-five-day game, and one day's performance is not the whole match's, let alone the whole season's. In 2026, during the Ranji final in Indore, I hand-coded 1,842 balls, and that experience taught me that a single innings hundred and a season average are two different worlds. Priyank Panchal scored 1,310 runs that season, but the question was not how many runs he scored—it was how many other batters reached that level alongside him. Ranji's real story is always beyond individual statistics.

So what is the correct assessment of this day? The slow Palam pitch gave an experienced batter a chance to save his team and a young left-arm spinner a chance to show control. In Vidarbha, a bowler took nine wickets to put his team in a strong position, but the same day his team lost four wickets at 56/4—meaning the match is open, not one-sided. That is Ranji's beauty: no team wins in a day, and no player becomes a star in a day. What becomes is proven over the next three-four months.

The biggest lesson for me is that we must learn to read the scorecard in its full complexity. 266 all out and 111* not out—this contradiction is probably a score-extraction error, but it reminds us that until the official scorecard arrives, we should not jump to any conclusion. I always tell my editors that patience is the greatest virtue in Ranji reporting. One day's play is one day's story, and rushing to make it a season's story only causes harm.

Next time a young spinner bowls 30 overs or a bowler takes nine wickets, the question should not be when he becomes the next star. The question should be what his average is over the next five matches, how his line and length change on different pitches, and whether his body can bear the load. Every prospect is an excavation site, and most are still buried. Ranji Trophy's real work is to dig out these buried names—slowly, patiently, and without noise.