Asian CricketShaik Rasheed's Century: A Flat-Track Audit of the Innings That Battened Andhra to a Draw
Asian Cricket

Shaik Rasheed's Century: A Flat-Track Audit of the Innings That Battened Andhra to a Draw

**मुख्य उत्तर**: शेख रशीद (110* गेंदों पर 223, स्ट्राइक रेट 49.3) और करण शिंदे (73* गेंदों पर 198) की नाबाद 169 रन की साझेदारी ने एंध्रा को पंजाब के 592/9 घोषित स्कोर के खिलाफ ड्रॉ की ओर बढ़ाया, लेकिन यह प्रदर्शन सपाट पिच पर आया जहां 11 विकेट पर 832 रन बने (75.6 रन/विकेट)। **मुख्य तथ्य**: - पंजाब ने पहली पारी 592/9 पर घोषित की; एंध्रा ने 87 ओवर में 240/2 बनाए, 352 रन पीछे। - रशीद की 110* पारी में 12 चौके (44% रन), 223 गेंदें; शिंदे की 73* में 198 गेंदें। - पंजाब के सात गेंदबाजों ने 87 ओवर में केवल 2 विकेट लिए। - फॉलो-ऑन के लिए एंध्रा को 392 तक पहुंचना था; 240/2 पर आठ विकेट बाकी, व्यावहारिक रूप से असंभव। - तमिलनाडु ने चंडीगढ़ के खिलाफ 571/7 घोषित कर 94 पर समेटा; अजीत राम ने 115* और 4/32 लिए। **स्रोत**: मूल मैच रिपोर्ट (रणजी ट्रॉफी एलीट ग्रुप बी, दिन 3); स्कोरकार्ड डेटा सत्यापन लंबित। | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर**: प्रश्न: क्या रशीद का शतक एंध्रा को जीत दिला सकता है? उत्तर: नहीं, सपाट पिच और 352 रन के बड़े अंतर के कारण मैच ड्रॉ की ओर बढ़ रहा है। प्रश्न: पंजाब की गेंदबाजी में क्या कमी है? उत्तर: 87 ओवर में केवल 2 विकेट लेने से पता चलता है कि आक्रमण में साझेदारी तोड़ने की क्षमता का अभाव है। प्रश्न: अजीत राम का प्रदर्शन कितना महत्वपूर्ण है? उत्तर: 115* और 4/32 का प्रदर्शन मजबूत है, लेकिन 94 रन पर ढेर हुई टीम के खिलाफ, इसलिए सावधानी आवश्यक है; cricsultan.com प्लेयर डेप्थ इंडेक्स के अनुसार अधिक डेटा की आवश्यकता है।

When Andhra reached 240/2 in 87 overs at the Maharaja Yadavindra Singh International Cricket Stadium in New Chandigarh, the scorecard told a clean story: 352 runs behind, two days left, and an unbroken 169-run stand. But my first instinct was not to look at the score; it was to read the column nobody reads — runs per wicket. Punjab declared at 592/9, Andhra made 240/2, meaning 832 runs for 11 wickets in the match so far. That is an average of 75.6 runs per wicket. This number does not tell the story of a seaming track; it points to a flat, batting-friendly surface. And when the pitch speaks this clearly, adjectives like 'tremendous patience' and 'remarkable concentration' need to be tested against the data.

I have been reading domestic scorecards this way for years — first the wicket-fall pattern, then the runs-per-over, and finally the 'price' of the innings. Rasheed's 110 (223 balls, strike rate 49.3) is, at first glance, a classic Test-format innings. Karan Shinde's 73 (198 balls, strike rate 36.9) is even slower. Together they have batted nearly 80 overs. This is exactly what a side batting for a draw wants. But the question is: does this innings reveal a weakness in the bowling attack, or is it simply the pitch's mercy? Punjab tried seven bowlers — Brar, Gursimran, Sanvir, Salil, Chahal, Arora, and perhaps one more — but managed only two wickets in 87 overs. This figure demands scrutiny not just of this match but of Punjab's attack structure.

