Uttar Pradesh Miss Victory Despite 309-Run Stand: Atit Sheth and Mahesh Pithiya's Resistance Earns Baroda a Draw

Some Ranji Trophy matches are remembered less for the scoreboard than for the hours during which batters refuse to leave the crease. The contest between Uttar Pradesh and Baroda belongs to that category. Uttar Pradesh established a commanding position with 492 in the first innings, built around a remarkable opening partnership of 309 between Adarsh Singh and Madhav Kaushik. Baroda replied with 355, leaving Uttar Pradesh with a substantial first-innings advantage of 137 runs. The second innings appeared to be moving towards a Uttar Pradesh victory when Baroda slipped to 115 for six. Yet Atit Sheth and Mahesh Pithiya refused to surrender the remaining wickets. Sheth finished unbeaten on 40, while Pithiya faced 84 deliveries for his 14 runs. The match ended in a draw.

The most interesting image from this contest is not simply the 309-run partnership or Uttar Pradesh's total of 492. It is the final partnership that gave a team staring at defeat an opportunity to save the match. Cricket often celebrates the batter who scores quickly, but in four-day cricket the most valuable batter can sometimes be the one who abandons the urge to score quickly. Pithiya's 84-ball innings offers a clear illustration.

The match's story reached cricket discussions and supporters' messages before the final interpretation was settled. One supporter focused on Uttar Pradesh's imposing total; another asked how the side could fail to win from such a commanding position. Years of reporting have taught me that every result contains a story that the final score alone cannot explain. WhatsApp can deliver a story before it reaches the press box, but a message must be verified before it becomes a fact. The score progression in this contest supports one clear conclusion: Uttar Pradesh controlled much of the match but failed to take the final wickets.

The context: Uttar Pradesh's batting created the advantage

Uttar Pradesh's first innings established the foundation of the contest. Adarsh Singh and Madhav Kaushik added 309 for the opening wicket, facing 541 deliveries between them. In four-day cricket, such a partnership represents much more than a large number of runs. It keeps the opposition in the field for an extended period, forces the captain to use several bowling options and places a sustained physical and tactical burden on the fielding side.

Adarsh Singh scored 162, while Madhav Kaushik contributed 137. Their innings meant that Uttar Pradesh's middle order did not have to begin under immediate pressure. Aryan Juyal then added 67, giving the innings further stability.

Based on my years of watching cricket, the value of a long opening partnership cannot be measured only by the runs accumulated. It is also important to consider the pressure placed on the opposition's bowling resources. A partnership lasting 541 deliveries required Baroda's bowlers to work for long periods. Yet Baroda did not disappear from the contest entirely.

Mahesh Pithiya claimed five wickets in Uttar Pradesh's first innings, giving his side a route back into the game. His figures were 5 for 112. When a team has conceded a 309-run opening stand, taking wickets in the middle phase becomes especially important. Pithiya supplied that intervention.

Uttar Pradesh eventually finished on 492, while Baroda had made 355 in their first innings. The resulting lead was 137. That was a significant advantage in a multi-day contest, but a first-innings lead does not automatically produce a victory. The bowling side must still take wickets in the second innings, while the captain must manage the remaining time effectively.

That is where the match's tactical story became more complicated.

Uttar Pradesh's advantage and Baroda's challenge

After taking a 137-run lead, Uttar Pradesh had a straightforward objective: dismiss Baroda quickly enough to leave a realistic window for victory. According to the available score details, Baroda had fallen to 115 for six in the second innings. It was a potentially decisive position for Uttar Pradesh.

However, six wickets down and an innings completed are two very different things. Lower-order batters are often underestimated, although they can change the use of time in first-class cricket. Top-order players are generally expected to build runs, but when the lower order is asked to save an innings, its priorities change.

Atit Sheth and Mahesh Pithiya accepted that responsibility for Baroda. Both focused on preserving their wickets. Sheth remained unbeaten on 40, while Pithiya scored 14 from 84 balls. A spectator accustomed to limited-overs cricket might consider that a modest contribution. In the circumstances of this match, it was considerably more valuable.

