67/4 at 1.81: How Puducherry's Two Left-Arm Spinners Bound UP on a Rain-Hit Day

I open scorecards late at night in Kolkata. I count deliveries the way other people count regrets — quietly, past midnight. What caught first that day was not a wicket. It was Sagar Udeshi's spell: 13-9-8-1. Nine maidens in thirteen overs, roughly 69 percent of his bowling without a single run conceded. An economy of 0.62, against the 2.5 that counts as good control on a helpful first-class surface. Uttar Pradesh's innings stopped at 67/4 in 37 overs, a run rate of 1.81. Puducherry had won the toss and chosen to bowl, and UP arrived with two wins from two.

One line in the card kept me up: total extras, zero. Four wickets down, 37 overs bowled, and not one wide, no-ball, bye or leg-bye. Add the six scores — 2, 23, 21, 2, 17 and 2 — and you get exactly 67. My spreadsheet has thousands of rows; the noise never makes it into them. So I do not accept such a figure with my eyes closed. I am flagging that line as pending verification, openly.

The Ranji Trophy arithmetic is clean: six points for a win, three for a first-innings lead, one for a draw or no result. With 37 overs gone and four wickets down, the real prize for both sides is not six points but three. That is why Puducherry's decision to field first became the single highest-leverage call of the day. Batting first on day one of a four-day game is defensible only if the surface is expected to break sharply later; with cloud around, covers on and dampness in the pitch, Puducherry read it the other way — a short seam window, then grip.

The day's quota was 90 overs; play gave us 37. Roughly 53 overs went into the rain. DLS does not apply here. The risk is not a revised target, it is a no-result. And this is where an old habit earns its keep: a Russian summer taught me that weather is the variable nobody puts in the model. Watching France's pressing triggers in 2026 taught me the same lesson — the side that reads the weather starts a step ahead. The venue is not stated in the material available to me, so I will keep the coastal-Puducherry and northeast-monsoon connection inside the bracket of inference, not fact.

The real story is the bowling pair. Udeshi sealed one end and Ankit Sharma bought the wickets at the other — 2/14 from 9 overs. That is the classic structure of paired pressure: a pile of maidens at one end, a bowler at the other whose economy forces risk. Fielders were up in the ring, so even singles were expensive. A run rate of 1.81 in first-class cricket is never the product of a storm; it is the product of a grind.

The top of the order is where the problem is clearest. Abhishek Goswami was bowled for 2 in the first over. His season reads 20 runs in five innings — 13 against Goa, 5 and 0 against Bihar. An average near 4.0. At 28, this is a career inflection, not a form blip. Being bowled in the first over of an innings hints either at playing inside the line of late movement or at a guard and trigger issue. One delivery cannot carry a conclusion, but five innings at 20 runs has already carried one.

Madhav Kaushik made 23 off 30 with five fours — 87 percent of his runs in boundaries, a T20 pattern sitting inside a 1.81 team rate. He was lbw to left-arm spin, the angle into the pad that left-arm orthodox creates. Rinku Singh made 2, caught behind. His 'form' is a white-ball reputation, not a red-ball number. Calling his innings a failure while ignoring the surface is unfair; calling him a Test prospect on this evidence is unsupported.

The most under-credited innings belongs to Aryan Juyal: 21 off 73 balls. At No. 3, as captain and wicketkeeper, occupying 73 balls on that surface is the job itself. The source frames it as 'some application', which undersells it. Yes, 61/3 became 61/4 in two balls and zero runs — the kind of session-boundary event that in a four-day match inverts an innings' temperature.

Karan Sharma is 17 off 58 not out, a centurion in the previous match, with Aaradhya Yadav on 2*. That pair is UP's only route back into the first-innings-lead equation, and this is where the media narrative and the scorecard disagree.

Here is the hard part of the work: build the most attractive reading at full strength, then turn it over. The attractive reading is that UP collapsed. Build it — four down, 1.81, opener bowled in over one, a wicket immediately after the captain's grind. Clean story. Now turn it: 67 for 4 in 37 overs is a collapse only on a fair surface. Against dampness, cloud and two left-arm spinners, it is survival. The real failure is not the batting, it is the selection structure — a 28-year-old opener averaging around 4 who is still being picked five innings in.

The second reversal is about the weather. Puducherry being 'firmly on top' is directionally right but unconditional only if play resumes. Another washout caps their advantage at one to three points instead of six. The same rain that compressed the day into 37 overs can rewrite both teams' risk math. Puducherry's squad profile belongs in this picture too — professionals who moved in, like Ankit Sharma and Gaurav Yadav, meaning a thin core and experience over depth. Such sides over-perform on helpful surfaces and thin out on flat ones.

Tomorrow is the match's biggest question. A full 90-over day puts the first-innings lead around 200 and turns Karan Sharma's brief from surviving into extending. If the rain returns, even three points vanish and UP buys another week before answering questions about its top order. My eye stays on Goswami's next innings — after 20 runs in five, a sixth can prove either the selectors' patience or its end.

In one line: the rain made the day short, but Udeshi and Ankit Sharma made the innings short — and the real score is not 67/4, it is UP's fifth consecutive bad day at the top.