Rain cuts day short as Puducherry spinners hold Uttar Pradesh to 67/4
मुख्य उत्तर: बारिश और खराब रोशनी के कारण 37 ओवर ही संभव हुए, जिसमें उत्तर प्रदेश ने 67/4 बनाया। पुडुचेरी के लेफ्ट-आर्म स्पिनर सागर उदेशी (13-9-8-1) और अंकित शर्मा (2/14) ने दिन पर नियंत्रण रखा। प्रथम श्रेणी मैच में DLS लागू नहीं होता; अगला लक्ष्य पहली पारी की बढ़त है। मुख्य तथ्य: • उत्तर प्रदेश: 37 ओवर में 67/4, रन रेट 1.81; 90 ओवर के दिन 53 ओवर बर्बाद। • सागर उदेशी: 13 ओवर, 9 मेडन, 8 रन, 1 विकेट; इकॉनमी 0.62। • अंकित शर्मा: 9 ओवर में 2/14; एकमात्र तेज विकेट पहले ओवर में। • आर्यन जुयाल: 21 रन, 73 गेंद; करण शर्मा 17* (58), पिछले मैच में शतक। • स्कोरकार्ड में शून्य अतिरिक्त; व्यक्तिगत योग 67। स्रोत: स्टेज-1 मैच रिपोर्ट, 2026 रणजी ट्रॉफी सीज़न (तिथि अपुष्ट)। संबंधित प्रश्नोत्तर: प्रश्न: क्या 67/4 को उत्तर प्रदेश का बल्लेबाजी संकट कहा जा सकता है? उत्तर: एक पारी से यह निष्कर्ष जल्दबाजी होगी; 37 ओवर और 1.81 रन रेट सतह-प्रेरित दिन दिखाते हैं, पर गोस्वामी का लगभग 4.0 सीज़न औसत असली चिंता है। प्रश्न: पुडुचेरी की स्थिति कितनी मजबूत है? उत्तर: मौसम पर निर्भर; खेल होने पर पहली पारी की बढ़त के तीन अंक उसके पक्ष में हैं, लगातार बारिश से यह बढ़त एक अंक में बदल सकती है। प्रश्न: अगले दिन किस पर नजर रखनी चाहिए? उत्तर: करण शर्मा और आराध्य यादव की साझेदारी पर; यही उत्तर प्रदेश को 150 के करीब ले जाकर पहली पारी की बढ़त की दिशा दे सकती है।
I opened the scorecard and saw 67/4 first. Then 37 overs. Then 1.81 runs per over. The three numbers explained the day better than any phrase about a batting collapse. My old notebook still has the 1,214-shot football project from 2026; it taught me to read context before the scoreboard. The same lesson applies to this truncated Ranji Trophy day.
Rain and bad light cut a 90-over day to 37 overs. Fifty-three overs were lost. Uttar Pradesh were 67/4. This is first-class cricket, so T20 benchmarks of 140-plus strike rates and seven-an-over economy do not apply. DLS does not operate in multi-day cricket; the risk is a draw or no-result, not a revised target. In the Ranji Trophy points system, an outright win gives six points, a first-innings lead three, and a draw or no-result one. That single sentence changed the game’s political economy.
Puducherry chose to field. That was the highest-leverage call of the day. The available report does not name the venue, so any pitch reading has to stay provisional. If this was coastal Puducherry in the October-December northeast monsoon window, a damp, covered, tacky surface would typically offer a short seam window and then grip for spin. Puducherry’s decision to bowl first suggested they had read surface and weather together.
Uttar Pradesh arrived with two wins from two. Momentum is not a measurable input; it is a story, not a metric. On a 37-over day, the more relevant question is which side can convert the three-point first-innings lead. Puducherry’s field-first call put their risk on the weather’s side.

