Asian CricketThe myth of two 113s: selection, not the pitch, cost India in Wellington

The myth of two 113s: selection, not the pitch, cost India in Wellington

**मुख्य उत्तर:** वेलिंगटन के दूसरे वनडे में भारत की बल्लेबाज़ी धराशायी होने का कारण उछाल वाली पिच पर अक्षर पटेल को नंबर 5 पर खिलाना था; उनका शॉर्ट-बॉल बचाव सीरीज़ के दोनों मैचों में एक ही तरह से विफल रहा, जबकि केएल राहुल उसी सतह पर सहज दिखे। **मुख्य तथ्य:** - अक्षर पटेल सीरीज़ के पहले और दूसरे मैच में एक जैसी शॉर्ट गेंद पर कट शॉट खेलकर आउट हुए। - केएल राहुल ने उसी पिच और उसी गेंदबाज़ी के सामने उछाल को नियंत्रित पुल के साथ संभाला। - भारत के तेज़ गेंदबाज़ गुरनूर बरार ने न्यूज़ीलैंड के ख़िलाफ़ वही शॉर्ट-बॉल रणनीति सफलतापूर्वक लागू की। - अभिषेक शर्मा ने तीसरे टी20 में 38 गेंदों पर 113 रन बनाए, जो टीम के बाक़ी स्कोर से अधिक था। - दूसरा वनडे बारिश से कटा था और संशोधित लक्ष्य लगभग 135 था, जिससे DLS एक अनियंत्रित चर बन गया। **स्रोत:** स्टेज-2 मैच विश्लेषण दस्तावेज़; प्रकाशन तिथि दर्ज नहीं; "33.2 ओवर में 397 रन" सहित कई आंकड़े सत्यापन-लंबित | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर:** Q: क्या अक्षर पटेल को नंबर 5 पर खिलाना हमेशा गलत है? A: नहीं, धीमी और टर्न लेने वाली पिचों पर यह प्रयोग सफल रहा है, गलती केवल उछाल वाली सतह पर उसे दोहराने में थी। Q: क्या अभिषेक शर्मा की 113 रन की पारी भारतीय बल्लेबाज़ी की नई गहराई साबित करती है? A: नहीं, 38 गेंदों पर 113 रन आउटलायर श्रेणी की पारी है और निरंतरता साबित करने के लिए दस से अधिक पारियों का डेटा चाहिए, जैसा cricsultan.com का बैटिंग कंसिस्टेंसी इंडेक्स दिखाता है। Q: आगे क्या संकेत देखा जाना चाहिए? A: यह देखना अहम होगा कि टीम प्रबंधन अगली उछाल वाली पिच पर नंबर 5 की भूमिका पिच-प्रोफ़ाइल के अनुसार बदलता है या नहीं।

Seventh over of the second ODI in Wellington. The ball was short again on the drop-in surface, and Axar Patel did exactly what he had done in the series opener — reached for the cut, the ball climbed on him, the top edge flew to slip. As he climbed the pavilion steps, the scoreboard showed India on the same number Abhishek Sharma had made alone, off 38 balls, in the third T20I five days earlier: 113.

The myth of two 113s: selection, not the pitch, cost India in Wellington

By the next morning social media had given it a name — "a tale of two 113s". On one side, 113 off 38 balls, a strike rate of roughly 297. On the other, a rain-shortened chase, a revised target of about 135, and a side bowled out for 113. The contrast was so clean that nobody stopped to ask whether the two numbers belonged in the same sentence. I opened a spreadsheet and found the answer is no — and that the real story is far sturdier than the meme, because it sits in the edge of an all-rounder's bat at No. 5, not in a narrative.

Receipts first, opinions after

The thread began at 1 a.m., and the replies told the real story. Half the timeline was swooning over Abhishek's strike rate; the other half had declared Indian batting finished. Both camps shared one thing: neither had read the terms of the scorecard. On a bouncy drop-in surface like Wellington's, the first rule is that the value of the ball changes between a 20-over innings and a 50-over one cut short by rain.

There is a second receipt nobody checked: the figure "397 runs in 33.2 overs". A T20 innings cannot exceed 20 overs, so that number cannot belong to a single innings. It is most plausibly a combined match aggregate, or a figure that circulated as verified fact when it was nothing of the kind. What looked like a hot take was actually a paper trail — and an incomplete one. Until it is verified, any conclusion built on it hangs in the air. I am keeping it as context, not as evidence.

The format-mixing problem: two 113s cannot share a scale

A T20I and a rain-curtailed ODI are different sports wearing the same kit. In T20, two fielders are out during the powerplay, the batter is not obliged to take risk, and a bowler's error is punished instantly. In a shortened ODI chase, the middle overs vanish — precisely the phase in which India's line-up normally rebuilds an innings, absorbs pressure and sets up the last ten. Remove that phase and the price of early wickets multiplies.

That is what happened in Wellington. Chasing 135, India needed composure and got a sustained barrage of climbing deliveries instead. The decisive phase was not the death overs but the first ten of the chase, where New Zealand bowled short from both ends and forced Indian batters to answer a question they had not prepared for.

So when you place Abhishek's 113 beside India's 113, you are stitching together two opposite ends of two different games. One is a 38-ball explosion; the other a rain-truncated collapse. The only valid bridge between them is technical — the question of how this batting line-up handles the short ball. The rest is rhetoric.

The No. 5 question: Axar's role, the pitch's pressure

