From a Run-Fest to a Test of Bounce: Two Contrasting 113s Reveal India's Batting Challenges in Wellington
मुख्य उत्तर: वेलिंगटन में भारत और न्यूजीलैंड के बीच दो अलग-अलग प्रारूपों के मुकाबलों ने भारतीय बल्लेबाज़ी की दो तस्वीरें दिखाईं। 27 अक्टूबर 2026 को अभिषेक शर्मा ने तीसरे टी20I में 38 गेंदों पर 113 रन बनाए, जबकि 7 नवंबर 2026 को दूसरे ODI में भारत 26 ओवर में 113/7 तक पहुंचा और DLS से चार रन से जीता। प्रमुख तथ्य: - 27 अक्टूबर 2026: अभिषेक शर्मा ने 113 रन (38 गेंद), स्ट्राइक रेट 297.37 बनाया। - भारत ने टी20I में न्यूजीलैंड के 198 रन के जवाब में 13.2 ओवर में 199 रन का लक्ष्य हासिल किया। - भारत और वैभव सूर्यवंशी ने टी20I पावरप्ले में 118 रन बनाकर पुरुष टी20 अंतरराष्ट्रीय रिकॉर्ड बनाया। - 7 नवंबर 2026: न्यूजीलैंड 134 रन पर ऑल आउट; गूरनूर बरार ने 4/30 लिए। - भारत 113/7 पर था, ऑल आउट नहीं; बारिश के बाद DLS पद्धति से भारत चार रन से जीता और तीन मैचों की ODI श्रृंखला में 2-0 की बढ़त बनाई। स्रोत एवं प्रकाशन तिथि: - Reuters, 'Abhishek ton flattens New Zealand as India seal T20 series', 27 अक्टूबर 2026। - Times of India, 'From run-fest to a spicy feast: A tale of two 113s in Wellington', 7 नवंबर 2026। - Cricbuzz, भारत बनाम न्यूजीलैंड दूसरा ODI लाइव स्कोरकार्ड, 7 नवंबर 2026। संबंधित प्रश्नोत्तर: प्रश्न: अभिषेक शर्मा ने कितनी गेंदों में शतक बनाया? उत्तर: अभिषेक शर्मा ने 35 गेंदों में शतक पूरा किया और 38 गेंदों पर 113 रन बनाए। प्रश्न: भारत ने न्यूजीलैंड के खिलाफ दूसरा ODI कैसे जीता? उत्तर: बारिश के कारण खेल रुकने पर भारत 113/7 पर था और DLS पार स्कोर से चार रन आगे होने के कारण चार रन से विजेता घोषित हुआ। प्रश्न: दूसरे ODI में भारत की चयन संबंधी मुख्य चर्चा क्या रही? उत्तर: अक्षर पटेल को केएल राहुल से पहले पांचवें नंबर पर भेजने का निर्णय, खासकर छोटी गेंदों के खिलाफ अक्षर की लगातार परेशानी के कारण, चर्चा का विषय बना।
Wellington offered two remarkably different pictures of Indian batting within the space of eleven days. On October 27, 2026, Abhishek Sharma smashed 113 off just 38 balls in the third T20I against New Zealand. India chased 199 in only 13.2 overs. On November 7, in the second ODI at the same city, India reached 113/7 in 26 overs before rain prevented further play. India secured a four-run victory under the Duckworth-Lewis-Stern method.
The identical run tally concealed two entirely different cricketing situations. One was a demonstration of modern T20 aggression, in which the New Zealand bowlers were put under pressure during the opening six overs. The other was a contest in which bounce, seam movement and sustained short-pitched bowling exposed technical limitations in India's batting order.
Treating the two Wellington 113s as comparable batting performances would be the first analytical mistake. The tactical demands of T20 internationals and ODIs are different, even when the venue and some playing conditions overlap. The meaningful connection between these matches lies in India's ability to adapt its batting to changing conditions.
T20I: Abhishek Sharma changed the equation in the powerplay
New Zealand made 198 in 20 overs in the third T20I on October 27, with Daryl Mitchell scoring an unbeaten 89. It was a competitive target, but the hosts could hardly have anticipated the speed with which India's opening pair would dismantle their bowling plans.

