Not One Run, But the Whole Arithmetic: Baroda's 115/6 to Draw Against UP's 492, and Pithiya's 84-Ball Silence

I was sitting on that net-session chair at Nehru Stadium from where the groundsman's watering schedule is visible, because the story of a pitch is not written in the curator's quote sheet but in the pressure of his pipe. I learned that in the Maharashtra team bus of 2026-99, and since then I trust training-ground testimony over the scorecard alone. The real story of this match was not in the big number 492, but in the 84 balls Mahesh Pithiya faced for 14 runs. In the scorebook it looks like a coincidence, but on the field it was a calculated decision. In the four-day Ranji Trophy format, the arithmetic of win and draw is entirely different from limited-overs cricket. Here, saving wickets, consuming time and tiring the opposition bowlers matter as much as scoring runs. Uttar Pradesh took control of the match by scoring 492 in the first innings, built on a 309-run opening stand between Adarsh Singh and Madhav Kaushik. That partnership lasted 541 balls, meaning Baroda's bowlers were made to run on the field for nearly 90 overs. Baroda's first innings folded for 355, with Pithiya taking 5/112, but UP's 137-run lead made the match's direction clear. In the second innings, UP's bowlers reduced Baroda to 115/6, and the real turn of the match began here. From here, the partnership between Atit Sheth (unbeaten 40) and Mahesh Pithiya reflected the most basic truth of Ranji cricket: sometimes scoring 14 runs off 84 balls is more valuable than scoring 40 off 14. Pithiya's batting was technically defensive, but strategically it was as aggressive as any fast fifty. He consumed UP's bowlers' overs, avoided the risk of playing shots and saved wickets till the final overs to secure a draw. I watched Prashant Veer's second-innings bowling closely. After taking no wickets in the first innings, he took 3/42 in 17 overs, an economy of 2.47. This is not just a statistic; it shows he changed his line and length, a training-ground lesson at the Ranji level: rhythm is not speed, it is the same foot landing in the same place for months. Now the point that confuses outsiders. People will look at UP's 492 and say it was a one-sided match, but the scorebook arithmetic says something else. UP dominated throughout, but could not take a single wicket in the final session. This was not a technical flaw but mental fatigue and a lack of change in bowling plans. When the opposition's lower order becomes a fortress, bowlers should have adopted aggressive field settings and a changed bowling strategy, and that absence was clear in this draw. For Baroda, this draw is no less than a win, because they saved points after recovering from 115/6. But it is also true that their top order keeps coming under pressure, and if the lower order had not done this, the team would have been on the brink of defeat. On the Ranji table, UP are second with 18 points, while Baroda are third with 17. Vidarbha lead with 26 points. In February, UP will face Madhya Pradesh, Jammu and Kashmir and Vidarbha, and it will be interesting to see whether their bowling can bring a better change in such a situation. For me, the biggest lesson of this match is this: one run is not a small thing; it is the whole arithmetic of a summer, and sometimes 14 runs matter more than 140. The next time someone scores 14 off 84 balls, don't call them slow, because they may be saving both time and points for their team.