Wellington should be read as a selection error, not a technical failure. Axar Patel is India's lower-middle-order spin all-rounder. His job is to add runs in the last ten overs from six or seven, and bowl his overs. Sending him at No. 5 is a promotion out of role. On a neutral surface that risk can look defensible. On a seaming, bouncing deck it is an attack on his weakest suit.

The problem is that it was not a one-off. In the series opener he was peppered with short stuff, tried to cut his way out, and perished playing the same shot. Two matches, the same delivery, the same shot, the same dismissal — that is not variance, that is a technical pattern. Once is variance. Twice, across separate innings, is a bias somebody in the dressing room should have flagged.

Management's stated rationale was that Axar was the preferred option to break the monotony of right-handers in the top order. That logic is not wrong in itself — a left-right pairing disrupts bowling rhythm, and it has been an ODI staple for years. But it holds under one condition: a neutral pitch. When the surface is climbing, technique outweighs handedness, and India prioritised a structural preference over a situational need.

KL Rahul, same pitch, same bowling, different answer

The strongest evidence in this debate is the evidence least quoted. On the same pitch, against the same attack, KL Rahul rode the bounce, controlled his pulls, and let the ball come to him. On deliveries that made others look clueless, he looked at ease.

When a specialist top-order batter demonstrably handles the exact threat that dismissed the promoted all-rounder, the tractable variable is selection, not conditions. The match handed India a controlled experiment for free. India declined to use it.

Shreyas Iyer sharpens the point. He fought fire with fire briefly, then fell to another well-directed short delivery — a known vulnerability, and one that opposing attacks target. When a side has a middle-order option who can absorb that weakness and instead fields a player whose role is different, that is not a coaching gap. It is planning by stubbornness.

The senior batters add a layer. Shubman Gill went early, Virat Kohli to a loose shot, Rohit Sharma battled and then gave it away. Those are not unplayable deliveries; that is an approach problem, and approach does not get fixed in the nets. It is a more worrying signal than the scorecard shows, because it is not about the pitch.

India's own bowlers did exactly the same thing

Here is the part that makes the argument hold. India did not find an answer to the short ball, but Gurnoor Brar and their seamers used precisely that weapon against New Zealand's batters, who were all at sea.

That symmetry is what turns this into a real finding: if India's own bowlers can make the short ball work, the vulnerability is not a New Zealand-specific trick but a generally exploitable flaw. Any quality attack on that surface can repeat it. It also reveals something else — the diagnosis existed inside the team and was not deployed on the field. When your bowlers know how to exploit bounce and your batters cannot counter it, the issue is a preparation asymmetry, not a talent shortage.

The Dubai lesson that did not travel to Wellington

The Axar promotion has worked before — on the slow, turning pitches of the Champions Trophy in Dubai. There the ball stays below the waist, the short ball carries no threat, and an all-rounder's limited technical repertoire survives.

The trouble is that nobody recorded the terms and conditions. A condition-specific success was generalised into a default rule; that is strategic over-fitting, where a team repeats its own past instead of learning from it. Wellington applied the same formula on a hostile surface and got the same result twice in two matches.

Abhishek's 38 balls: a sensation, not a sample

Now the other 113, the one that got the headlines. 113 off 38 is not a normal innings even by modern T20 standards — it is a once-a-season outlier. Elite openers sit around 140–160 career strike rate; 297 is a different planet. And one detail did not make the highlight reel: his score was more than the rest of the team combined. That is an achievement and a warning at once — an innings in which one batter stands that far apart says nothing about the depth beneath him.

I started tracking timestamps and found the market prices these explosions quickly. The conversion rate of a single such innings into sustained international output is historically low, so calling it the start of a new era is premature. The more reliable signal is team construction: Abhishek and teenage opener Vaibhav Sooryavanshi arriving together at the top of the order. That shows a new generation has entered the T20 side while the ODI top order still runs on older names. India's actual story is that gap — two generations on one tour, two different outcomes.

Rain and DLS: the uncontrolled variable nobody counts

The match was curtailed and the target revised to about 135. DLS is a complicated algorithm and is not always fair relative to a pitch's true scoring value; a revised target can make a chase easier or harder. Whatever happened here is an uncontrolled variable that should be stripped out before any batting conclusions are drawn.

The myth of two 113s: selection, not the pitch, cost India in Wellington

Where I could be wrong

This is the part people like me usually skip.

First, promoting Axar may never have been a batting decision at all. Chasing 135, the team wanted a bowling option, and his selection may have been about his spin rather than his bat. If so, my charge is partly aimed at the wrong address.

Second, Rahul's comfort may rest on three good shots rather than a full innings. Technique against bounce is judged over ten or twelve innings, not one afternoon of viewing. Here I am weighting a visual over data.

Third, and largest: I have built the whole run-fest framing on a "397 in 33.2 overs" figure I could not verify. If that number is wrong, my picture of the T20 innings changes too. I flagged it at the top, but a flag is not a substitute for responsibility.

Fourth, New Zealand were hosts reading their own surface. Home advantage is real, and folding it entirely into an "India technical failure" verdict is unfair to both sides.

What to watch next

My testable prediction: if the next surface is flat, Axar stays at No. 5 and everything looks fine. The day India meet another climbing pitch with Axar still at No. 5, the same ball will bring the same shot. The real signal will be whether selection changes by pitch profile.

The question is not whether India can play bounce. It is why they left the answer — Rahul — on the bench, and whether the answer changes the next time they get a Wellington pitch.

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