Wellington’s Two 113s: Abhishek’s Storm and India’s ODI Technical Test

Wellington produced two completely different stories around the same number. In the third T20I, Abhishek Sharma scored 113 from 38 balls, at a strike rate of roughly 297.37. In the rain-affected second ODI, India were bowled out for 113 while chasing a revised target reported at around 135. Put the two figures beside each other and the headline writes itself. Watch the cricket more carefully and the comparison immediately breaks down.

I filed Bangladesh’s first Test victory from the boundary rope at Chittagong in January 2026. The phone stayed in my pocket while the sounds of the ground went into my notebook. That day taught me that the same number can carry different meanings in different conditions. In Wellington, Abhishek’s 113 represented the outer limit of T20 aggression; India’s ODI 113 exposed a combination of conditions, shot selection and role mismatch.

Two formats, two separate games

The T20I must be read first. The available analysis says India scored 100 runs in five overs. If the figure is confirmed by the official scorecard, the match was effectively taken away from New Zealand during the powerplay. The partnership between Abhishek Sharma and Vaibhav Sooryavanshi left New Zealand little time to settle on a length. During fielding restrictions, bowlers have fewer defensive options while batters have more room to accept risk.

Abhishek’s 113 came from 38 balls. That is an extraordinary international T20 outlier, not yet a career benchmark. The source material also refers to 397 runs in 33.2 overs, but that cannot describe one T20 innings. It may be a combined match aggregate or a transcription error. The figure should therefore be verified before being used as evidence. The five-over total also requires scorecard confirmation.

The central picture remains clear. India won the opening phase before New Zealand’s bowlers could establish control. Abhishek did not wait passively for the ideal length; he changed the bowler’s preferred length by moving forward, using the crease and forcing risk into the field. When a batter controls the length rather than merely responding to it, the powerplay restrictions become even more valuable.

The innings may signal a new T20 generation, but it should not yet be treated as proof of sustained dominance. Thirty-eight balls can reveal a ceiling; they cannot establish a baseline. A ten-innings sample of strike rate, average and powerplay impact will tell us whether this was a breakthrough or an exceptional peak.

The ODI: 113 before the middle order could settle

The ODI had a different structure. Rain shortened the match and India were set a revised target of around 135. The exact over allocation and DLS calculation are not specified in the available material, so this should not be read as a normal 50-over chase. In a shortened contest, every early wicket becomes more valuable because the batting side loses the time needed to repair the innings.

On Wellington’s drop-in surface, New Zealand used short-pitched bowling repeatedly. This was not an occasional bouncer. Bowlers worked from both ends to push Indian batters onto the back foot, then waited for hurried pulls, cuts and hooks. Weather and variable bounce made the plan more effective.

Shubman Gill fell early. Virat Kohli and Rohit Sharma also departed after shots that were not entirely forced by unplayable deliveries. That distinction matters. New Zealand created pressure, but India also rewarded it. In a shortened chase, a loose decision carries more weight because there is no long innings in which to recover.

Shreyas Iyer briefly tried to answer pace with aggression, but another well-directed short ball ended that approach. Against this kind of bowling, a batter needs to make three decisions quickly: get out of the line, stay sufficiently controlled while playing from the back foot, or force the bowler to return to a fuller length. India did not consistently show those choices.

KL Rahul was the clearest counterexample. According to the available analysis, Rahul rode the bounce and controlled his pulls while other batters looked uncertain. On the same pitch and against the same attack, one batter recognized the threat and managed it. That makes the Axar Patel-KL Rahul selection debate more defensible than any sweeping claim about the future of India’s batting.

Axar Patel: left-hand balance or a role mismatch?

India sent Axar Patel in at No. 5. The management rationale, as described in the analysis, was to break the monotony of a right-handed batting line-up. That logic can work on a slow, turning pitch. Axar’s role during the Champions Trophy in Dubai may have strengthened the case.

Wellington, however, posed a different question. Was left-right balance more important than the ability to handle short bowling? Once the pitch profile changes, the selection logic must change with it. A role that succeeds on a slow surface cannot automatically be carried over to a deck offering seam, pace and bounce.

The concern around Axar is not based on one dismissal alone. The analysis says he was dismissed by similar short-ball tactics in the series opener. Repeatedly reacting to the same threat with a cut or pull turns a single mistake into a technical pattern. The issue is not Axar’s value as an all-rounder; it is the expectation placed on him when he is promoted into a specialist middle-order batting role.

If Rahul is in the XI and the central threat is the short ball, conditions should influence the order more than a general left-right principle. This does not make the decision a permanent selection error. Rain, DLS and the shortened nature of the chase affected the contest. It does provide a repeatable lesson: handedness should not outrank pitch-specific technique.

