Karan's Unbeaten 162: The Real Ledger of UP's Fightback on a 2.71-Per-Over Pitch

The 37th over of the first day was the last over of the day. UP were 67 for 4, scoring at 1.8 an over. A rain-shortened day, a new ball doing something off the seam, and a top order that could not negotiate the movement. By the close of the second day, the same side, against the same opposition, had reached 328 for 9 in 121 overs.

In the 84 overs in between, 200 runs arrived for the loss of three wickets. Of those 200, 145 came from one bat — Karan Sharma, unbeaten on 162.

I will not keep an emotional ledger of the 162. I will keep a ledger of the 24-hour gap, because that gap is the only verifiable evidence in this match report. Two different games were played on the same pitch within a day. The question is who changed the rules of the game: the batter, the surface, or the structure of the bowling attack.

Context: four-day format, two days left

The Ranji Trophy is India's premier domestic first-class competition, played over four days at 90 overs a day. In that structure time is an asset, but it is not spent at a uniform rate. A first-morning session and a fourth-afternoon session cannot be bought in the same currency. This entire match sits inside that unequal exchange.

Puducherry, at home, won the toss and chose to field, meaning UP batted first. Day one was truncated by rain to 37 overs; day two delivered roughly 84 overs. Two days remained at stumps on day two.

The bowling figures are the largest clue. Udeshi took 4 for 86, Ankit Sharma 3 for 73, and both are left-arm orthodox spinners. Seven of the nine wickets fell to spin. That ratio is not normally produced by a fresh, damp, seaming surface in Indian domestic first-class cricket; it is produced by a dry, gripping, slow one. The pitch was probably spin-friendly from the start and more so by day two.

I normally verify a pitch read against two independent video sources. This report does not allow that luxury. The source is an unattributed, wire-style match report. Its scaffolding — scores, overs, bowling figures — is internally consistent, but two cautions apply: there is a quote that is plausibly attributed to the wrong cricketer, and the batting order cannot be reconstructed chronologically across several paragraphs. The quote about being 'trapped' most likely refers to Shivam Mavi's lbw, with Mavi on the return-to-play path. The venue is not named in the source. I will not hide these gaps, because a gap in the ledger is still a gap.

Core: two sessions, two different instalments

The damp session: the 37-over instalment

A run rate of 1.8 on day one is not an accident; it is a scheduled payment. Choosing to field in a four-day game means pushing the opposition's top order into the most hostile 90 minutes of the match — new ball, damp pitch, seam movement, uncertain footwork. UP's 67 for 4 is the first instalment of that payment.

This is where an old line of mine returns: a collapse is not a moment; it is a ledger of small concessions. Sixty-seven runs in 37 overs means 1.8 an over — the batters were not merely losing wickets, they were not even getting the chance to leave the ball. When the leave rate drops, wickets are only a matter of time.

The drying session: 200 in 84

The picture inverted on day two. The pitch dried, the ball gripped, and yet the runs came at 2.38 an over — slightly above the match rate of 2.71, far above day one's 1.8. From 128 for 6 to 328 for 9, three wickets fell and 200 runs arrived.

The real information sits here: the pitch changed less in the batter's favour on day two than the structural pressure of the bowling attack changed against itself. Two left-arm orthodox spinners turn the ball the same way, from the same angle, from the same release point. A batter's decision model works for the first fifteen overs; after forty, that model becomes habituated.

The arithmetic inside 145

This is the most important read. UP made 200 on day two; Karan made 145. The rest made 55 combined. In percentage terms, 72.5.

When one batter scores 72.5 per cent of a stand, it is not a partnership; it is a solo account with temporary tenants. That does not diminish Karan — it reclassifies the work. An unbeaten innings at nine down involves strike rotation, refusing the second run, and choosing boundaries with the tail. Reaching 328 for 9 means he bought those overs with the last man.

Why 2.71 is the biggest number

The typical run rate in Indian domestic first-class cricket sits between 3.0 and 3.4. Here it was 2.71. That gap forces a revaluation of the 162. On a 2.71 pitch, 162 is the equivalent of 200-plus elsewhere — but that conversion can only be computed with balls faced, and balls faced are absent from the report. So I will not call the 162 match-winning. I will call it the maximum use of a surface-determined price.

Bowling load: the 84-over invoice

A derivable figure exists here. If Udeshi conceded 86 at roughly the innings rate, his workload is about 32 overs. Ankit Sharma's 73 runs works out to about 27. Together, roughly 59 of 121 overs — nearly half the innings in the hands of two left-arm spinners. That is an estimate, not an exact figure, since individual economies vary. But the order of magnitude is clear.

The question is what those shoulders, lower backs and fingers say on days three and four after 84 overs in a day. The romantic international conversation about load management tends to stop at fixture congestion and squad depth. Domestic first-class cricket writes the example in plain ink: a spinner past thirty overs in a day loses both turn and drift by the fourth afternoon.

328 for 9: standing with two days left

Batting at nine down with two days remaining cuts both ways. Each extra over adds runs at 2.71 and adds to Puducherry's bowling invoice. But the structural truth is that UP has already spent its best batting window. It batted on the easiest days of the pitch; Puducherry will bat on days three and four, when the ball grips harder.

Contrarian: the 162 is not heroism, it is the invoice of a one-angled attack

The conventional read is simple: UP collapsed, Karan Sharma dragged them up. True, but incomplete, because it removes the structure of Puducherry's attack from the ledger.

Puducherry's seven spin wickets raise a question: did they have only one angle? Udeshi and Ankit are both left-arm orthodox. To a right-hander, both turn the ball the same way, create the same deflection, pose the same footwork problem. For roughly half of 121 overs, the batter's problem did not change shape.

Variety in cricket works not through the amount of turn but through breaking the decision cycle. An off-spinner arriving after 25 overs disrupts prediction; a left-arm orthodox arriving after 30 reinforces it. Karan Sharma took the benefit of that habit.

Here I concede my own limit. For this read to be falsifiable it needs two conditions. One, the two spinners' individual economies must not diverge sharply; a wide gap would prove one was genuinely more dangerous and the 'one-angle' thesis would fail. Two, the wickets that fell on day two must not be overwhelmingly one bowler's; if they were, the partnership was broken by an individual, not sustained by structural sameness. Without ball-by-ball data neither can be settled. So I offer a testable hypothesis, not a verdict.

A second contrarian point concerns the scoreboard. 128 for 6 to 328 for 9 looks like a fightback, but structurally it may be insufficient. On a day-three surface, 328 against Puducherry's line-up may be defensible without being comfortable. The spin attack did not fail; under pressure it confessed its own limits — the open question is whether UP's top order did the same.

And this is where professional habit helps. The Third Half is where the first two halves confess. Here the third half is the fourth day and the post-match, where Puducherry will state what the plan was and UP will state whether 328 was ever enough.

Takeaway: the first session of day three is the audit

Three verifiable things to watch in the first 90 minutes of day three.

First, how quickly Puducherry introduce a different angle. If no right-arm spinner or old-ball seam spell arrives inside twenty overs, the attack's structure has not changed and Karan's habituated advantage survives intact.

Second, Udeshi's over count. If the 59-over estimate holds, his revs and drift should drop on day three. If they do not, my load model is wrong and I will say so.

Third, how many Karan adds with the last man. Every ten runs pushes the first-innings par estimate upward, and the more the pitch wears, the more a score in the 300s is worth.

The result is not yet written, but the question is settled. Is 328 enough? The answer is not inside Karan's 162. It is in the hands of Puducherry's third bowler — who he is, and from which angle he arrives.