Abhishek Sharma and 15-year-old Vaibhav Sooryavanshi attacked from the beginning. They scored 118 runs in the powerplay, setting a new record in men's T20 international cricket. The previous record was 116, scored by Romania against Serbia in 2026.
Abhishek finished with 113 from 38 deliveries, including nine fours and 11 sixes. His strike rate was approximately 297.37. He reached his century in 35 balls and repeatedly forced New Zealand's bowlers to reconsider their lengths. Sooryavanshi contributed 45, and the pair added 133 for the opening wicket. India eventually won by six wickets, reaching the target in 13.2 overs.
According to Reuters' report published on October 27, 2026, Abhishek came close to threatening his own 30-ball century record, which he had set against Afghanistan in Delhi the previous month. His innings demonstrated the direction of India's modern T20 approach: opening batters increasingly treat the powerplay as an opportunity for maximum scoring rather than merely a period in which to establish a foundation.
In my years of studying cricket matches, the importance of the powerplay has become increasingly apparent. However, 118 runs should not become a routine benchmark. This was an extraordinary innings, and its context includes bowling quality, wind conditions, pitch pace and fielding restrictions.
The most important feature of Abhishek's innings was not the individual century but India's 118-run powerplay. When a team forces the opposition to abandon its initial bowling plans inside six overs, the pressure on the required rate during the middle overs largely disappears.
ODI: New Zealand turned bounce into a weapon
Conditions changed dramatically in the second ODI on November 7. The drop-in surface at Hnry Stadium in Wellington was affected by the weather. New Zealand were dismissed for 134 in 41 overs. Daryl Mitchell scored 55 and Mitchell Santner made 31, attempting to give the hosts a competitive total.
For India, Gurnoor Brar took four wickets for 30 runs, while Anshul Kamboj claimed two. India's fast bowlers used short deliveries and aggressive lengths to trouble New Zealand's batters. The hosts were unable to settle against the same bounce that New Zealand would later exploit against India.
India began with a target of 135. Under ordinary circumstances, that would have been a manageable assignment for this batting line-up. New Zealand, however, used sustained short-pitched bowling and deliveries directed towards the body to make the chase difficult. The decisive shift occurred during the opening ten overs rather than at the end of the innings.
Shubman Gill departed early. Virat Kohli scored seven before losing his wicket, while Rohit Sharma battled for a period before playing a rash shot. After those dismissals, India needed a batter capable of rebuilding the innings according to the conditions.
This was where the decision to promote Axar Patel to No. 5 attracted attention. Team management preferred Axar despite having a specialist batter such as KL Rahul available. The stated reasoning was to break the monotony of having right-handed batters in succession. That approach can be useful in certain situations, but technical suitability appeared more important on Wellington's surface.
The Axar Patel decision: a clash between strategy and conditions
Promoting Axar Patel is not inherently a poor decision. His batting role proved useful on the slow, turning surfaces during the Champions Trophy in Dubai. A left-handed batter can disrupt the opposition's bowling lines and fielding arrangements, particularly when spinners operate in tandem. However, transferring that success directly to New Zealand's bouncy conditions is a different proposition.
New Zealand repeatedly tested Axar with short deliveries. He appeared to search for an escape through cut shots and similar improvised strokes. He had lost his wicket through a comparable approach in the opening ODI. In the second match, the pattern returned. Axar scored seven from 17 balls before falling to Matthew Fisher. His attempted ramp against a short delivery was poorly executed, and Jacob Duffy completed the catch at third man.
The analytical issue is larger than one dismissal. When a batter displays similar difficulties against the same bowling strategy in consecutive matches, the batting role and selection decision deserve review. One dismissal may be variance, but a repeated technical pattern provides useful evidence for team management.
KL Rahul offered a contrasting response on the same pitch. He read the bounce, controlled his pull shots and was prepared to defend when necessary. Rahul remained unbeaten on 26 from 38 deliveries. It was not a substantial innings in terms of runs, but his responsibility was to preserve wickets and manage pressure.