To understand Pithiya's innings, it is necessary to return to the match situation. Baroda were 115 for six and still behind Uttar Pradesh. Trying to score quickly or play ambitious shots could have increased the risk of another dismissal. The safer route was to judge each delivery carefully, avoid unnecessary risks and occupy the crease for as long as possible.

Mahesh Pithiya's dual contribution shaped the final phase

Pithiya contributed in two distinct phases. In the first innings, he took five wickets and disrupted Uttar Pradesh's batting. In the second, he faced 84 deliveries as a batter and helped his side preserve the draw.

This is the aspect of his performance that ordinary runs-and-wickets summaries can overlook. The 5 for 112 represents a bowling achievement. The 14-run innings is a batting figure. Viewed together, they explain the different responsibilities he fulfilled during the match.

In the first innings, Pithiya found important wickets amid Uttar Pradesh's substantial total. In the second, when Baroda were in trouble, he understood the responsibility of batting for survival. Scoring runs was not his primary objective. He needed to buy time for his team.

In my experience, contributions of this kind in domestic cricket are often overshadowed by the glamour of headline performances. Spectators remember centuries, five-wicket hauls and winning margins. The effort of a batter who faces more than 80 deliveries to save an innings may receive less immediate attention. Pithiya demonstrated another dimension of his value in this contest.

There are limits to what the available figures can tell us about his batting technique. We do not have a breakdown of the deliveries he left, defended or played from the front foot. Nor do we have the field settings or a ball-by-ball account of Uttar Pradesh's plans. It would therefore be inappropriate to invent technical details. The strongest supported conclusion is that Pithiya faced 84 deliveries and survived during a decisive phase.

Sheth's unbeaten 40 was equally important. He took responsibility for holding the innings together and remained at the crease until the end. In such circumstances, the value of a partnership is greater than the sum of two individual scores. One batter provides stability to the other, both challenge the bowlers' plans and the opposition captain is forced to consider alternative options.

The partnership between Sheth and Pithiya denied Uttar Pradesh the final breakthrough. The match ended in a draw, with Baroda having used the remaining time successfully.

Prashant Veer's second-innings impact

Prashant Veer produced a notable second-innings performance for Uttar Pradesh. He took three wickets for 42 runs in 17 overs, an economy rate of approximately 2.47 runs per over. In first-class cricket, that combination of control and wicket-taking is valuable.

Veer had taken no wickets in the first innings. His three wickets in the second innings strengthened his role in the attack. This change should not be viewed merely as a comparison of figures. Bowlers often work under different circumstances in the second innings. The match situation, batting objectives and opposition strategy can all change.

Veer's performance showed that he made an important contribution to Uttar Pradesh's attack. However, the available details do not establish the technical method behind his wickets. We cannot say whether they came through swing, seam movement, spin or batting errors. His figures of three wickets in 17 overs are sufficient evidence of a useful performance without requiring unsupported technical claims.

Kartik Yadav also took five wickets for Uttar Pradesh, conceding 104 runs, while Karan Sharma claimed three for 39. These figures show that Uttar Pradesh had bowlers capable of taking wickets. The problem was not a complete absence of wicket-taking ability. It was the failure to remove the final partnership after reaching a promising position.

There is an important distinction here. Bowling well and taking enough wickets to win a match are not always the same thing. Uttar Pradesh reduced Baroda to six wickets down, but could not complete the task.

The decisive difference: control versus conversion

Read only through the scorecard, Uttar Pradesh appear to have held the stronger position. A first-innings total of 492, a lead of 137 and Baroda reduced to 115 for six in the second innings all suggest a substantial advantage.

The draw, however, shows that controlling a match and winning it are separate stages. Time, wickets, bowling changes and the mental discipline of the batters must come together in the final phase.

