Two 113s in Wellington, One False Comparison: Why Promoting Axar Patel to No. 5 Cost India

The shot Axar Patel played to the short ball in Wellington was a rerun of the series opener — same top-edged cut, same aerial control lost, same catch. Being dismissed the same way across two separate innings is a technical pattern, not variance. On the same pitch, against the same bowling, KL Rahul stood at the other end riding the bounce, pulling with control, keeping the ball down. That contrast is the actual story of this match.

The week produced a second coincidence. In a T20I, Abhishek Sharma struck 113 off 38 balls; in a rain-curtailed ODI, India's entire innings folded for 113. One number, two different sports, and a headline that writes itself. The attraction is rhetorical, not statistical — and that distinction is the foundation of this report.

I built the spreadsheet before I knew it was a resume, and the habit holds. The sample is two matches: the second ODI of a five-match series and the third T20I. The two formats were coded separately and never merged — different field restrictions, different ball condition, different over budget. The coding rule was kept blunt: dismissal mode, delivery length (short/good/full) and shot control (controlled versus aerial).

The ODI was rain-curtailed, with a revised target of roughly 135. Reduced overs compress the middle phase, the exact passage where India's line-up normally rebuilds, which multiplies the value of early wickets. Wellington's drop-in surface was weather-affected and New Zealand bowled a sustained short-ball barrage from both ends. The decisive phase was not the death overs but the first ten overs of the chase.

One honesty note before the analysis runs away. The figure of 397 runs in 33.2 overs cannot belong to a single T20 innings — a side gets a maximum of 20 overs. The most plausible reading is a combined aggregate across both innings, roughly 11.9 runs per over. It is treated here as data pending verification, because a conclusion built on a typo is not a conclusion.

Axar Patel's promotion to No. 5 was a role error, and the evidence repeats across two matches. His career slot is lower-middle order, a spin-bowling all-rounder, not a top-five batter. Management's stated rationale was breaking right-hander monotony. That logic holds on a neutral surface; on a seaming, bouncing deck the technique-versus-conditions variable outranks handedness. The same experiment worked on Dubai's slow turners during the Champions Trophy, and a condition-specific success has now been generalised into a default rule.

Rahul is the direct counterfactual. Same pitch, same attack, same pressure — balanced footwork against bounce. When a specialist handles precisely the threat that removed the promoted all-rounder, the explanation stops being the conditions and becomes the selection. Selection is the tractable variable; weather is not.

The technical vulnerability is real, and the strongest proof is India's own bowling. India's seam attack, Gurnoor Brar included, ran the same short-ball plan against New Zealand's batters and made it work. If your bowlers can exploit bounce, your batters should have been drilled against it. That is a preparation asymmetry: the plan was built in the bowling room and never reached the batting room.

The T20I numbers speak more cleanly. A hundred runs in five overs is 20 an over — the match was decided inside the fielding-restriction phase, the most predictive phase in the format. Abhishek's 113 off 38, a strike rate near 297, was more than the rest of the team combined, which is single-player dependency, not a system. That kind of innings arrives once a season; treating it as evidence of settled international dominance is premature. Vaibhav Sooryavanshi's inclusion signals a new T20I cohort has arrived while the ODI top order remains the older generation. That roster asymmetry will persist for a while.

Here is the part the commentary box skips. The two 113s are a rhetorical pairing, not a statistical one — different format, different field restrictions, different ball, different over count. The only valid bridge between them is the technical short-ball theme, never the run totals. Second, rain and DLS are an uncontrolled variable: the revised target may have inflated the difficulty of the chase relative to the pitch's true scoring value. One curtailed, weather-affected match is not evidence of a series trend.

Third, and sharpest: Rohit Sharma and Virat Kohli were both dismissed to loose shots, not unplayable deliveries. A short-ball technique gap can be netted out; a loose-shot habit cannot. In my years of watching matches, approach patterns repeat faster than technical ones, and you need at least three or four innings before you call it a pattern rather than a bad afternoon.

A hot take has to survive the cost-per-win test before I repeat it. The claim that passes here is narrow: Wellington was not proof of a batting decline, it was proof of a selection error at No. 5, with a repeat dismissal pattern logged across two innings and a counterfactual standing at the other end on the same square.

The forward signal is specific. Watch the team sheet on the next seaming surface: whether Rahul stays below Axar. Watch Axar's dismissal type across his next three to five innings — two top-edged pulls in three would confirm the pattern and force the selection rule to change. Watch Abhishek's strike rate over a ten-innings window, not one. I am writing all three down before the series ends, so nobody has to pretend afterwards that the result was obvious.