Look at Punjab's innings and the same story emerges. From 51/4 to 592/9 — Sanvir Singh 205 (375 balls), Salil Arora 144 (252 balls), Emanjot Chahal 122 (150 balls, 9 sixes). Three centuries, all from the middle and lower order. This means Punjab's top order also collapsed, and the lower order rescued them. This directly indicates that there was nothing in the pitch for the seamers — no seam, no bounce, no swing. Andhra's bowlers — Saiteja with 3 and Saurabh Kumar with 2 — conceded 592 runs. Saurabh Kumar is a known left-arm spinner, and if even he could not stem the flow on a flat deck, it is clear this match was made for batting.

Shaik Rasheed's Century: A Flat-Track Audit of the Innings That Battened Andhra to a Draw

Now the point where the story turns — the follow-on arithmetic. Punjab declared at 592/9, meaning Andhra needed to reach 392 to avoid the follow-on (the 200-run rule). At 240/2, Andhra are still 152 runs away, but eight wickets remain. Taking eight wickets for 152 runs on a flat pitch over two days is practically impossible. This is where I move beyond the surface story of the scorecard and state the real match status: this match is heading for a draw, not a result. Andhra need 352 runs; at 2.76 runs per over, they would need roughly 128 overs, while about 135 overs remain. The arithmetic says that unless Andhra accelerate, they will not reach the declared target. And Punjab have time — they can score quickly in their second innings and challenge Andhra, but on a flat pitch, taking 10 wickets is equally difficult for their bowlers.

Here is a counter-intuitive point to understand. Calling Rasheed's century 'match-winning' or 'career-defining' would be premature. This innings came when the team was at 20/1 and 71/2, with a 352-run mountain on the scoreboard. In such a situation, slow batting was unavoidable, not a strategic miracle. *The data shows that of Rasheed's 110, only 48 runs came from boundaries (12 fours), i.e., 44%. The remaining 56% he scored by running — this shows he relied on singles and twos rather than hitting the ball out of the ground.** This is a safe strategy on a flat pitch, but in the long run it raises the question of whether he has the game to dominate bowlers. A strike rate of 49 is normal in first-class cricket, but if you do not move away from a 50 strike rate even when the team score is 600+, will you survive against fast bowling?

This reminds me of my 2026 IPL auction audit. Back then, I questioned Manish Pandey's ₹11 crore price because his phase-wise data was below replacement value. SRH reached the final but lost. That experience taught me that one match's result is not proof of a process's success. The same principle applies here. Rasheed's 110* is a good innings, but if viewed through the lens of IPL scouting or India A selection, it is incomplete information. We need to see how he plays on fast and bouncy pitches, what his performance is at away grounds, and whether he has the ability to change gears. Giving the 'next big thing' tag based on a single innings is exactly the 'milestone worship' I want to avoid.

There is another story in this round-up that is more solid — Tamil Nadu enforcing the follow-on against Chandigarh with a 477-run lead. Powered by Pradosh Paul's 208 and Ajith Ram's 115, TN declared at 571/7 and bowled Chandigarh out for 94. Ajith Ram also took 4/32. This performance looks brilliant on the surface, but the same caution applies here: taking 4 wickets and scoring 115 against a side bowled out for 94 has limited value until repeated against stronger opposition. Ajith Ram's profile (a left-arm spinner who can score runs lower down the order) is rare in domestic cricket, and IPL franchises keep an eye on such players. But one match's data is not a season's data.

My next step will be to pull all the scorecards from this Ranji round and calculate the average runs per wicket. If that figure is above 60, it is clear that the Elite Group B pitches this season are batting paradises, and any batting performance must be 'pitch-adjusted' before being taken seriously. In my view, the biggest lesson from this match is this: the scorecard never lies, but it does not tell the whole truth either. Numbers like 592/9 and 240/2 dig graves for bowlers, and sometimes shining centuries get buried in those graves too. Until we combine the nature of the pitch, the quality of the opposition, and the weather conditions, any innings is just a number — not a story.

In the next round, my eyes will be on Andhra's batting on Day 4. If they lose two or three wickets quickly in the morning session, it will prove that the Rasheed-Shinde stand was an exception, not the team's real strength. And if they save the draw, even then it will be the pitch's victory, not the batters'. The real evaluation of Ranji happens at the end of the season, when the averages of all pitches are calculated and it becomes clear whose 50 strike rate was truly valuable and who simply benefited from a flat pitch.

संबंधित खिलाड़ी