Shaik Rasheed's Century: The Real Story Behind Andhra's Saving Innings

In the years I've spent watching Ranji Trophy matches, the thing that surprises me most is the gap between the scoreboard and the pitch. At the Maharaja Yadavindra Singh International Cricket Stadium in New Chandigarh, Punjab declared at 592/9 and Andhra reached 240/2 by the end of Day 3. Shaik Rasheed is unbeaten on 110, Karan Shinde on 73. An unbroken 169-run stand. On paper, a fine rearguard. But whenever I see numbers like these, my first question is: what was the pitch like? Because a ratio of 832 runs for 11 wickets (about 76 runs per wicket) is extraordinarily high for any first-class match. This is not a normal seaming or bouncing track.

To understand the texture of this match, you have to look at the pattern across three days. Punjab recovered from 51/4 to 592/9 — Sanvir Singh's 205, Salil Arora's 144 and Emanjot Chahal's 122 (off 150 balls, with nine sixes) are proof that the bowlers had no help. Andhra too lost early wickets at 20/1 and 71/2, but then Rasheed and Shinde exploited their understanding of the pitch. Rasheed's 110 off 223 balls includes 12 fours — meaning he didn't take many risks to score, but accumulated by pushing the ball into gaps. Karan Shinde's 73 off 198 balls was even slower (strike rate around 37), clearly showing a draw-saving mindset.

The real story here is in the bowling, not the batting. Punjab tried seven bowlers but could take only two wickets in 87 overs. In my experience, when a team has seven options and takes so few wickets, it means they lack a 'strike bowler' who can break a long partnership. This isn't just a problem in this match — it's a question mark over Punjab's bowling depth. Of course, on a flat pitch every bowler's menace diminishes, but two wickets in 87 overs? That's a structural concern.

Now look at the angle most people miss. By the end of Day 3, Andhra are 352 behind with two days left. To enforce the follow-on, Punjab would need to bowl Andhra out for under 392 (592 plus 200). That means Andhra would have to lose eight wickets for 152 runs, when the pitch offers no assistance and batters like Rasheed and Shinde are set. In my view, the follow-on arithmetic is now merely academic. Practically, this match is heading for a draw.

But there's something that bothers me. This match tells us about a batter who can hold one end for a long time. When I first sat in the Uppal press box at 20, I saw how batting averages inflate on flat pitches in domestic cricket. Shaik Rasheed's 110* is technically correct — 223 balls, 12 fours, patience according to the match situation. But this innings doesn't tell us how he'll play on fast, bouncy tracks. That's the biggest problem with the Ranji Trophy: we label a century on a pitch producing 76 runs per wicket as 'star birth'.

I'm not saying Rasheed's innings isn't important. Rather, it's the right kind of performance for his development — an innings that saves the team from defeat. But cricket fans and selectors must understand that a century on the New Chandigarh pitch and a century on the bouncy M. Chinnaswamy Stadium pitch in Bengaluru are not the same thing.

For Andhra, the next step is clear: don't lose a wicket in the first session of Day 4. If Rasheed and Shinde survive the first hour, it will be difficult for Punjab to save this match. And if Andhra cross 392, the follow-on threat ends. My eye is on the first session of Day 4 — if Andhra lose even one wicket early, pressure will mount on the lower order. But if these two stay set, the match will drift to a draw, and another question will be added to Punjab's bowling figures.

For Rasheed, this innings adds a good experience to his profile, but its real value will be known when he plays away from home on fast-bowling pitches. Until then, this 110* is a good story — just read it in the context of the pitch it was made on.