Uttar Pradesh did well in the opening stages with both bat and ball. Baroda made 355 in the first innings, leaving Uttar Pradesh with a sizeable lead. Once six wickets had fallen in the second innings, Baroda were forced into a defensive position. Sheth and Pithiya then turned the final phase in their team's favour.

The obvious question for Uttar Pradesh is whether the side had sufficient time and an effective attacking strategy to take the remaining wickets.

The available information does not provide a definitive answer. We do not have the declaration timing, remaining overs, bowling changes, field settings or a detailed account of the final session. It is also unclear how many overs remained when the last partnership began. Criticising a particular captaincy decision would therefore be premature.

Nevertheless, the result demands tactical examination. When the opposition are 115 for six and trying to save a match, the bowling side must prioritise wickets. Simply restricting runs is insufficient. Plans that encourage errors, timely bowling changes and balanced field settings become essential.

Baroda, meanwhile, demonstrated that the lower order's value is not limited to adding a few runs. Players must understand which risks are acceptable in a particular match situation and which are unnecessary. Sheth and Pithiya recognised that distinction.

The Ranji Trophy's real value: long innings and difficult decisions

Over the years, I have watched the perceived importance of domestic cricket change. International matches and franchise competitions attract enormous attention, and the Ranji Trophy can sometimes slip behind them in public discussion. Yet anyone trying to understand the depth of Indian cricket cannot afford to overlook this competition.

Here, players are tested beyond their ability to score quickly or influence a few overs. They must bat for extended periods, bowl under different conditions and adapt their strategies as the match develops.

This contest offered several examples. Adarsh Singh and Madhav Kaushik demonstrated the ability to build a long partnership. Pithiya's five-wicket haul showed his bowling contribution. The same Pithiya then faced 84 deliveries in the second innings, illustrating the value of defensive batting. Veer completed a disciplined 17-over spell in the second innings.

These performances should be seen as part of the domestic development system rather than isolated events. The Ranji Trophy tests players in different roles. Batters must occupy the crease, bowlers must maintain their control across extended spells, and lower-order players must understand what their team needs from them.

I have often asked supporters how closely they follow domestic cricket. For many, the main story begins when a player earns a place in the national side. But years of domestic work precede that selection. The long Ranji Trophy winter, second-team cricket and opportunities at state level are all part of that process.

I took the long route to the World Cup and found the real match. The decisive work often begins long before the major event watched by millions. Uttar Pradesh's contest with Baroda is another reminder of that longer journey.

Uttar Pradesh and Baroda in the points table

The significance of this draw extends beyond the match itself. According to the supplied table information, Vidarbha led with 26 points. Uttar Pradesh were second with 18 points, while Baroda were third with 17. The gap between Uttar Pradesh and Baroda was only one point after four matches.

That position suggests a competitive group. Uttar Pradesh may feel disappointed because they held the stronger position for much of the contest. Yet their second-place position also demonstrates why a single result should not define an entire campaign.

Baroda should not interpret the draw as an unqualified success either. The team recovered from a difficult position, but losing six wickets for 115 in the second innings raises questions about top-order stability. A strong team cannot expect its lower order to rescue it in every match.

Uttar Pradesh have been listed as facing Madhya Pradesh, defending champions Jammu and Kashmir, and Vidarbha in the second phase. The fixture against Vidarbha from February 1 to 4 could become particularly important. Vidarbha were ahead in the table, and Uttar Pradesh would have an opportunity to reduce the gap.

It would be premature to make firm qualification predictions at this stage. Such an assessment would require the results of the remaining fixtures, the complete points regulations and the updated positions of all teams. For now, the most useful approach is to identify what Uttar Pradesh must improve before the next round of matches.

Positive signs and warnings for Baroda

Baroda's final-phase resistance demonstrated mental resilience. Even after losing six wickets, the players did not surrender the contest. Sheth scored an unbeaten 40, while Pithiya faced 84 deliveries with patience.

But this performance should not be treated as proof that Baroda controlled the entire match. The team had scored 355 in the first innings and had fallen to 115 for six in the second. It saved a difficult situation, but still needs to examine its early batting vulnerability.

