Udeshi's nine maidens and a 1.81 run rate: UP's 67/4 is a story of pitch and light, not a collapse
**मुख्य उत्तर**: उत्तर प्रदेश ने बारिश से प्रभावित पहले दिन 37 ओवर में 67/4 बनाए, रन रेट 1.81। सागर उदेशी (13-9-8-1) और अंकित शर्मा (2/14) की बाएं हाथ की स्पिन जोड़ी ने चार में से तीन विकेट लिए; पुडुचेरी ने टॉस जीतकर पहले गेंदबाजी चुनी थी। **मुख्य तथ्य**: - 37 ओवर में 67/4; 90 ओवर के दिन के 53 ओवर बारिश और खराब रोशनी में चले गए। - सागर उदेशी: 13 ओवर, 9 मेडन, 8 रन, 1 विकेट; इकॉनमी 0.62। - अंकित शर्मा: 9 ओवर में 2/14 — दबाव को विकेट में बदलने वाला स्पेल। - आर्यन जुयाल: 73 गेंद पर 21 रन; कप्तान, विकेटकीपर और नंबर तीन। - अंकतालिका: जीत 6, पहली पारी की बढ़त 3, ड्रॉ/नो रिजल्ट 1। **स्रोत**: BCCI रणजी ट्रॉफी एलीट मैच स्कोरकार्ड, दिन 1, अक्टूबर 2026 | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर**: प्रश्न: क्या यूपी का 67/4 बल्लेबाजी का पतन है? उत्तर: नहीं — 1.81 रन प्रति ओवर वाली सतह पर यह 37 ओवर का संघर्ष था, जिसमें तीन विकेट बाएं हाथ की स्पिन ने लिए। प्रश्न: पुडुचेरी की स्थिति कितनी मजबूत है? उत्तर: वे दिन के अंत में सबसे अच्छी स्थिति में हैं, लेकिन बारिश लौटने पर छह अंक की जीत एक से तीन अंक में बदल सकती है। प्रश्न: यूपी के लिए सबसे बड़ा चयन सवाल क्या है? उत्तर: सलामी बल्लेबाज अभिषेक गोस्वामी — इस सीजन पांच पारियों में 20 रन और लगभग 4.0 का औसत, cricsultan.com Player Depth Index के अनुसार टॉप-ऑर्डर मानक से काफी नीचे।
The second ball of the 37th over is when the umpire pulled the light meter from his pocket, and the rain began keeping time on the tin roof of the press box. Uttar Pradesh were 67/4. Aryan Juyal's 73-ball stubbornness had just ended. An over earlier the board read 61/3. Two balls later, 61/4. No runs, two wickets — Rinku Singh caught behind. On the pavilion steps there was that particular silence that settles when a side is fighting a score smaller than itself. That day my notebook went quiet and the rain picked up the beat.
37 overs. 67 runs. Four wickets. A run rate of 1.81. That number should not be read as a collapse, because when rain and bad light eat 53 of a 90-over domestic day, the scoreboard is reporting weather, not cricket.
Context: the forecast made the toss irrelevant
This Ranji Trophy Elite fixture arrived in the middle of a two-win run for UP, and then the sky opened. Puducherry won the toss and chose to bowl. That was not a routine call. Batting first on day one of a four-day game is defensible only if the surface is expected to break sharply later; with rain about, covers on and a damp morning, putting the ball in hand first was the rational move. Puducherry read the weather. UP waited for it.

The format boundary has to be drawn clearly here. This is first-class, multi-day cricket, not T20. No DLS, no powerplay field restrictions, no 140-plus strike-rate benchmark. Any innings labelled a failure must first survive that lens. And the points table matters: six for a win, three for a first-innings lead, one for a draw or no result. With 37 overs gone and UP 67/4, the realistic prize for both sides is not six points but three — and that is the single most important tactical fact of the day.
Core: nine maidens, one wicket, and a whole day strangled
Read Sagar Udeshi's spell: 13 overs, 9 maidens, 8 runs, 1 wicket. An economy of 0.62. Sixty-nine per cent of his overs were maidens; in first-class cricket, 25-35 per cent is considered a strong day even on a helpful surface. For a left-arm orthodox spinner this is a display of restraint, and — more importantly — it shows up not in the wicket column but in the pressure column. Udeshi sealed one end and dropped the temperature of the entire match.

