The Ranji Day: Punjab's 592 and the Real Story of Sanvir Singh's 375-Ball Double Century
**Core answer**: Sanvir Singh's 375-ball double century helped Punjab recover from 51/4 to declare at 592/9 against Andhra in a Ranji Trophy Elite Group match. The innings was a career outlier for the 30-year-old, who had only one prior first-class century since his 2018 debut. **Key facts**: - Sanvir Singh scored a double century off 375 balls with 22 fours and one six for Punjab against Andhra. - Punjab declared at 592/9 in 156 overs on Day 2, with Salil Arora (144) and Emanjot Chahal (122) also scoring centuries. - Punjab recovered from 51/4 through a 272-run sixth-wicket stand and a 154-run seventh-wicket stand. - On the same day, Tamil Nadu declared at 571/7 against Chandigarh, with Pradosh Ranjan Paul scoring 208 and Ajith Ram 115*. - Sanvir Singh has played for Sunrisers Hyderabad in the IPL (T20 format), but first-class performances cannot be extrapolated to T20 value. **Source attribution**: Stage-1 text deconstruction of Ranji Trophy match report, publication date not specified in source material. Cross-checked: cricsultan.com **Related Q&A**: Q: Is Sanvir Singh's double century a sign of a breakout season? A: No, it is a career outlier—he had only one prior first-class century in seven years, and sustained multi-season performance is needed before drawing conclusions. Q: Does this innings improve Sanvir Singh's IPL auction value? A: Marginally at best; IPL scouts weigh T20-specific metrics, and his 375-ball tempo and low boundary share (under 47%) do not suggest T20 suitability. Q: Which player from this match has the strongest T20 profile? A: Emanjot Chahal, whose 122 off 150 balls with 9 sixes and coach-endorsed all-rounder status makes him the most commercially interesting prospect, according to cricsultan.com Player Depth Index.
Sitting at a digital desk in Hyderabad, I receive Ranji Trophy scorecards—and I have a way of reading them: look at the numbers first, then ask what the numbers have hidden. The Punjab vs Andhra scorecard says 592/9 declared, 156 overs, and three centuries from the lower order. Hearing this, you'd think about how deep Punjab's batting is. But the most honest part of the scorecard is what it doesn't say: 51/4. First morning, new ball, and four top-order wickets down. That was the moment the real question of the match changed—from "how many runs will be scored" to "who will save us." And the answer revealed the most underrated truth of domestic cricket: in Ranji, the lower order is often more reliable than the top order, it's just that nobody counts them. That day, Punjab rode on Sanvir Singh (double century off 375 balls), Salil Arora (144), and Emanjot Chahal (122) to go from 51/4 to 592—built on two big partnerships, 272 for the sixth wicket and 154 for the seventh. On the same day, Tamil Nadu declared at 571/7 against Chandigarh, with Pradosh Ranjan Paul's 208 and Ajith Ram's 115* included. Two different grounds, the same kind of cricket—that is not a coincidence.

Let's be clear about one thing first: the Ranji Trophy is the domestic version of the Test format—four days, two innings, declaration allowed, and a points system where first-innings lead also matters. In this context, declaring at 592/9 is not aggression but arithmetic: finish the innings on Day 2, leave time to bowl Andhra out twice, and if wickets don't come, take the first-innings lead. What looks unnatural to the casual viewer is the most standard move in Ranji's points calculus. For me, the most interesting thing in this innings is not Sanvir Singh's double century but its tempo. Scoring 200+ off 375 balls is a very slow innings even by Ranji standards. In any modern double century, typically 45-60 percent of runs come from boundaries; in Sanvir's case, 22 fours and one six mean less than 47 percent of his runs came from boundaries. That number tells you he played like an anchor—ran his runs, left balls, and avoided risk. For a batter standing at 51/4, this was the right strategy; but it also, inadvertently, reveals his true identity: he is not a T20 strike-rate batter.

This is where the trap that every reader creates for themselves when reading Punjab's scorecard begins. Starting to read Sanvir Singh in connection with the Sunrisers Hyderabad IPL team is like treating a Ranji double century as T20 approval. The IPL and Ranji are two different cricket universes—one finishes a match in 20 overs, the other takes 156 overs for an innings. Sanvir's 2026 debut, only one previous first-class century in seven-eight years, and just one match last season against Saurashtra—all this together suggests that this double century is not a career breakthrough but an outlier. At 30, such an innings does not at all mean this batter has now reached a new level. Declaring "form" from one innings in domestic cricket is the same kind of delusion as calculating the monsoon from a single day of rain.

