Ranji Trophy Round 2, Day 3: Shahbaz's Seven, Vidarbha's Escape From 26/6 — and the Three Matches That Ended a Day Early

At Sher-e-Kashmir Stadium in Srinagar, Vidarbha needed 79. After 22.5 overs they were 81/7. The scorecard says a seven-wicket win. The scorecard does not say that six wickets had fallen for 26 runs on the way there, and that the two batters who finished unbeaten — Harsh Dubey and Nachiket Bhute — together built the passage that saved a match the top order had all but lost.

That is the round's most important result, and it is the result that will get the least space.

Four grounds, four different crickets

This Ranji Trophy round was played at four venues — Srinagar, Kanpur's Green Park, Delhi's Palam and Pune. Three of the four matches finished on Day 3, in a format scheduled for four days. That is not coincidence.

I calculated runs per wicket from the scorelines, because no pitch report is recorded anywhere. Srinagar came out at 20.8, Kanpur at 18.3, Palam at 15.0 — and in Pune, Maharashtra declared at 527/5 in 150 overs, a scoring rate of 3.51 per over. In one round, a pitch producing 15 runs per wicket and a pitch producing 500-plus coexisted.

That is this round's greatest strength and its greatest danger. Strength, because bowlers got help. Danger, because the numbers that will circulate in newspapers next week are not comparable with each other.

Kanpur: where even 210 was not reached

In the Uttar Pradesh-Goa match, neither side touched 210. UP were bowled out for 197 in the first innings, Goa for 167. Chasing 236 in the fourth innings, Goa collapsed for 167 — a 68-run defeat.

The highest score in that match was Aryan Juyal's 74. He is a wicketkeeper-batter, and he top-scored in an innings where the team was bowled out for 197. Supply of wicketkeeper-batters in Indian cricket has always been thin. Measured against that shortage, Juyal's 74 is the round's least-discussed performance.

Then there is Kartik Yadav — 5/37 in the second innings, and with Vaibhav Chaudhary's 3/33, eight of the ten fourth-innings wickets. That dominance by two bowlers in one innings won UP the match, but it is also their weakness. Leaving ten wickets to two bowlers does not survive a full season.

Palam: Shahbaz's match, with the batting saved from embarrassment

Bengal beat Services, but their two innings were 184 and 146. Both times all out. Winning such a match was possible only if the bowlers did something extraordinary, and Shahbaz Ahmed did.

7/79 in the match and Player of the Match. In the final innings, Pramanik's 4/48 and Shahbaz's 3/44 — seven of the ten fourth-innings wickets to spinners. Services batted 68.5 overs in the last innings at 2.15 runs per over and still lost ten wickets. It was an attritional kill by spin on a slow pitch.

For me the round's most selectable performance is Shahbaz's, not any century. A left-arm spinner who can bat in the top six — that profile is the rarest in Indian cricket. And it came on a pitch where only 15 runs per wicket were scored.

Pune: the easiest pitch, the loudest noise

Maharashtra declared at 527/5. Ruturaj Gaikwad was unbeaten on 101, Ankit Bawne on 169, and Siddhesh Patil made 148. Three century partnerships, 150 overs, a rate of 3.51.

Gaikwad's hundred is real, no question. But it came on the most batter-friendly of the round's four pitches, at home, and the team's rate was 3.51 — the normal level of domestic red-ball cricket, not a statement of tempo.

One thing needs saying clearly here, because it is the biggest mistake available. This is first-class cricket. Red ball. Four days. Gaikwad's identity is built on the IPL and T20, but this 101* in Pune says nothing about his T20 strike rate, and it does not by itself earn him a Test place. Whether his technique against pace has improved is not proven by this innings.

Bawne's 169* is proof of domestic mastery. Not proof of selection. He is about 32, the pitch was flat, and the innings was declared closed — he stands at the peak of his own career, not the national team's.

