492 Runs, 309-Run Opening Stand and Still a Draw: Questions on Uttar Pradesh's Killer Instinct, Baroda's Lower-Order Grit Saves the Match

I have been reading scorecards for over a decade and a half, but some scorecards don't tell their own story — they need to be told. The Ranji Trophy match between Uttar Pradesh and Baroda is one of them. At first glance, it looks like an ordinary draw. But if you go a little below the surface, a different picture emerges: Uttar Pradesh controlled the cricket for four days, scored 492, put together a record 309-run opening stand, reduced Baroda to 115/6 — and still could not win.

For me, this is not just a result. It points to a mistake that often goes unnoticed in domestic cricket: control and victory are two different things. In reply to Uttar Pradesh's 492, Baroda were bowled out for 355. On paper, that was a 137-run lead. But a lead means nothing until you can convert it into wickets.

Context: The Ranji Calculation — Four Days, Time and Patience

Ranji Trophy is first-class cricket, and the strategy here is completely different from limited-overs cricket. Strike rate matters less than staying at the crease, consuming time, and preserving wickets. When I started 'The Numbers Desk' early in my career, the first thing I learned was that every format has its own 'ledger.' T20's ledger is strike rate; first-class cricket's ledger is the number of overs and time spent at the crease.

In this match, Uttar Pradesh scored 492 in the first innings, including a 309-run opening stand between Adarsh Singh (162) and Madhav Kaushik (137). That partnership lasted 541 balls — roughly 90 overs. This is not just a statistic; it was a direct assault on Baroda's bowlers' morale. Aryan Juyal's 67 then took the total to 492.

In bowling, Mahesh Pithiya took 5/112 for Baroda — in an innings where 492 runs were scored, taking five wickets is indeed a big achievement. For Uttar Pradesh, Kartik Yadav took 5/104 and Karan Sharma 3/39. On paper, this was Uttar Pradesh's dominance.

Core: When 115/6 Could Not Be Converted into Victory

This is where the real story begins. In the second innings, Baroda were at one point 115/6 and still 22 runs behind. On any normal day, Uttar Pradesh would be expected to win from this position. But what Baroda captain and lower-order batter Atit Sheth (unbeaten 40) and Mahesh Pithiya (14 off 84 balls) did might look 'slow' by conventional cricket analysis, but in the context of first-class cricket, it was an extremely skilled strategy.

Pithiya's 14 off 84 balls — that's a strike rate of 16.67. If you look at it through a T20 lens, it would seem like a wasted innings. But the question here was not strike rate; it was about consuming overs. Baroda's only objective was to exhaust whatever overs Uttar Pradesh's bowlers had left. And this is where conventional data analysis fails — because there is no column in the scorecard for 'overs saved.'

I built an xG model during the 2026 Russia World Cup, and there I learned that France won the knockout stages with lower xG than their opponents — meaning efficiency matters more than dominance. The same principle applies here. Baroda's recovery from 115/6 was an example of 'efficiency,' not 'dominance.'

There was a major change in Uttar Pradesh's bowling — Prashant Veer, who had taken no wickets in the first innings, returned with 3/42 in 17 overs in the second. His economy was 2.47 runs per over. This was clearly a strategic adjustment — perhaps better use of assistance from the pitch, or a change in bowling angle. But the biggest problem was that Uttar Pradesh could not break the final partnership.

This raises a question I ask in every analysis: did Uttar Pradesh choose the right time to declare? Did they use aggressive field settings? Was the bowling rotation correct in the final session? The answers to these questions are not in the original report, and that is the limitation of my model — I can only show what is recorded in the scorecard, not what was thought on the field.

Contrarian: 'Uttar Pradesh is a strong team' — This Conclusion Is Incomplete

There is a common perception here that I would like to challenge. After the match, it is easy to say that Uttar Pradesh is a strong team and Baroda survived. But look at the points table — Uttar Pradesh were second with 18 points, Baroda third with 17, and Vidarbha topped with 26. That means the gap between Uttar Pradesh and Baroda was just one point.

This is not a 'strong vs weak' story. It is the story of a competitive domestic group where small opportunities make a big difference. And here I must clarify another point — the real crisis for the Ranji Trophy is not that Test cricket is dying, but that the domestic tournament's media presence is shrinking. I have seen from inside the newsroom how no one covers Ranji until the knockouts. This match is also a victim of that neglect — 492 runs, a 309-run partnership, five-wicket hauls — and yet no major headlines.

One concern for Baroda is that their top order collapsed to 115/6. The lower order saved them, but will it happen every time? This could become a pattern that hurts them later. In my experience, teams that rely on lower-order rescue eventually fail at some point in a long tournament.

Takeaway: Signal for the Next Round

Uttar Pradesh's upcoming schedule is not easy — Madhya Pradesh, defending champions Jammu and Kashmir, and table-toppers Vidarbha (February 1-4, Nagpur). This is the phase that will reveal whether Uttar Pradesh's 'cricket of control' can be converted into victories.

The biggest question for me is not who won or who saved the draw. The question is: does Uttar Pradesh have that 'killer instinct' that can break the final partnership from 115/6? My spreadsheet cannot answer that — it can only show how big the opportunity was. And if the same situation repeats in Nagpur next month, it won't just be a draw — it will be a pattern.