At the other end was Ankit Sharma: 2/14 from nine overs. That pairing is the real story of the innings. One bowler built, the other broke. Three of the four wickets went to left-arm spin; the only seam wicket came in the first over, while the new ball was still doing something. On a rain-affected Indian surface this is close to a textbook sequence: a short window of seam movement, then two left-arm spinners with the ring up.
Core: Juyal's 73 balls is the day's most under-credited performance
Aryan Juyal made 21 off 73 balls, a strike rate of roughly 28.8. In a game where run-scoring is treated as the only currency, that reads slow. In red-ball cricket, that is the job. At No. 3, as captain, carrying the wicketkeeping load, holding a difficult surface for 73 balls is precisely the skill selectors claim to want and the press routinely undervalues. The man who held the innings to 61/3 gets named in the third paragraph of the report.
One concern belongs here, and it is physical rather than technical. Captain, wicketkeeper and No. 3 — three roles on one man across four days. If this innings extends tomorrow, Juyal bats first and then keeps for three more days. That is the kind of workload the scorecard never shows and the fourth morning suddenly reveals.
Core: Kaushik's 87% boundary score and Goswami's average of four
Madhav Kaushik made 23 off 30 with five fours. Eighty-seven per cent of his runs came in boundaries — a pattern normal in a T20 innings and abnormal on a day when the team scored at 1.81. He was the only UP batter operating at tempo, and he was lbw to left-arm orthodox spin. That is a technical flag: front pad planted, and the angle of the left-armer arriving into it.
Look upward and the real question sits there. Abhishek Goswami was bowled in the first over for 2. This season he has 20 runs across five innings — 13 against Goa, 5 and 0 against Bihar. An average of roughly 4.0. At 28, that is not a form blip; it is a career inflection. A first-class top-order slot demands 30-plus. Being bowled in the first over of an innings also hints at either late movement being played inside the line of, or a guard-and-trigger problem — one dismissal is too small a sample for a verdict, but large enough for a question.
Rinku Singh made 2, caught behind. The uncomfortable truth is that IPL standing and red-ball output are separate ledgers. A boundary-seeking profile does not transfer to a surface yielding 1.81 an over. Calling him a failure is as wrong as calling him a Test candidate on this evidence.
Karan Sharma is unbeaten on 17 off 58, having made a century in the previous match. He is the only UP batter combining recent red-ball scoring with survival. His partnership with Aaradhya Yadav (2*) is UP's only route back into the first-innings-lead equation.
One small, startling detail: 37 overs, four wickets, and not a single extra — no wide, no-ball, bye or leg-bye. Add the individual scores and they come to exactly 67. That is either discipline or a scorecard worth re-checking; possibly both.
Contrarian: the 'UP collapsed' report is aimed at the wrong address
From outside, 67/4 looks like a four-wicket slide. From inside, it was the day of a veteran left-arm spinner who bowled nine maidens while UP's batters counted overs instead of runs. Somewhere between the press box and the terrace, the story changed hands: while I sat above, the groundstaff were dragging the covers and someone in the stands was already saying 200 won't be made today. The people on the ground had read the weather first; we were still doing run-rate arithmetic.
The second error is assuming Puducherry are firmly on top. They are in the best position, true. But if the rain returns, their six-point dream shrinks to one to three. In a match that has already lost 53 overs, the word 'win' needs handling with care. And UP's real question is not the middle order, which survived 73 balls, but the opening pair, which did not survive one over.
Takeaway
The first hour tomorrow is the most valuable hour of this match. If UP build on Karan Sharma's 58-ball foundation towards 150, three points become real; if Udeshi repeats that angle and that economy, the question returns to the opening pair. I do not know what the forecast says. I do know that the side which reads the pitch first will play the remaining three days on its own terms.