Rahul's innings demonstrated that a technical solution was available. India had a batter capable of adjusting his stroke selection to the height of the delivery. Promoting Axar ahead of him delayed the use of that option.
Shreyas Iyer also attempted to counterattack. He scored 30 before a well-directed short delivery brought his dismissal. New Zealand's strategy was effective because the bowlers were not relying on pace alone. They were reading the batters' responses and adjusting their lengths and lines accordingly.
New Zealand's plan and the gap in India's preparation
An interesting symmetry emerged between the two innings. India's bowlers used short deliveries successfully against New Zealand in the first innings. New Zealand then employed the same approach against India's batters. Both teams faced the same surface, but their batters responded differently.
Gurnoor Brar's four wickets demonstrated that Indian bowlers could exploit the bounce. Meanwhile, Kyle Jamieson and Jacob Duffy applied similar pressure in the chase, taking three wickets each.
It would therefore be inaccurate to blame the pitch entirely. If India's bowlers can succeed with short-pitched deliveries on the same surface, India's batters need a systematic answer to that challenge.
The gap between India's bowling plan and its batting preparation is a more significant warning for the next overseas tour. Net practice against fast deliveries alone will not be enough. Batters need to work on shot selection against different heights, lines, speeds and fielding arrangements.
In my experience, technical weaknesses and poor shot selection must be recorded separately. Shubman Gill's early dismissal, Virat Kohli's loose shot and Rohit Sharma's risky response under pressure cannot automatically be explained by the same cause. Some wickets result from exceptional bowling; others come from poor decisions. Combining them into one category makes it harder to identify what the team must correct.
Rain and DLS: the context behind the result
India reached 113/7 in 26 overs when rain interrupted play. The visitors needed 22 runs to win and had three wickets remaining. Under the revised 37-over target, India were four runs ahead of the DLS par score. Further play became impossible, and India won by four runs under the Duckworth-Lewis-Stern method.
An important scorecard clarification is necessary: India were not all out for 113. They were 113/7, with three wickets remaining. The reference to a five-match ODI series also does not match the available match record. This was a three-match ODI series, and the victory gave India a 2-0 lead.
In rain-affected cricket, DLS influences more than the revised target. The par score changes with wickets and overs remaining. Consequently, 113 should not be interpreted as a completed Indian innings. The batters struggled in difficult conditions, but the result was also influenced by the weather and the DLS calculation at the time of the interruption.
The victory was important for India's series position, but it did not resolve the batting questions. India won the match, yet concerns about early wickets and the middle-order structure remained. Results and performance need separate assessments.
Two formats, two generations and different selection requirements
The two matches also highlighted differences in India's squad structure. In T20 internationals, Abhishek Sharma and Vaibhav Sooryavanshi demonstrated how aggressive young batters can redefine the powerplay. In the ODI, established players such as Rohit Sharma, Virat Kohli, Shubman Gill, Shreyas Iyer and KL Rahul had to manage the innings according to the conditions.
This contrast reinforces the need for format-specific selection. In T20 cricket, aggression, early pressure and maximum scoring opportunities may be priorities. In ODIs, batters must adjust their tempo, preserve wickets and fulfil different roles during different phases of the innings.
Abhishek's 113 provides an encouraging indication of his potential. However, one extraordinary innings from 38 balls cannot establish sustained international dominance. His strike rate, average and performances against high-quality attacks over the next ten or more international innings will provide a more useful assessment.
Likewise, it would be premature to declare India's batting fundamentally weak on the basis of one rain-affected ODI. The strongest conclusion is narrower: promoting Axar Patel to No. 5 was less suitable than the available alternatives in Wellington's conditions.
The next test: selection must account for the pitch
India have taken a 2-0 lead in the ODI series. The immediate result is positive, but the next challenge is to ensure that the batting order reflects the conditions. Axar's promotion may be useful on slow, turning surfaces. On a fast and bouncy pitch, the argument for selecting a specialist batter becomes stronger.

Three indicators deserve attention in the coming matches. First, can Axar change his shot selection against short-pitched bowling? Second, will KL Rahul be promoted earlier in the middle order on seaming surfaces? Third, can senior batters such as Rohit Sharma and Virat Kohli manage risk more effectively during pressure situations?
The next phase is equally important for Abhishek Sharma. His 113 demonstrated his upper performance ceiling. The challenge now is to reproduce that impact across different pitches, bowling strategies and match situations.
I opened the phase ledger, and the one-run final had taught me that decisive moments must be understood through the overs that preceded them. The same principle applies in Wellington. The T20I explosion demonstrated India's attacking capacity, while the ODI exposed the importance of technical preparation and condition-specific selection.
When India next encounters a bouncy surface like Wellington, the real test will be less about scoring runs and more about sending the right batter at the right time. Will team management make that distinction in its next selection decision?
