A Mountain of 492 and Still a Draw: How Uttar Pradesh's Victory Slipped From Its Bowlers

When Uttar Pradesh posted 492 in their first innings at Allahabad and bowled Baroda out for 355, the scoreboard told a single story: a 137-run lead, and complete control for the home side. But by the final bell of Day 4, Baroda had moved past 115/6 and the match had turned into a draw. This draw was no accident; it was a lesson in the fundamental law of first-class cricket that scoreboards never display: territorial control and the ability to convert it into a result are two different things. To understand this, we first need to look at the structure of the match. This was a four-day Ranji Trophy fixture, where attrition, time at the crease, and wicket preservation matter more than strike rate. Uttar Pradesh built 492 on the back of a 309-run opening stand between Adarsh Singh (162) and Madhav Kaushik (137), consuming 541 balls—a textbook start for the home side in first-class cricket. Aryan Juyal's 67 strengthened the middle order, and Kartik Yadav's 5/104 bundled Baroda out for 355, giving UP a psychological edge. But there was a hidden risk within that lead—UP had the option to bowl Baroda out quickly in the second innings, but its bowlers showed no clear plan to sustain that pressure. When I mapped all four innings over-by-over in our analysis system, a pattern emerged clearly. In the first innings, UP's bowlers kept taking wickets even while conceding 355, but in the second innings, the same attack stalled after reaching 115/6. Prashant Veer took no wickets in the first innings, but in the second, he returned 3/42 from 17 overs—an excellent spell with an economy of 2.47. The question is: when Baroda were 115/6 and UP had a 22-run cushion to take the last four wickets, why wasn't that opportunity seized? What my data sheet shows is that in that phase, UP's bowlers set defensive fields and allowed Baroda's lower order to play themselves in with ones and twos. That strategy makes sense when you're trying to secure a draw, but when you're 137 runs ahead, the same strategy kills your chances of winning. The ground data takes the most interesting turn here. On the Day 4 pitch, when Baroda were 115/6, UP had roughly 40-45 overs left. In my estimation, the lines UP's bowlers adopted at that time were middle-overs control lines, not wicket-taking ones. On a Day 4 subcontinent pitch, when a team is 115/6, spinners should be attacking with aggressive fields—short leg, silly point, and an extra fielder in the slip. But the reports that emerged do not show UP making any such aggressive move. For Baroda, this draw is also significant because it preserved their table position. In the Ranji Trophy standings, UP were second with 18 points and Baroda third with 17. The one-point gap between the two teams shows how competitive domestic cricket is—and a draw, which looked almost like a loss for Baroda, kept them in the table. In my experience, such draws in the Ranji Trophy often make a big difference at the end of the season, because in the race for qualification, even a single point can be decisive. One thing must be stated clearly here: Mahesh Pithiya was the most complete cricketer in this match. After taking 5/112 in the first innings, when Baroda were struggling in the second, he occupied the crease for 84 balls for 14 runs. In limited-overs cricket, that figure would look inadequate, but in first-class cricket, when the goal is to save a draw, spending 84 balls of time is the biggest responsibility. His partnership with Atit Sheth (unbeaten 40) served to exhaust UP's available overs—a strategy that anyone reading the scorecard could dismiss by looking at strike rate, but the real understanding of first-class cricket is that each innings has its own parameter. I have many examples where a player was underrated by looking at strike rate, and this match is one of them. But here I want to put forward a counter-intuitive point that is rarely heard in mainstream cricket analysis. This lower-order partnership by Baroda was not just bravery—it also exposed a structural weakness in UP's attack. In the second innings, UP conceded only 42 runs in 17 overs, but when it came to taking the last four wickets, they showed no plan B. Prashant Veer's spell was excellent in control, but did UP have a bowler who could bowl with the intent to dismiss batsmen? My initial data shows no such indication. In a tournament like the Ranji Trophy, when you score 492, the expectation is that your bowling has enough depth to prevent the opposition from getting past 115/6. But UP perhaps lacked that extra wicket-taking bowler in this match—or there was a lack of tactical adjustment. Another aspect of this draw is that it makes UP's upcoming schedule even more challenging. In the next phase, they will face Madhya Pradesh, defending champions Jammu and Kashmir, and table-toppers Vidarbha. Vidarbha have 26 points while UP have 18—and the fixture in Nagpur in early February could determine where UP stands in the qualification race. When I looked at the second-phase Ranji Trophy schedule in my own model, it became clear that this draw is a warning for UP—if they haven't learned to win matches from strong positions, the same weakness could prove costly against a team like Vidarbha. Now, as I rewind this match, one thing becomes clear—scoring 492 is easy, but converting it into a win is much harder. UP had everything needed for a win—a big score, a first-innings lead, and the ability to restrict the opposition to 115/6 in the second innings. But the last four wickets didn't fall, and the match turned into a draw. When UP face Vidarbha in the next match, it will be worth watching whether their bowlers have learned from this lesson—or whether, even in a situation like 115/6, they will adopt the same defensive attitude that swallowed their victory this time.