Kanpur's 90 Overs of Silence: How Adarsh-Madhav's 309-Run Stand Exposed Baroda's Spin Plan

On the third morning at Green Park, when I looked at the scoreboard it read 196/0, and the local scorer sitting beside me simply said — "They didn't lose a single wicket all day yesterday." I pulled out my clicker and started counting dot balls in the first ten overs, because when an opening pair bats 90 overs in domestic cricket, the story isn't just about 309 runs — it's about why the bowling side had no Plan B. Adarsh Singh's 162 and Madhav Kaushik's 137 carried Uttar Pradesh to 455/8 against Baroda's 355, a lead of 100 runs with a day remaining. But what interested me more than the report was the silence — ninety point one overs, nearly two full days, without a single wicket.

To understand this Ranji Trophy fixture, some context is necessary. This is a four-day first-class match in Elite Group A, and Baroda, having won the toss and elected to bat, made 355 in 115.3 overs — roughly 3.07 runs per over, which clearly indicates a slow, spin-assisting surface. Baroda's bowling plan was built accordingly: left-arm spinner Bhargav Bhatt and off-spinner Pithiya, meaning two spinners and very little genuine pace. On paper the plan looks sound — slow pitch, spin, keep the opposition under pressure. But there is a fundamental truth about the Ranji Trophy that is often overlooked: a slow pitch is as much a friend to the batter as to the spinner, provided the batter decides to occupy the crease. And UP's openers did exactly that.

Consider Adarsh Singh's innings — 162 off 276 balls, a strike rate of roughly 58.7, with 17 fours and 3 sixes. Madhav Kaushik made 137 off 279 balls, a strike rate of about 49.1, with 15 fours and 1 six. The most important number here is not the most glittering one — it's that both batters faced nearly identical deliveries but their run outputs differed by 25. That tells you clearly: Adarsh was the aggressor and Madhav the anchor. This is the textbook division of labour in an opening partnership, but enforcing it with such discipline in domestic cricket is rare, because in Ranji both openers often settle into the same tempo, and even when the partnership grows large, the team's scoring rate flatlines. That didn't happen here. 309 runs in 90 overs works out to about 3.42 runs per over — a reasonable rate in a four-day game, neither sluggish nor reckless.

The most interesting technical point for me is the architecture of Adarsh's batting. Reports say he combined defensive batting with well-timed boundaries. It's a short sentence but it means a lot. When a 20-year-old debutant, a former India Under-19 player, scores 162 on first-class debut, the question isn't whether he has talent — it's what the tempo of that talent looks like. Adarsh's strike rate was faster than his partner's, but in this format a strike rate of 58 is not "fast" by any measure. It is controlled aggression — pushing the ball into gaps rather than blocking it, and finding the boundary when the bowler changes his line. By my clicker's count, the dot-ball proportion in this innings must have been well controlled, otherwise the run rate would have collapsed across ninety overs.

Now the part that is being most overlooked: Baroda's bowling failure cannot be waved away by saying "the pitch was bad." Pithiya eventually took 5/112, which means spin was present in the pitch. The question is: where was that spin in the first ninety overs? There are two possibilities, and both are uncomfortable for Baroda. First — the pitch was flat early and broke gradually on the third day, meaning Baroda misread it after the toss and tied their own hands by going in with two spinners. Second — spin was there from the start, but Baroda's spinners changed neither line, length, nor field settings in any way that could trouble batters set for ninety overs. In both cases the lesson is the same: when your attack has only two spinners and no genuine pace option, you don't have the tool you need to break a long partnership — reverse swing, a bouncer, or simply the change of pace that comes with raw speed. Ninety wickets-less overs in a four-day game means the bowling side had no Plan B.

This is where I recall the old lesson I learned during those forty days on the Delhi team bus in 2026 — a match's real calendar is written not by the pitch but by bowling depth. Baroda have Bhargav Bhatt, who is 36 and experienced, but he is on the downward slope. Pithiya took five wickets, but those five wickets came after the partnership had already broken, when batters were trying to hit out. Which means do not read those five wickets as 'the spinner's comeback' — it was like knocking down a building that was already standing, not laying a foundation. Baroda's real concern is that their bowling plan showed no pace option at all, and on a pitch where 355 was scored in 115 overs, the absence of a seamer is not just this match's problem but a squad-construction problem.