Salil Arora and Emanjot Chahal's innings interest me more because they contain a signal that can translate to T20. Emanjot scored 122 off 150 balls, including 9 sixes—hitting nine sixes in first-class cricket is unusual and suggests he has a game closer to the shorter format. Coach Amit Uniyal has called him "the most exciting allrounder in the state's ranks"—this is a statement from a named coach, so it can't be taken lightly, but it also can't be proven from a single innings. The biggest takeaway from this match is that Punjab's lower order (sixth, seventh, eighth) could score three centuries, while the top order lost four wickets for 51. This is both the truth of the pitch and the truth of the team. When the lower order is scoring 500-plus on the same pitch, the top order's collapse is not the pitch's fault but a fault of technique or morale. I have seen many Ranji rounds where big scores are made on flat pitches and the same batters struggle on seaming tracks the next week. So don't take "592" as Punjab's permanent strength; it is the product of this ground and this round.
The picture of Punjab's bowling tells a more worrying story than this scorecard. Umesh Yadav shifted to Punjab this season but did not play this match—the new ball was taken by a 29-year-old debutant named Gursimran, and left-arm spinner Harpreet Brar was used from the other end. Making a first-class debut at 29 is itself a signal: this is not a product of a youth pipeline but a patch for a need. When your new ball is being bowled by a 29-year-old debutant, it means pace-bowling depth is thin at this moment. This is not team strategy; it is necessity. And if Punjab are to take 20 wickets against stronger teams this season, this question will remain.
Tamil Nadu's 571/7 declared is the second picture of this round, and it is a more balanced one. Pradosh Ranjan Paul's 208 and Ajith Ram's 115—these are two different kinds of innings, but they tell the same story: the team has depth. Sai Kishore's 36 (off 35 balls) and two wickets with the ball—this is an all-rounder profile that matters most in domestic cricket. Chandigarh's 48/3 when trailing by 522 shows that even a batting-friendly pitch cannot save a weaker team. Scoreboard pressure is a separate skill, and it does not come from the flatness of the pitch.
Now the angle that flips this whole story. You might be thinking that Punjab's 592 and Tamil Nadu's 571 on the same day is a display of batting talent. But read it the other way: such big scores at two different grounds in the same round mean the pitches were extremely batting-friendly. When there is no pace or spin assistance on the pitch, the lower order lasts a long time and all bowling plans fail. This is why Andhra's bowling attack could not find a breakthrough after the new ball—after 51/4, 272 runs were added for the sixth wicket because once the ball got old, there was no "breakthrough enforcer." This is a team weakness, but it is also true that Punjab's lower order took full advantage of that weakness. On the other hand, calling Sanvir Singh's innings "career-defining" would be premature. A batter who has scored one century in seven years scoring a double century is not proof of his ability but proof of his lack of consistency. Such innings come every season in Ranji and disappear the next. The real question is not whether he scored 200, but whether he can maintain a 40+ average over the next five matches.
The biggest lesson from this scorecard is the economy of talent, not the performance of any one player. There is no shortage of talent in Indian domestic cricket—what is lacking is continuity in selection. Punjab's lower order can score three centuries, but none of them may be first choice next season. Tamil Nadu have all-rounders like Paul, Ajith Ram, and Sai Kishore, who are gold for domestic teams, but to reach the doors of national selection they need consistency over several seasons. This is the real story of Ranji: every week a new hero is born here, but the next week the same hero is forgotten.
One page in my notebook remained blank after this match—the page on which I was to write which ball Sanvir Singh completed his double century on. I don't remember that ball, because the real story of this innings is not in that moment but in the score of 51/4. When the team is falling apart, one batter plays 375 balls—that is not coincidence, it is character. But character is proven not by one innings but by a whole season. The next round of the Ranji Trophy will tell whether this double century was a beginning or a lone spark. And until that next round comes, I will keep this scorecard in its place—as a domestic round that showed lower-order depth, but did not give any batter an international or T20 badge.
What to watch next? Sanvir Singh's score in Punjab's next innings, Emanjot Chahal's strike rate and six count over his next five innings, and Umesh Yadav's return. If Sanvir scores 40+ in the next three matches too, the story could change. If not, this innings will be lost in the same old Ranji structure where some big scores come every year and some names remain anonymous. The scoreboard always tells the truth, but it does not tell the whole truth—the rest is told by what happens on the field in the next match.