A team's strength cannot be judged only by its best performance. It is also necessary to examine how frequently the team finds itself in trouble. In this match, Baroda's lower order performed well, but depending on similar rescues repeatedly would be dangerous.

The next step for the team management should be an assessment of top-order stability. One match is insufficient to establish a recurring pattern. Previous and subsequent scorecards will be needed to determine whether early wickets have been a regular problem or whether this was an isolated occurrence.

What the draw means to supporters

Supporters look for a story between victory and defeat. That task becomes more difficult when a match ends in a draw. Uttar Pradesh supporters will remember the 492-run total and the 137-run lead. They will also ask why their team could not take the final wicket after reducing Baroda to 115 for six. Baroda supporters will remember the resistance of Sheth and Pithiya.

There is one important lesson for every supporter. In four-day cricket, the result is not determined only by which team scores more runs. The use of time is equally important.

Uttar Pradesh used time and runs effectively through their first innings. Baroda used time to its advantage during the final phase of the second innings. Both sides demonstrated their strengths at different stages. The difference was that Uttar Pradesh's strong position did not become a victory.

During the 2026 Champions Trophy in England, conversations with supporters taught me that fans want to understand the struggle behind the statistics. I still remember the voices of Indian supporters outside The Oval. They remind me that cricket's story belongs to more than the eleven players on the field. Supporters are part of it too. In this contest, a Uttar Pradesh supporter may have expected victory, while a Baroda supporter would have continued hoping until the final wicket fell.

Since then, I have understood the importance of giving supporters a place in sports reporting while distinguishing emotional expectations from match facts. Whatever the emotional reaction to this result, the scorecard remains clear: Uttar Pradesh held the stronger position, and Baroda saved the match.

The road ahead: Uttar Pradesh must improve its finishing plan

The most important lesson for Uttar Pradesh is not about batting but about bowling in the final phase. Scoring 492 and taking a 137-run lead were signs of the team's strength. But when the opposition are 115 for six, the bowlers must take the remaining wickets to turn that advantage into a victory.

In future matches, Uttar Pradesh will need to examine its plans against the lower order. Aggression alone will not be enough. Bowling availability, spell lengths, field settings and the time remaining must be considered together.

Veer's second-innings performance was encouraging. His three wickets in 17 overs showed that he could make an impact under pressure. Kartik Yadav and Karan Sharma also highlighted the attack's wicket-taking potential. The challenge is to convert those contributions into victories by developing a plan for the final partnership.

Baroda face two challenges. They must strengthen their top-order batting and carry the confidence gained from this draw into the next fixtures. The partnership between Sheth and Pithiya provides a useful example, but the team cannot expect a lower-order rescue every time.

Mahesh Pithiya deserves particular attention after this match. Taking five wickets and then batting patiently in the second innings demonstrated a contribution across two disciplines. However, any larger conclusion about his future should wait until his performances across subsequent matches establish consistency.

The final signal: who will correct the mistake in the next innings?

Every deadline has a rhythm; I listen for the beat before I write. In this contest, Uttar Pradesh's story began with a 309-run partnership, reached 492 and then failed to produce a victory despite Baroda being reduced to 115 for six. Baroda's story began with the challenge of its first innings and ended with the patience of its final partnership.

It would be wrong to treat this draw as final proof of Uttar Pradesh's failure or as evidence of Baroda's overall superiority. It was one match in which Uttar Pradesh built the stronger position and Baroda managed the remaining time more effectively.

The second phase now becomes the focus. Uttar Pradesh must show that it can combine substantial batting performances with the ability to take the final wickets. Baroda must demonstrate that it can make its top order more stable.

The real Ranji Trophy story often unfolds in the next match. The final wicket did not fall in this contest, but the match has left both teams with important questions. Uttar Pradesh's bowlers must find an answer to the final partnership next time, while Baroda's batters must prove that their side can do more than survive a crisis: it must also establish control from the beginning.