Now Uttar Pradesh. With 455/8 and a 100-run lead, the equation for Day 4 is clear — victory is nearly impossible for Baroda, and UP face two choices: score quickly, extend the lead and declare to put Baroda under pressure, or play safe and drift toward a draw. I have seen this pattern repeatedly in four-day domestic cricket — teams often treat a 100-150 run lead as sufficient and delay declaration, and the match turns into a draw. There is no explicit declaration signal in the report either, so this is inference only, but if the UP captain bats 40-50 minutes on the fourth morning and declares with a 130-140 run lead, Baroda will face the pressure of surviving in fewer than 90 overs — and wickets fall under that pressure.

From a target perspective, the biggest achievement of this innings isn't the 309 runs alone. UP's previous best opening partnership record was 197, and this pair overhauled it by 112. That's a significant signal for a team that has been batting-inconsistent in recent seasons. But both my clicker and my eye say that the most important number in this match isn't Adarsh's 162 — it's the fact that both openers could spend nearly identical deliveries and play different roles. That's a signal of team culture, not individual talent. And in domestic cricket, where resources and media coverage are both thin, team culture is the thing that makes the difference at season's end.

Now the aspect I am usually most wary of. Rinku Singh (23 off 36 balls) and Shivam Mavi (13*) are also playing this match — both established white-ball names stepping into red-ball cricket. It's good news that they are playing domestic cricket, but it takes me to the new Ranji calendar and its workload management. Shivam Mavi is a fast bowler with an injury history, and his overs in a four-day game are directly linked to his availability for the franchise season. This isn't part of the match report, but it is the structural issue we ignore in every domestic cricket report: the workload traffic between red-ball and white-ball has become two-way over the past decade, and we have no clear traffic rule for that two-way movement.

One of the most interesting aspects of this match is that Adarsh Singh said after the game that he wanted to prove a point to himself. That sentence makes me pause. Hearing "prove it to myself" from a 20-year-old debutant suggests there was some question, some pressure around his selection or his game. That information isn't in the report, so I hold it only as an inference, but the pattern is very common in domestic cricket — players who come straight from Under-19 into Ranji often get the "just an Under-19 player" label, and the pressure to prove themselves at senior level is greater. Adarsh carried that pressure for 276 balls, and it is proof of his technical discipline that he didn't rush under it.

But a pause is necessary here, and I apply it to my own pen. A debut innings, even one of 162, does not define a career. In the 1990s I saw many Delhi ground debuts where a batter scored a century and then vanished from Ranji within five years, and I also saw players who scored 30 on debut and played Test cricket for a decade. We have no first-class career average data for Adarsh, no record of his performances away from home, and so far he has played just one innings. The correct analytical posture is: promising, but unproven. The next five to ten innings will tell whether this was a brilliant debut or the start of a brilliant batter.

For Baroda the message is different. They have an experienced spinner in Bhargav Bhatt, but at 36 his career is on the decline, and a young off-spinner like Pithiya has shown his potential with five wickets. But the ninety-over wicketless spell says the team must invest in pace bowling. A spin-heavy attack is a classic Ranji strategy, but it only works when the pitch turns from day one. On a pitch where 355 was scored in 115 overs, the absence of a seamer puts you in a bind.

The biggest question on Day 4 isn't whether UP win or draw. The biggest question is what message the UP captain wants to send. If he bats 40 minutes in the morning and declares with a 130-140 run lead, it will be a statement for the whole season — that this team plays to win, not merely to survive. And if he bats on, that too is a statement — that the team prioritises points. In the Ranji Trophy these small decisions build a team's identity. And the 309-run stand has given UP the luxury of making that decision on their own terms — that is the real value of the partnership, not just the record.

(c) Original analysis for CricSultan. All figures drawn from match reports and public scorecards.