And that is precisely Maharashtra's real problem. 527/5, a lead of 358, and Jharkhand reached 130/1 in 47 overs in the second innings. One day left, nine wickets in hand. By my calculation Maharashtra enforced the follow-on — the four-day threshold is a 200-run lead and they had 358. But taking nine wickets in a day on a flat pitch is not easy. A draw is the most likely outcome here.

The side the scorecard does not show

Now the thing that matters most in this entire round and that nobody will notice.

Three of four matches finished on Day 3. In a four-day format that is a day saved — but whose loss? The player this tournament exists to develop got fewer overs. Fewer balls bowled, fewer balls faced. A batter learning to withstand 200 overs of pressure did not get that chance this round.

This is not only about this round. For several seasons domestic red-ball cricket has shown a tendency to prepare result-oriented pitches, and this round is a clear example. 20.8 in Srinagar, 18.3 in Kanpur, 15.0 at Palam — these figures say bowlers got help. But the other side is that technically raw batters never got the chance to struggle.

Vidarbha's win is the best illustration of this dilemma. Recovering from 26/6 to 81/7 is proof of mental strength — it was no comfortable victory. Bhute took 5/48 and made 13. Dubey finished 22*. By my reading, of the 55 runs added between the sixth and seventh wickets, at least 35 belonged to these two. Which means the tail won a match the top order had nearly lost.

But that same top order will not recover from 26/6 against stronger bowling next time. The result has been hidden; the weakness has not gone away.

Jammu & Kashmir: a defeat that looks like a win

Do not underestimate J&K on this loss. They had Vidarbha at 26/6 chasing 79. Losing by three wickets at home, on a helpful pitch — that margin does not reflect the performance.

Sunil Kumar took eight wickets across the match, including 4/30 in the first innings. He came close to winning a match his batters lost.

And Abdul Samad's 39 should not be read the way it will be read. J&K were bowled out for 123, meaning Samad made 31.7 per cent of his team's total, on a seaming pitch. That is not a T20 hitter's cameo; it is a genuine red-ball contribution. But one innings does not settle the question of whether he is ready for the longer format.

Goa's 72, hidden inside 167

Suyash Prabhudessai made 72 in a total of 167, in the fourth innings, while losing. On paper it is just 72. In reality it is 43 per cent of an innings in which the other ten batters together managed 95.

An innings like that is worth more than its score, because it was played in solitude.

The mistake this round will produce

I think the story that forms from this round will be the wrong story.

The papers will say: Gaikwad is back in form. The truth is that his hundred came on the round's easiest pitch, at home, at a team rate of 3.51. It is evidence of red-ball concentration, not of a technical fix.

Conversely, Shahbaz Ahmed's 7/79 — the round's strongest selection case — will get less space, because his name is not in IPL headlines.

One more thing must be recorded. The numbers from this round are not comparable with each other. A match at 15 runs per wicket and an innings at 3.51 an over cannot be put in the same table without doing methodological damage. Every figure needs its pitch context written beside it.

And one caution. Be careful with the name "Kartik Yadav". Uttar Pradesh also has a fast bowler named Kartik Tyagi. The 5/37 in this round belongs to Kartik Yadav, and merging the two in any database would be a serious error.

What to watch next

First, watch how many matches finish on Day 3 in the next round. If that number is again three or four, it stops being a round-level coincidence and becomes a policy-level signal.

Second, watch Shahbaz Ahmed's next two innings. If he keeps contributing in both departments, Bengal's entire strategy is carrying the risk of resting on one player — and that risk will show on the day he does not play.

Third, watch Vidarbha's top order. 305 and 26/6 — two faces in one match. Next time, against a stronger attack, that 26/6 becomes a defeat.

And fourth, Aryan Juyal. A wicketkeeper-batter's 74 in a team bowled out for 197. Watch that number for two more rounds before saying anything.

In Srinagar, when those 55 runs were being added after Vidarbha's seventh wicket, there were not many people in the stadium. The numbers that appear in the big papers next week will come from Pune. But the most honest cricket in this round was played in Srinagar — where winning meant scoring 79 and losing six wickets to get there.