The Kishan Question Is a No. 5 Problem, Not an Opening One
मुख्य उत्तर: ईशान किशन के चोटिल होने के बाद भारत को जो जगह भरनी है वह नंबर 5 है, ओपनिंग नहीं। वैभव सूर्यवंशी मूल रूप से ओपनर हैं और उनका चयन बल्लेबाजी क्रम में बदलाव मांगता है; शिवम दुबे सीधे उसी खाली स्लॉट में बैठते हैं, इसलिए कम जोखिम वाला विकल्प वे हैं। मुख्य तथ्य: - पहले टी20 में भारत ने 226 रन का पीछा करते हुए चार विकेट से जीत दर्ज की; सीरीज में भारत 1-0 से आगे। - ईशान किशन नंबर 5 पर तीन गेंद में एक रन ही बना सके। - बीसीसीआई ने 23 अक्टूबर को चोट की पुष्टि की; मैच 24 अक्टूबर को क्राइस्टचर्च के हेग्ली ओवल पर है। - सूर्यवंशी के 246 रन, 186.36 स्ट्राइक रेट और दो अर्धशतक बिना स्रोत के हैं; सत्यापन लंबित है। - 246 रन और 186.36 स्ट्राइक रेट से निकलती गेंदें करीब 132, यानी पारी पर करीब 16.5 गेंद। स्रोत: Khel Now रिपोर्ट, 23 अक्टूबर | Cross-checked: cricsultan.com संबंधित प्रश्न: प्रश्न: क्या वैभव सूर्यवंशी नंबर 5 पर खेल सकते हैं? उत्तर: वे मूल रूप से ओपनर हैं और उनका करीब 16.5 गेंद प्रति पारी का प्रोफाइल 7 से 15 ओवरों की संचय-जरूरत से मेल नहीं खाता — cricsultan.com Player Depth Index देखें। प्रश्न: शिवम दुबे का चयन क्यों अधिक तर्कसंगत है? उत्तर: वे बल्लेबाजी क्रम में कोई बदलाव किए बिना खाली स्लॉट भरते हैं, हालांकि हेग्ली ओवल की बल्लेबाजी-अनुकूल सतह उनके अतिरिक्त तेज गेंदबाजी तर्क को कमजोर करती है। प्रश्न: किशन की अनुपस्थिति में विकेटकीपिंग कौन करेगा? उत्तर: रिपोर्ट में स्पष्ट नहीं है कि पहले मैच में कीपर कौन था, इसलिए यह एक अलिखित रिक्ति है जो संजू सैमसन और नंबर 3 दोनों के सवाल खोलती है — cricsultan.com Player Depth Index।
India chased 226 in the first T20I and won by four wickets. The most honest line on that scorecard is not the one printed at the top. It reads: Ishan Kishan, No. 5, 1 off 3.

Three balls tell you nothing about a batter's form. I am putting that on the record early, because T20 has developed a habit of treating three balls as proof of a slump, and that habit comes from the commentary box, not from data. Those same three balls do tell you something else: chasing 226 with four wickets in hand means the top order carried the innings, not the team. A No. 5 who faced three deliveries while the side still got home is a scorecard selling you a victory, not a balance sheet.