India’s bowlers asked New Zealand the same question

The match contained an important contradiction. India’s bowlers reportedly used the short ball successfully against New Zealand, with Gurnoor Brar among the bowlers involved. New Zealand’s batters also struggled against the bounce. That suggests the pitch was not simply biased against one side. The team that combined length, line and field placement more effectively gained the advantage.

It also means India had an internal example of how to attack the surface. The bowlers understood where to push New Zealand’s batters; the batters did not consistently display an equivalent plan. That is a preparation asymmetry. Practising against short bowling in the nets is different from deciding, under match pressure, which ball to leave and which ball to attack.

In my years of watching matches, I have seen overseas technical weaknesses hidden behind the name of a pitch. Wind, rain and bounce matter, but they are only half the sentence. The other half asks what Rahul did differently and how India’s bowlers made New Zealand uncomfortable. Wellington supplied both sides of that comparison.

The danger of joining the two 113s

Abhishek’s T20I 113 and India’s ODI 113 are two strong headlines from the same tour, but they have no direct statistical relationship. The T20I offered a short innings, powerplay restrictions and a high reward for aggression. The ODI involved rain, a revised target and sustained short-pitched bowling.

It is tempting to say that India moved from a batting storm to a batting crisis within a week. That would be incomplete. The two matches also involved different personnel and different format roles. The T20I top order included Abhishek Sharma and Vaibhav Sooryavanshi, while the ODI batting structure involved Rohit Sharma, Virat Kohli, Shubman Gill, Shreyas Iyer and Axar Patel. Treating them as one batting unit erases the format divide.

There is one valid bridge between the matches: control of the opening phase. India controlled the first five overs of the T20I. New Zealand controlled the early phase of the ODI. In one match, the batters imposed their lengths on the bowlers; in the other, the bowlers imposed theirs on the batters.

“The purse is a number; the back of the bus is the story.” I learned that during the 2026 Bangladesh Premier League. A scorecard can do something similar: it displays the visible figure while concealing the hierarchy beneath it. Wellington’s two 113s invite comparison, but the deeper story is who adapted to the conditions.

Senior batters and the question of haste

It would be easy to turn Rohit and Kohli’s dismissals into a story about age or transition. The available evidence supports a narrower reading: both were dismissed after loose shots. That is different from being beaten by an unplayable ball. Experienced batters can handle bounce when they are not trapped by a pre-decided attacking plan.

India’s review should ask whether the wickets came from exceptional bowling or from avoidable decisions. The sample is too small for a long-term decline verdict. If similar dismissals continue in the next matches, however, the issue will move beyond New Zealand’s conditions.

Abhishek’s innings deserves the same discipline. His range is obvious, but the next test will come when opponents alter pace and length after spreading the field. The next ten innings will tell us more than the first 38 balls.

The outside noise and the internal decision

Public debate will usually take two routes. One side will call Abhishek’s 113 the arrival of a new generation. The other will treat India’s 113 as evidence of a batting crisis. Both reactions risk turning one extreme match into a general rule.

The most sustainable debate concerns Axar at No. 5. It has three concrete reference points: a repeated dismissal pattern, Rahul’s contrasting control on the same surface and a general left-right rationale that may not have been suited to the conditions. That is a more useful argument than a broad declaration about India’s batting health.

Three press-box veterans can agree on a fact and still miss the beat. Here, the fact is 113. The beat is hidden in the first six to ten overs. India owned that phase in the T20I; New Zealand owned it in the ODI.

“Ten wickets fell while my phone stayed in my pocket” is more than an old reporting line. A match observer should notice where a bowler returns after a wicket, where a batter looks before the next ball and which substitute carries drinks from the dressing room. Strategy often appears in body language before it appears in the scorecard. In Wellington, the Indian batters’ response to the short ball said plenty.

The next signal

India’s next ODI team sheet will reveal whether No. 5 is selected according to pitch profile or according to a general combination principle. If the surface again offers seam and bounce, Rahul is the more practical specialist batting option. The question is not whether Axar belongs in the XI; it is what role the conditions justify.

In the T20I, Abhishek and Sooryavanshi must now convert aggression into repeatability. One innings has shown the ceiling, and the opposition will design plans specifically to lower it. India’s ODI side must show that Wellington’s 113 was a conditions-heavy failure rather than a permanent technical illness.

Forty years of keeping the beat, and the deadline still taps first. Before the next team sheet arrives, one question will remain: will India select for the pitch in front of them, or carry the logic of the last successful surface into the next one?