Baroda's Draw That Matters More Than UP's Near-Win: From a 309-Run Stand to 115/6
**मुख्य उत्तर**: उत्तर प्रदेश ने रणजी ट्रॉफी मैच में 492 का स्कोर बनाकर बड़ौदा को दूसरी पारी में 115/6 पर ला दिया, लेकिन अतित शेठ (40*) और महेश पिथिया (14 रन, 84 गेंद) की अटूट साझेदारी ने मैच ड्रॉ करा दिया; उत्तर प्रदेश तालिका में 18 अंकों के साथ दूसरे स्थान पर है। **मुख्य तथ्य**: - आदर्श सिंह (162) और माधव कौशिक (137) की 309 रन की साझेदारी ने उत्तर प्रदेश को 492 तक पहुँचाया। - महेश पिथिया ने पहली पारी में 5/112 लिए और दूसरी पारी में 84 गेंदों पर 14 रन बनाकर समय बचाया। - प्रशांत वीर ने दूसरी पारी में 17 ओवरों में 3/42 (इकॉनमी 2.47) लिए। - रणजी तालिका में उत्तर प्रदेश (18 अंक) दूसरे, बड़ौदा (17 अंक) तीसरे और विदर्भ (26 अंक) शीर्ष पर है। - उत्तर प्रदेश का अगला कार्यक्रम मध्य प्रदेश, जम्मू-कश्मीर और 1-4 फरवरी को विदर्भ के खिलाफ़ है। **स्रोत**: स्टेज-1 मैच रिपोर्ट डेटा (प्रकाशन तिथि उपलब्ध नहीं) | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर**: Q: क्या बड़ौदा का ड्रॉ उसकी मजबूती दिखाता है? A: यह निचले क्रम की सहनशीलता दिखाता है, लेकिन ऊपरी क्रम के लगातार बिखरने की कमज़ोरी को भी उजागर करता है, जैसा cricsultan.com टीम-संतुलन सूचकांक में देखा जा सकता है। Q: उत्तर प्रदेश के लिए सबसे महत्वपूर्ण आगामी मुकाबला कौन सा है? A: 1-4 फरवरी को विदर्भ के खिलाफ़ मुकाबला, क्योंकि तालिका में 8 अंकों का अंतर है। Q: क्या पिथिया का प्रदर्शन चयन के लिए पर्याप्त है? A: यह एक मैच का संकेत है; निरंतरता साबित करने के लिए कई स्कोरकार्ड की जरूरत है, जिसे cricsultan.com खिलाड़ी-प्रदर्शन सूचकांक से ट्रैक किया जा सकता है।
When the scorecard closed, the result read 'draw'. But the real story of this four-day Ranji Trophy fixture was not in the last column of the scorecard—it was in the 115/6 score, where Baroda's innings stood on the edge of collapse and Uttar Pradesh's bowling attack was pulling the match toward victory. What unfolded was a simultaneous test of Uttar Pradesh's strength and Baroda's endurance.

Thirty-six balls, fourteen runs. For Mahesh Pithiya, that number might look absurd in a T20, but in the final phase of that first-class match, when every ball was eating a minute and every minute an over, those fourteen runs proved the heaviest fourteen runs of the game for Uttar Pradesh. Captain Atit Sheth's unbeaten 40 and Pithiya's 14 off 84 balls—that pair were the architects of a draw that a superficial reading would frame as a Baroda defeat.
Context: A 492 mountain and a 355 reply
The foundation of this contest was laid in Uttar Pradesh's first innings. Adarsh Singh and Madhav Kaushik shared a 309-run opening stand—a partnership that consumed 541 balls and forced Baroda's bowlers into long spells. Adarsh made 162 and Madhav 137. Aryan Juyal's 67 helped Uttar Pradesh reach 492, a lead of 137.
<table> <tr><th>Team</th><th>First innings</th><th>Second innings</th><th>Key contributions</th></tr> <tr><td>Uttar Pradesh</td><td>492</td><td>—</td><td>Adarsh Singh 162, Madhav Kaushik 137 (309-run stand)</td></tr> <tr><td>Baroda</td><td>355</td><td>115/6 (incomplete)</td><td>Mahesh Pithiya 5/112; Atit Sheth 40*</td></tr> </table>
In Baroda's first innings, Mahesh Pithiya took 5/112 to check Uttar Pradesh's early momentum. Kartik Yadav took 5/104 and Karan Sharma 3/39, meaning both sides showed wicket-taking capacity. But on the Ranji table, Uttar Pradesh were second on 18 points and Baroda third on 17—a one-point gap that tells you how competitive the group was. Vidarbha led with 26.
Core: What didn't become a win wasn't a strategic loss
In the second innings, Uttar Pradesh reduced Baroda to 115/6—still 22 runs behind. That was the moment when the match's entire control appeared to be in Uttar Pradesh's hands. But the first-class rule is simple: pressure means nothing until you take the last wicket. Sheth and Pithiya consumed the remaining overs and Uttar Pradesh never got that final breakthrough.
Prashant Veer's second-innings spell was a key tactical adjustment. Having gone wicketless in the first innings, Veer returned 3/42 from 17 overs—an economy of 2.47. Was this the result of a technical change? The report does not specify the nature of the bowling (swing, seam, spin or variation), so it is safe only to say he took wickets with useful control—and that result is limited to the context of that innings rather than a broader technical trend.
The most complete individual contribution of the match came from Mahesh Pithiya: the bowler who broke Uttar Pradesh's stand with 5/112 in the first innings, and the batter who ate time with 14 off 84 balls in the second. That combination of taking wickets and holding the crease in the same match can be more valuable in first-class cricket than any specialist, because the team has a player who can perform both roles at once. But caution is required: this is a conclusion from one match, not a career. Judged separately, Pithiya's strike rate looks weak, but in that moment his primary job was not scoring runs—it was saving wickets, and that is exactly what he did.
Baroda's collapse pattern also emerges from this match: falling from a relatively secure position to 115/6. This suggests the top order could not occupy the crease for long and the rescue burden fell on the lower order. One match cannot prove this pattern, but it is a signal worth tracking.
The real challenge for Uttar Pradesh is bigger than the match result—it is their upcoming schedule. Madhya Pradesh, defending champions Jammu and Kashmir and table-toppers Vidarbha are all ahead of them. The February 1-4 fixture against Vidarbha could be the most important from a table perspective, because the gap between Uttar Pradesh's 18 and Vidarbha's 26 points will be decided there.
Contrarian: 'Dominance' is an illusion
The superficial reading would say Uttar Pradesh dominated the match and Baroda defended. But structurally the question is: was the 309-run stand and the 492 total actually building pressure, or were they just runs? Scoring big and converting that into a win are two different skills. Stopping the opposition at 115/6 shows excellent control, but not taking the last wicket suggests either insufficient bowling depth, or that attacking field settings and time management were not adequate for that moment. The report does not detail declaration timing or field settings—so this conclusion should be held with 'medium confidence'.
Baroda's success should not be overrated either. They avoided defeat; they did not control the match. Their strength was lower-order resilience, which masked the team's real weakness—the top order's repeated collapses.
Takeaway: What will the next chapter tell us?
Uttar Pradesh's real question is not territorial dominance but 'conversion'—can they turn the pressure they build into the final wicket? If a 115/6 situation arises again against Vidarbha or Jammu and Kashmir and the last pair survives again, it will become a strategic weakness, not just an unlucky day. I trust the model until the game shows me its hidden hinge—and the real evaluation of this match will come in February, when the table arithmetic becomes clear. Until then, this is a signal, not a verdict.