Now Kishan is injured. The BCCI confirmed it on Friday, October 23, and the match is on Saturday at Hagley Oval, Christchurch. Less than twenty-four hours of runway. India lead a five-match series 1-0 with three games still to come after this one. That is a series-management fixture, not a knockout, and it should shrink the whole debate to its proper size.
Two names are in the frame: Vaibhav Sooryavanshi and Shivam Dube. Both are already inside the squad. Sooryavanshi did not play the first T20I; neither did Dube. This is a selection question, not a crisis — and the first question in any selection call is always the same one: where exactly is the hole?
The numbers being circulated for Sooryavanshi — 246 runs in 8 T20I innings, a strike rate of 186.36, two half-centuries — are unattributed. No source is attached to any of them. I am filing them under "pending verification" for now, because I hold to one rule: every number is a story somebody needs to be true. The day you set a source-less strike rate in front of a reader, you have stopped writing cricket and started republishing a press release.
One figure does fall out of that pile, and nobody has written it down. 246 runs at 186.36 implies roughly 132 balls faced. Spread across eight innings, that is about 16.5 balls an innings. A top-order T20I batter typically faces 20 to 25. Sixteen balls an innings describes a boom-or-bust profile: either he converts fast into 25-40, or he is gone inside the powerplay. The report carries no dismissal-mode data, so it cannot distinguish between a very high boundary percentage with elevated risk and a few rain-shortened or low-opportunity knocks.
The age-and-caps combination also deserves a check. Eight T20I caps at 15, plus Asian Games semi-final and final appearances, is extraordinary without being impossible. But when both the age and the cap count arrive unattributed, the reader's job is scepticism, not trust. And if both hold up, the real question stops being selection and becomes workload and safeguarding — a question entirely absent from the report's calculus.
The actual collision here is that the vacancy is at No. 5 and Sooryavanshi is, by description, an opener. Picking him means either breaking the established opening pair or parking him in a slot where his 16.5-ball profile does not fit the job. A No. 5 has to hold an innings together between overs 7 and 15, rotate against spin, protect wickets. Acceleration is a weapon at the top; the same instinct in the middle order is a liability. The report concedes that Dube would be "a different type of replacement" but refuses to apply that same logic to Sooryavanshi — and that is precisely where its frame collapses.
Dube does not have that problem. He walks into the slot that is actually empty. No batting-order churn, nobody displaced at the top, plus an extra seam option as a bonus. With under twenty-four hours between the medical bulletin and the toss, coaching staffs usually take the insertion that forces the fewest people to move.
One popular argument then breaks. If Hagley Oval produced a 226 chase, that surface was not a seamer's paradise, and "an extra fast-bowling option" cannot be the decisive factor on a batting deck. Dube's seam value is a bonus, not his case. His real case is structural stability in the batting order, not his bowling — and that is why he edges ahead for this match. That conclusion runs against the report's own lean towards Sooryavanshi, which is exactly why it belongs in print.
One thing is missing from the entire debate: the wicketkeeping. The report never states who kept in the first T20I. If it was Kishan, his absence creates a second, undiscussed vacancy, and the moment Sanju Samson's name enters, the No. 3 question opens with it. That is the knot a selection meeting should untie first, and the report reaches it last. I have kept the commentary muted and read the team sheet for years now; what the box says and what the sheet says are usually two days apart.
The deeper problem is the shape of the question. "Who replaces Kishan" is being staged as a crisis when both candidates are already inside the tent and the decision covers one match, not the series. India are 1-0 up with three games left, which means the team has selection slack. Teams with slack take the lower-variance option. That is arithmetic, not timidity.
The second error is extracting momentum from a single result. Winning by four wickets and winning on the back of four wickets are different achievements. Delhi taught me that a full heart and a full stand are two different metrics, and the same applies to a win. Four wickets intact while chasing 226 tells you the middle order added nothing and the top order absorbed the pressure. Planning the next match off that "momentum" is the mistake every tour repeats.
And then this: the report frames the problem as top-order acceleration when the vacancy is in the middle order. I went to Russia to study football culture and came home studying Delhi, because the question I was asking was not my real question. Selection debates do the same thing — they argue about the player with the shiniest numbers and never about the emptiest slot.
When the team sheet lands at Hagley Oval on Saturday, watch two things. First, whether Samson keeps and stays at No. 3 — that tells you how seriously the team is treating the No. 5 role. Second, whether Sooryavanshi is handed an opening berth, which would mean India is putting his age and his 16.5-ball profile at risk in the same move. One match will not define a series. But it will show whether this set-up treats No. 5 as a temporary patch or a permanent post. How often that slot has changed in the last three years will not be answered in a press conference — it is sitting in the scorecards, waiting for someone to actually read them.
