Arora and Sanvir dig Punjab out of 71/5; Tamil Nadu grind through Day 1

The first day of the current Ranji Trophy round told two completely different stories: at one ground a first innings that looked finished at 71 for 5 ended the day with its strongest partnership intact; at the other, Tamil Nadu batted at a single, patient tempo from the first over to the last. One thing was common to both: wickets fell early, batting took charge afterwards, and by the closing hour the bowling sides had run out of answers. For Punjab the day began in the worst possible way. The scorecard read 71 for 5. That is the kind of position where the dressing room stops counting runs and starts counting overs. But no further wicket fell before stumps. Salil Arora finished unbeaten on 111 and Sanvir Singh on 100, and their unbroken sixth-wicket stand changed the entire character of the innings. The honest reading of that recovery is that it was not purely a batting achievement. Andhra's new-ball bowlers created the collapse. Kavuri Saiteja took 3 for 65 and K. S. Narasimha Raju 2 for 41, and without that opening spell there would have been no rescue to write about. Any report that credits only the batsmen's 'character' while reducing the bowlers to a line of figures tells half the story. The collapse had a clear sequence. The first wicket fell at 20. Prabhsimran Singh made 24, Jashanpreet Singh 1, captain Uday Saharan 0 and Ramandeep Singh 0. From 20 for 1 to 71 for 5, Punjab lost four wickets, two of them without scoring, and the captain among them. That combination — an opener's wicket followed by a middle-order slide with the captain out for nought — is the hardest to absorb. A scoreline of 71 for 5 does not necessarily mean the pitch was unplayable. It usually means the bowlers found a line and length that left the batsmen unsure whether to play or leave, and that the pressure was shared between two bowlers rather than created by one. Raju's 2 for 41 and Saiteja's 3 for 65, with the wickets split between them, point to exactly that kind of sustained pressure. Arora, 23, came in at number six and made the season's fourth hundred, reaching three figures off 186 balls. He ended on 111 not out with 11 fours and 3 sixes — 62 of his runs came in boundaries, which says his innings never lost its scoring intent even while it was absorbing pressure. His season numbers give the innings its context: 110 against Assam, 107 against Chhattisgarh, 151 against Hyderabad, and now 111 not out. Four hundreds in a domestic season is an achievement on its own; four against different opponents in different conditions is a statement about consistency rather than form. That said, calling him the most consistent batsman of the season is an opinion, not a statistic. The statistic is four hundreds. The opinion is what it means for his standing in the domestic game. The distinction matters because domestic reporting often repeats a single judgement until it reads like fact. Sanvir Singh's hundred deserves separate attention. He came in at number seven with the innings already five down, and his job was to survive first and score second. Reaching 100 meant batting long, and ending the day unbeaten meant the innings still had a lower order and a first-innings target ahead of it. The partnership was balanced rather than purely defensive. Arora kept scoring at a healthy rate; Sanvir held his end and let his partner keep his rhythm. That division of labour is what makes a rescue stand work. There is also a captaincy dimension. Saharan was out for a duck in the first session. When a captain falls without scoring and the side is five down for 71, the pressure in the dressing room is at its highest. Two batsmen batting through to stumps in that situation is a psychological result as much as a technical one. At the other venue, Tamil Nadu chose to bat against Chandigarh, where they are the visiting side. Electing to bat as the away team usually signals an intention to post a total and put the hosts under pressure. The day suggested Tamil Nadu's method was accumulation rather than acceleration. Vimal Kumar was the first wicket to fall, for 11. Narayan Jagadeesan then produced the most fluent innings of the day: 52 off 88 balls with eight fours. He was out at 92 for 2, which means 81 runs had been added between the first and second wickets, with the bulk of them coming from him. Baba Indrajith took over the anchor role. He made 51 off 112 balls, which means he left or defended well over half the deliveries he faced. For a bowling side that is the most frustrating kind of innings, because such a batsman neither gives you a wicket nor lets you dictate the tempo. Indrajith was out at 231 for 2, which makes the second-wicket stand worth 139. That stand was the backbone of the innings: it took the new ball out of the equation, forced the spinners into long spells and made the fielding captain rethink his plans. Bhagmender Lather was Chandigarh's most successful bowler with 2 for 47. The wickets column is credit; the runs column shows the batsmen never let him settle. Nikhil Sharma and Nishunk Birla took a wicket each, and Birla's was the key one — Indrajith, the man who had faced the most balls. The most striking innings of that match belonged to Paul, who faced 215 deliveries and hit 12 fours. Batting 215 balls is roughly three and a half sessions of occupation. But his total score is not recorded in the available data, which makes it impossible to judge the tempo of his innings accurately. A batsman who faces 215 balls and is on 100-plus is telling a different story from one on 60. We will not guess. What is verifiable is the occupation itself, and that he was the most stable end of the innings for most of the day. His full name is also missing from the available details; only 'Paul' is recorded. The likely full name cannot be printed without confirmation. C. Andre Siddarth made 13. At stumps Guruswamy Ajitesh was 34 not out off 46 balls with six fours. That rate means he was not simply surviving — he was putting pressure back on the bowlers, which gives Tamil Nadu an option to accelerate on the second morning. The comparison between the two matches exposes a habit in domestic reporting. Punjab's recovery from 71 for 5 was framed around the batsmen's resilience, while Andhra's bowlers were reduced to a set of numbers. That is a systematic asymmetry: wins are credited to batting virtue, collapses are blamed on batting failure, and the bowling craft that produced the situation disappears from the story. In this match the largest single performance of the first session belonged to Saiteja and Raju. Taking five wickets before lunch is the hardest task in the game, and the batting recovery that followed was only possible because two batsmen at numbers six and seven decided to absorb that pressure. Chandigarh's bowling tells a similar story. Four wickets fell — Lather 2, Sharma 1, Birla 1 — and then nothing. The figures reconcile with the wickets lost, but the pattern is the same as at the other ground: once batsmen are set and the ball is old, wickets become hard to find. The shared thread across both matches is that the bowling side had a window in the first session and lost it. That is a normal pattern in first-class cricket, but it appeared twice on the same day. For Punjab the question on day two is how deep the innings can go. Arora and Sanvir are both set and both have batted a full day. The obvious plan is to bat through the first session and put Andhra under scoreboard pressure. The longer Punjab bat, the less time Andhra have, and that is Punjab's biggest advantage. For Andhra the challenge is different. Their first session was excellent; now they must reproduce that discipline in long spells with an older ball. Saiteja and Raju will carry the main load. If the second morning passes without a wicket, Punjab will reach a total from which Andhra's plans will have to change entirely. For Tamil Nadu the question is how long the innings lasts. Paul has already faced 215 balls; if he bats on, the first innings will stretch. Ajitesh is scoring quickly and a partnership between the two would lift the run rate. Chandigarh need early wickets. They did not look physically spent at stumps, but they did not look likely to break through either. One or two wickets in the first hour would keep the total near 400; without them, the hosts will be under pressure on two fronts. One transparency note. The figures in this report come from the available scorecard details, and several remain subject to official confirmation. Neither Punjab's nor Tamil Nadu's innings total is recorded in the source, so neither has been stated here. For the sixth-wicket stand two figures circulate — 205 and 211 — and 211 is the one consistent with the two unbeaten scores (111 plus 100), so the stand is described here as unbroken rather than given a precise number. Paul's score and full name, and the identity of Saiteja's third wicket, are also missing. These figures should be republished only after reconciliation with the official scorecard. It should also be noted that this report contains no direct quotations, because none were available in the source material. Every analytical judgement here is derived from the scorecard and the shape of the day's play, not from anything a player, coach or selector said. Readers should treat the assessments of individual ability accordingly. The broader point is that the first day of a Ranji Trophy match rarely reveals the whole picture. Punjab showed depth by recovering from 71 for 5. Tamil Nadu showed intent by batting slowly and staying in. Both now have to prove on the second day that the recovery and the occupation can last. The lesson of the day is simple: an innings can survive five wickets falling, provided somebody decides to bat to the close.