Sanvir, Arora and Chahal Hundreds Make Day Two of the Ranji Trophy Belong to the Batters

Hook: The scoreboard told only half the story

The biggest score on Day Two of this Ranji Trophy round was 205, but Sanvir Singh’s double century is not the whole story. Punjab declared at 592/9 at home, while at Dharamsala Rajasthan moved to 297/4 one day after 20 wickets had fallen. One round produced two sharply different cricket matches: Punjab’s batting depth and Dharamsala’s dramatic change in conditions.

Sanvir’s 205 is the natural headline. Salil Arora’s 144 and Emanjot Singh Chahal’s 122 turned the Punjab innings into a collective batting statement. Yet this is not the match from which anyone should immediately announce India’s next star. A big score on a friendly surface and a big score under pressure are different currencies in first-class cricket.

I have watched Ranji cricket from press boxes for years. On days like this, the desk wants the centuries; the match’s deeper information is often hidden in timing and pitch behaviour. The scoreboard did not lie, but it did not tell the entire truth either.

Context: Four-day cricket has a different calculation

The Ranji Trophy is first-class cricket. It is not a long version of T20 or one-day cricket. Captains must balance runs, time, pitch behaviour and points. A first-innings lead matters, while an outright victory offers the strongest points reward. Punjab’s declaration at 592/9 was therefore a tactical decision designed to create time for a result.

Punjab’s innings was built on continuity. Overnight centurions resumed their work, and Sanvir Singh reached 205, Salil Arora made 144 and Emanjot Chahal scored 122. Three centuries and a double century suggest a deep batting card rather than one player rescuing the side alone.

The Dharamsala match moved in the opposite direction. Himachal Pradesh and Rajasthan exchanged 20 wickets on the first day. Rajasthan were dismissed for 78, while Himachal made 153 and took a 75-run first-innings lead. Yet Rajasthan reached 297/4 in the second innings, leading by 222 with six wickets in hand.

Nobody had that on the bingo card eight months ago: a side collapsing for 78 and then producing 297/4 in the same match. That is the hard lesson of first-class cricket. Conditions can change faster than reputations.

Core analysis: Sanvir’s 205 needs context

Sanvir Singh’s 205 is a major first-class innings. A double century requires concentration, stamina and the ability to expand an innings without losing control. Selectors will record it, especially because it came in a four-day domestic competition.

The context matters, however. Sanvir batted on a platform already created by Punjab’s other batters. His 205 was an outstanding extension of a strong innings, not a rescue mission from a collapsing position. That distinction does not reduce the achievement; it makes the assessment more accurate.

Domestic coverage often turns one large score into a prediction about technique, international readiness and future market value. The better questions are harder: can Sanvir handle movement away from home? Can he score when the ball is older and the pitch offers uneven bounce? Can he repeat the performance in a second innings? One score cannot answer those questions.

Based on my years of watching matches, a batter’s next difficult innings often tells us more than his biggest score. A flat pitch reduces the bowler’s options. Good batting remains essential, but the surface and the quality of the attack must be part of the calculation.

Salil Arora’s 144 gave the innings structure, while Chahal’s 122 showed how later-order batters can convert a favourable position. The phrase “cashed in on the platform” is useful here: it recognises the value of the innings while preserving its context.

Punjab’s most significant achievement was not simply producing three centuries; it was avoiding a major batting slowdown. That depth created the freedom to declare at 592/9. The declaration also placed responsibility on Punjab’s bowlers. If Andhra bat for a long period, Punjab may secure only a first-innings advantage rather than an outright victory.

Dharamsala: conditions changed the match

Dharamsala is the most instructive match of the round. Twenty wickets on Day One followed by Rajasthan’s 297/4 on Day Two cannot be explained only through batting quality or bowling weakness. The available information does not confirm the exact weather or pitch cause, but a reduction in early seam assistance is a plausible explanation.

The arithmetic is clear. Rajasthan made 78 in the first innings, Himachal made 153, and Rajasthan’s second-innings 297/4 produced a 222-run lead. Opener Rohan Rajbhar’s 140 stabilised the innings, while Mahipal Lomror contributed 97 at No. 3.

If the surface remains favourable, Rajasthan can build an imposing lead and put Himachal under severe pressure. If the pitch deteriorates, Himachal can still return to the match. Six wickets in hand provide security, but they also represent the remaining risk.

Dharamsala shows why first-day batting numbers can become misleading by the second day. Rajasthan’s 78 does not prove that the batting unit is fundamentally weak, just as 297/4 does not permanently establish Himachal’s attack as poor. The match is a study in condition dependence.

The missing names problem

There is an important information issue. The supplied headline names Urvil and Pradosh, but the available match details contain no score, team or role for either player. The information instead focuses on Sanvir Singh, Salil Arora, Emanjot Chahal, Rohan Rajbhar and Mahipal Lomror.

The explanation may be that part of another match was omitted, or that the headline and supplied body do not match. It would be irresponsible to invent performances for Urvil or Pradosh. The same caution applies to Sanvir: 205 is an opportunity, not a complete career verdict.

The next three innings—particularly away from home and in a difficult first-innings situation—will tell us whether this was a breakthrough pattern or a single-match spike. Domestic cricket rewards attention for one big innings; sustained performance changes selection conversations.

The counterargument

Perhaps Dharamsala’s change was not only about the pitch. Rajasthan’s batters may have altered their plans after the first-innings collapse. Rajbhar may have left the new ball better, Lomror may have reduced his risks, and the partnership may have forced Himachal’s bowlers into long spells.

Punjab’s 592/9 should also not be dismissed as a flat-pitch accident. Three centuries and a double century require decision-making and concentration. A helpful surface can support a score, but it cannot bat for a player across 200 runs.

The issue is not whether the performances deserve praise. They do. The issue is how quickly praise becomes prediction. Sanvir’s 205 is evidence, not a final conclusion; Rajasthan’s 222-run lead is a strong position, not a result.

Takeaway

Punjab’s bowlers will decide whether the declaration becomes a masterstroke or merely a first-innings advantage. At Dharamsala, Rajasthan’s remaining wickets and the surface on Day Three will determine whether the visitors press for victory or face a renewed fight.

Sanvir Singh’s next difficult innings will matter more than this double century alone. The missing Urvil and Pradosh references must also be checked against the full scorecards. In domestic cricket, noise lasts a day; repeated performance lasts much longer.