होमWorld CricketChasing 115, Collapsing to 19/4: In Raipur the Scoreboard Was Repaired, the Top Order Was Not

Chasing 115, Collapsing to 19/4: In Raipur the Scoreboard Was Repaired, the Top Order Was Not

**मुख्य उत्तर**: भारतीय महिला टीम ने रायपुर में जिम्बाब्वे के खिलाफ पहले T20I में 115 रन का लक्ष्य चार विकेट शेष रहते हासिल किया, लेकिन पावरप्ले में 3.1 ओवर में 19/4 पर सिमटकर टॉप ऑर्डर की गंभीर कमजोरी उजागर की। **मुख्य तथ्य**: - भारत ने 3.1 ओवर में 19 रन पर चार विकेट गंवाए, पांचवें विकेट के लिए 82 रन की साझेदारी हुई। - लक्ष्य 115 था, यानी जरूरी दर 5.75 रन प्रति ओवर, जिससे पारी नियंत्रण-आधारित बन गई। - चार विकेट की जीत का अर्थ है कि भारत ने अनुमानतः 115/6 पर पारी समाप्त की। - यह तीन मैचों की T20I सीरीज का पहला मुकाबला था, जो रायपुर में खेला गया। - डेब्यूटेंट निकी प्रसाद की सीनियर खिलाड़ी द्वारा प्रशंसा दर्ज की गई। **स्रोत**: ICC आधिकारिक रिपोर्ट, प्रकाशन तिथि उपलब्ध नहीं | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर**: प्रश्न: भारत ने पावरप्ले में कितने विकेट खोए? उत्तर: भारत ने 3.1 ओवर में 19 रन पर चार विकेट खोए। प्रश्न: मैच का लक्ष्य कितना था? उत्तर: जिम्बाब्वे के खिलाफ लक्ष्य 115 रन था, जो 5.75 रन प्रति ओवर की दर से था। प्रश्न: किस साझेदारी ने भारत की पारी संभाली? उत्तर: पांचवें विकेट के लिए 82 रन की साझेदारी ने भारत की पारी संभाली।

By the end of the third over at the Shaheed Veer Narayan Singh International Cricket Stadium in Raipur, the Indian women's scoreboard read 19/4. In the powerplay — the six overs where the rules stand with the batter — four wickets had already gone. The result is a four-wicket win, and the result is correct. But the first 19 balls of the innings that produced that win raised a question the victory column will not answer. I broke the structure of this chase into three parts — powerplay, middle overs, and the closing overs — and all three told different stories. The scoreboard said one thing; it was not the whole story. Start with the part that speaks loudest. Four wickets in the powerplay is a technical event, not bad luck. When the ball is new and fielding restrictions favour the batting side, wickets falling does not mean the ball was moving dangerously. It means the top order misread line and length, or misjudged shot selection, or both. Nineteen runs for four wickets in 3.1 overs is a diagnosis in itself, and it points at something any team management would prefer to defer until after the result. Now the part that saved the match. An 82-run stand for the fifth wicket. The bigger that number looks, the more it reveals about how thin the rest of the innings was. After 19/4 India added roughly 96 runs, and 82 of them came from one pair. The remaining six wickets and the remaining batters shared about 14. This is the 'one-partnership team' structure, and it holds only until the opposing bowling attack can break that one pair. The target was 115, a required rate of 5.75 an over. That is the kind of target that converts an innings from a test of firepower into a test of control. The 82-run stand was built well below eight an over, and that is the most useful lesson of this match — when chasing a low total the requirement is preserving wickets, not manufacturing boundaries. On that count the Indian batting did precisely what was needed. But it is also worth remembering that this strategy works only when the target is small. Chasing 160, 19/4 ends the match. Now the part that gets underrated. That Zimbabwe pushed India this deep is a bigger story than the win. The ICC report itself concedes the hosts had to dig deep. The question is how to read it — as an achievement of Zimbabwe's bowling, or as a failure of India's top order? The difference matters, and the next two matches will settle it. If Zimbabwe's new-ball bowling is genuinely this good, this series will not be easy. If this was one bad evening for India, Raipur was a warning, not a crisis. One thing needs stating plainly. I do not have the full scorecard of this match. There is no detail of Zimbabwe's innings, no bowling figures for either side, no toss and no pitch information. That makes it hard to judge whether 115 was par or under-par for the surface. If the pitch was slow, putting 19/4 entirely on the batters would be wrong. If the pitch was good for batting, 19/4 is a serious question. Without a pitch report I cannot reach that conclusion, and I should not. The reaction around debutant Niki Prasad matters because a senior player inside the team has publicly credited a newcomer. But the real question here is not who praised whom. It is how much work the debutant was given in that match, in what circumstances, and whether that work affected the result. Praise is a sentiment; opportunity is a fact. I want the fact. My estimate is that India finished on 115/6. The arithmetic is simple — 19/4 plus an 82-run fifth-wicket stand is 101/5, and a four-wicket win chasing 115 requires six wickets down. That estimate carries medium-high confidence, because I do not have the scorecard. It is also possible that the batter dismissed at 101 was the very player whose praise is quoted. That is an inference, not a fact. Here is the angle I usually avoid, and this time I cannot hold it back. The post-win speech always suppresses criticism of the process. A four-wicket win, praise for a young player, and a 1-0 series lead together build a narrative into which 19/4 does not fit. But 19/4 exists, and it will still exist in the next match. If India's top order is allowed to bury that error simply because the result went their way, this series will leave one lesson unlearned even if it is won. I do not have a delivery-by-delivery ledger of this match's 120 balls, so I will not claim to have watched every one. What I have is the architecture of the scoreboard, and it says one thing — India won this match not on the strength of its top order but on the rescue that followed it. The distinction looks small; by the end of the series it will decide whether this win was a beginning or a warning. The number worth watching in the next match is not how many runs India score. It is how many wickets fall in the first six overs. If that figure stays at two or fewer, Raipur was an accident. If it hovers at three or four, we will have to accept that the team which chased 115 did not solve its biggest problem — it only covered it for a while.

Chasing 115, Collapsing to 19/4: In Raipur the Scoreboard Was Repaired, the Top Order Was Not

Chasing 115, Collapsing to 19/4: In Raipur the Scoreboard Was Repaired, the Top Order Was Not

Chasing 115, Collapsing to 19/4: In Raipur the Scoreboard Was Repaired, the Top Order Was Not

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