The first truth of the day is that 67/4 looks like a collapse in T20 language. In first-class language, it was an extended new-ball phase stretched across a whole day. A run rate of 1.81 across 37 overs says Uttar Pradesh were losing rhythm, not falling apart—they were being ground down. On rain-affected Indian surfaces, the sequence is familiar: a short seam window, then two left-arm spinners with fielders up. That is exactly what happened.
Sagar Udeshi’s spell is the cleanest number of the day: 13 overs, nine maidens, eight runs, one wicket. Economy 0.62. Nine maidens out of 13 is 69 per cent. In helpful first-class conditions, 25-35 per cent maidens is a strong day for a spinner. Udeshi doubled it. His one wicket understates the work; his real job was building pressure at one end.
Ankit Sharma took 2/14 from nine overs. The pairing is the story: Udeshi blocked one end, Ankit bought wickets at the other. Three of the four wickets came from left-arm spin; the only seam wicket was the first-over breakthrough against Abhishek Goswami. That is not merely a bowling card. It is the structure of the day. Puducherry took the short new-ball advantage, then used spin to slow the 37 overs to their tempo.
Aryan Juyal made 21 off 73 balls, a strike rate near 28.8. To a white-ball reader that looks slow. In red-ball cricket, occupying 73 balls at No. 3 is the job. Captain, wicketkeeper and No. 3 is a three-part load, and Juyal still has three more days of keeping ahead of him. His innings is the most under-credited investment in Uttar Pradesh’s day. After his 21 off 73, the score moved from 61/3 to 61/4 in two balls: zero runs, one wicket. That kind of session-boundary event can invert a four-day innings.
Karan Sharma is 17 not out off 58 balls. He made a century in the previous match. Aaradhya Yadav is 2 not out. Uttar Pradesh’s route back runs through these two. If they take the score toward 150, the first-innings-lead equation opens. Karan has recent red-ball form; Aaradhya has time. They need to bat more than 30 overs together.
Madhav Kaushik made 23 off 30 with five fours. Twenty of his 23 runs came in boundaries. That is 87 per cent boundary dependency in a team innings running at 1.81. In T20 that is normal scoring; on this surface it is fragile. He was lbw to left-arm spin, a technical flag for front-pad and planted-foot play against the angle of a left-arm orthodox bowler. One delivery cannot carry a large conclusion, but the flag is worth noting.

Rinku Singh made 2, caught behind by the wicketkeeper. His in-form reputation comes from white-ball cricket. A red-ball day yielding 1.81 an over is not a natural fit for a profile that seeks boundaries between dot balls. IPL standing and red-ball output are separate ledgers. This one innings does not make him a failure, and current red-ball evidence does not make him a Test prospect.

Abhishek Goswami was bowled for 2 in the first over. He has 20 runs in five innings this season: 13 against Goa, 5 and 0 against Bihar. An average near 4.0 at 28 is not a form blip; it is a career inflection point. One match can lie; a season rarely does. Five innings are speaking clearly. Being bowled in the first over suggests a new-ball issue with line or trigger, but one dismissal without ball-tracking data keeps that inference at low confidence.
The scorecard has another oddity: zero extras. The individual scores sum to exactly 67: 2+23+21+2+17+2. Four wickets in 37 overs with no wides, no-balls, byes or leg-byes is rare. That number deserves a second scorecard check, because zero extras can also be a recording omission. In data journalism, an improbable figure earns verification before narrative.
The broadcast booth hears noise; the notebook hears patterns. Here the pattern was a maiden at one end, wickets at the other, and a 1.81 run rate in between. It is easy to call 67/4 a Uttar Pradesh batting crisis. But 37 overs, 1.81 an over and a 69 per cent maiden spell together tell a story about surface and time. Correlation is not causation. Udeshi’s maidens and Uttar Pradesh’s slow scoring look causally linked, yet rain and light were also shaping the day. The two need separating.
The opposite overcorrection is just as risky. If everything is blamed on weather and surface, Goswami’s season average near 4.0 disappears from the audit. Top-order instability is the real problem. Puducherry’s spin pair exposed it; they did not create it. The surface slowed the middle order and magnified an older weakness at the top.
Puducherry are directionally on top, conditionally. If play resumes, the three-point first-innings lead is theirs to lose. If rain continues, that lead can shrink to one point. Some BCCI domestic knockout fixtures carry a reserve day; its applicability to a group match needs verification. Without a reserve day, a draw or no-result is structurally more likely. That is why Puducherry’s field-first call was the day’s biggest bet, and it has not fully landed.
With 37 overs gone and Uttar Pradesh 67/4, the realistic prize for both sides is three points, not six. Uttar Pradesh’s route is direct: Karan Sharma and Aaradhya Yadav must bat 30-plus overs and take the score toward 150. If Uttar Pradesh fold for 120, Puducherry get the first-innings lead cheaply. If they reach 150-170, the match changes colour.
Three things to watch over the next three days: Goswami’s place, Rinku’s red-ball valuation, and Juyal’s workload. Goswami’s season average is the clearest selection question. Rinku’s red-ball metric must stay separate from his white-ball reputation. Juyal’s 73-ball patience will show up in the points or in the keeping load.
In Bangalore, the data desk is another kind of stadium. The question from here is whether domestic cricket will treat weather as part of the XI when it picks teams and plans innings, or whether it will call 67/4 a batting failure and move on.
