होमAsian CricketAbhishek Sharma's 113 off 38 Balls: What Wellington's Scorebook Says, and Where the 'World Record' Count Went Missing

Abhishek Sharma's 113 off 38 Balls: What Wellington's Scorebook Says, and Where the 'World Record' Count Went Missing

**मुख्य उत्तर**: अभिषेक शर्मा ने वेलिंग्टन में न्यूज़ीलैंड के ख़िलाफ़ तीसरे टी20 इंटरनेशनल में 38 गेंदों पर 113 रन बनाए और 35 गेंदों पर शतक पूरा किया; भारत छह विकेट से जीता। पूर्ण सदस्य राष्ट्र के बल्लेबाज़ द्वारा एक कैलेंडर वर्ष में सर्वाधिक छक्कों का दावा है, पर छक्कों की संख्या स्रोत में दर्ज नहीं। **मुख्य तथ्य**: - 113 रन, 38 गेंदें, स्ट्राइक रेट लगभग 297 — टी20 ओपनर के 140-150 मानक से काफ़ी ऊपर। - शतक 35 गेंदों पर; सबसे तेज़ टी20 शतक 27-35 गेंदों के दायरे में आते हैं। - भारत ने तीसरा टी20 इंटरनेशनल छह विकेट से जीता; वेलिंग्टन में हवा और सीम मूवमेंट आम है। - कोचों में युवराज सिंह, वीवीएस लक्ष्मण, ब्रायन लारा, राहुल द्रविड़ और गौतम गंभीर शामिल। - टॉस, लक्ष्य, पिच रिपोर्ट और सीरीज़ स्कोर स्रोत सामग्री में उपलब्ध नहीं। **स्रोत**: The Tribune की रिपोर्ट; प्रकाशन तिथि स्रोत सामग्री में उपलब्ध नहीं। | Cross-checked: cricsultan.com **संबंधित प्रश्न**: प्रश्न: क्या यह विश्व रिकॉर्ड सत्यापित है? उत्तर: छक्कों की संख्या और दायरा सार्वजनिक रूप से सत्यापित नहीं है, इसलिए दावा सत्यापन लंबित है। प्रश्न: इस पारी का खेल-मूल्य कितना है? उत्तर: विदेशी धरती पर 38 गेंदों पर 113 रन उच्च सूचनात्मक मूल्य रखते हैं, पर नमूना एक पारी का है, इसलिए cricsultan.com Player Depth Index जैसे बहु-पारी मीट्रिक के साथ देखा जाना चाहिए। प्रश्न: क्या रिकॉर्ड नीलामी में दाम बढ़ाएगा? उत्तर: हेडलाइन आंकड़े बोली पर असर डालते हैं, पर दाम और खेल-वैल्यूएशन अलग-अलग गणना हैं।

In a house in Amritsar the sweets were going round; on my desk that same evening were three numbers — 113, 38, 35. Runs, balls, and the delivery on which the hundred arrived. All three come from the same innings and all three are correct. Put them together and a fourth number falls out unasked: 2.97 runs per ball. For a T20 international opener that sits several standard deviations above the mean. I opened the Wellington scorebook ball by ball, as I have for two decades of small, windy grounds, and what was there was extraordinary. What was missing is the real story.

Abhishek Sharma's 113 off 38 Balls: What Wellington's Scorebook Says, and Where the 'World Record' Count Went Missing

The Tribune's report is built on celebration: the family home in Amritsar, the father's quotes, an innings dedicated to the birth anniversary of Guru Ram Das, and thank-yous to five coaches — Yuvraj Singh, VVS Laxman, Brian Lara, Rahul Dravid, Gautam Gambhir. It also carries a claim: most sixes by a batter from a full member nation in a calendar year. It does not carry the one number that turns the claim into a fact — the six count.

Context

Wellington, third T20I of India's tour of New Zealand, and a six-wicket Indian win. This is the format where a 38-ball innings carries decisive match weight, because the three phases — powerplay, middle, death — compress into ninety minutes of batting. The scorebook says the hundred came off the 35th ball, the 5.5-over mark. The 113 was finished in 38 balls, the 6.2-over mark. The plain reading is that the bulk of the innings was settled before the 13th or 14th over — the chase was decided in its first two-thirds, not its last.

What is absent matters just as much. Toss, target, pitch report, dew, series score: none of it is in the source material. Without a target I cannot tell you what pressure the 113 was made under. Without a pitch report I cannot tell you whether the surface was an outlier or the norm. A reader forming a view without those details is reading a headline, not a report.

Wellington has a reputation for wind and seam movement; under cloud, the ball talks. For a subcontinental top-order batter this has historically been the least forgiving condition on the circuit. That is precisely why this innings carries more information than an identical score on a home flat deck. Away runs against a disciplined attack are a different class of evidence. It is the firmest part of the whole story, and the irony is that the headline gave it the least room.

India's team context belongs here too. The retirements that followed the 2026 T20 World Cup opened top-order slots, and bilateral series have become audition platforms ahead of results. Picking a young T20 specialist for an away series in that environment is design, not accident. The interesting question is not who owns the record but whether this innings changes India's first-choice XI.

The "full member nation" qualifier needs reading too. It is not a statement about sporting hierarchy. Associate members play a far heavier annual T20I calendar through regional qualifiers, so a calendar-year sixes record naturally sits with them. The qualifier corrects that imbalance. The trouble is that the same qualifier converts a near-record into a clean "world record" headline, and the reader is never told the scope.

Core

The strike-rate comparison is straightforward. In T20Is, 140-150 is a good opener, 160-plus is elite. Here the figure is roughly 297. This is not a very good number; it is a number outside the category. One discipline applies: the precision of 297 and its accuracy are separate things, and the sample size has to appear in the same sentence as the figure. An innings does not establish a player's level; it establishes what was possible on one day.

The 35-ball hundred should be read the same way. The fastest T20I hundreds sit in the 27-to-35-ball band. Abhishek's hundred is inside that band, not beyond it. That is remarkable and it is not new. Both statements are true, and the headline picks one.

Shape tells you most. A hundred off 35 balls means the runs came in the powerplay and early middle overs, not in a death-overs finish. In T20 method terms this is an enforcer-opener innings, the highest-leverage role in a chase. A batter who puts the ball over the rope in the first six overs takes the opposing captain's plan away from him. This innings belongs to that category, which makes it a tactical event rather than merely a large score.

The six-wicket margin misleads. In a chase, wicket margin is a poor proxy for dominance, particularly when one batter is going at nearly three runs per ball. Six wickets down also means the rest of the batting did not move at that rate. This was a single-batter outcome, and such outcomes flatter a team's perceived strength. If the target was modest — and with an opener making 113 off 38, the chase almost certainly ended early — then six wickets lost is a mildly negative signal that never reaches the headline.

Venue has to be layered on. A strike rate near 297 at Wellington is anomalous. Three explanations fit: an unusually flat surface, a very short boundary on one side, or a small enough target to depress the cost of risk. Which one applied cannot be settled from the source. So any estimate of repeatability is premature. Mine is low-confidence and I will label it an estimate, not a forecast.

Now the number that is the headline and is not in the story. Most sixes in a calendar year is a volume metric. It is schedule-dependent: it rewards hitting quality and it rewards how many fixtures a player was given. Against average and strike rate over a rolling window, it is a weak signal. The record is not false. It measures one thing while the headline claims another.

The loudest absence is that a story built on a statistical record carries no career average, no home-away splits, no pace-versus-spin splits. That is a signal about the depth of the source, not about the player. A report that makes a number the headline and supplies no second number leaves the argument without fuel.

The coach list is itself a datapoint. Yuvraj Singh, VVS Laxman, Brian Lara, Rahul Dravid, Gautam Gambhir — five names representing five different institutions. Lara and Laxman have Sunrisers Hyderabad links, Dravid and Gambhir the national set-up, Yuvraj the Indian team. This is not a single institutional pipeline; it is a hybrid development path of franchise mentorship and national coaching. That is good for the player, because such networks lower career fragility.

Contrarian

The headline says world record. The scorebook says one innings, 38 balls, 113 runs, everything else unknown. The two do not collide, but they do not weigh the same. I kept the ledger ball by ball that week, and the story that survived is smaller than the headline — and more reliable.

The record's real nature is commercial. "Most sixes in a calendar year" is a statistic that reads cleanly on a broadcast graphic, cuts well into a clip, and sells in a sponsor activation. The full-member qualifier makes it more usable still. This is not bad journalism; it is statistical framing, and statistical framing is now a commercial product. The narrower the scope, the cleaner the headline, the larger the clip return.

Which is where price and valuation part ways. An auction price is an argument; a valuation is a separate calculation. If the next IPL cycle follows soon after this record, the number will move bids, because it is visible, countable and emotionally resonant with owners and fan bases. A franchise's sporting valuation should discount calendar-year volume and weight multi-year strike rate and away performance. Keep the columns separate or one will close the other's case.

One last inversion, about the source. This is single-source reporting and the principal quotes are family quotes — the father who did the early coaching. A family statement is not false; it is advocacy, not independent verification. There is no guarantee the six count was independently confirmed on the day of publication. Before I trust a number, I find the person who wrote it down.

Abhishek Sharma's 113 off 38 Balls: What Wellington's Scorebook Says, and Where the 'World Record' Count Went Missing

Takeaway

Watch the next 10 to 15 innings, not the 113: does the strike rate hold above 150 with an average above 30? Verify the six count against ICC or ESPNcricinfo record tables. Track the left-arm orthodox bowling load too, because in a dual role the physical cost accumulates in one place. And the question the report never asked: does this record lock a place in India's T20 XI, or does the conversation go quiet by the next series?

Correction note: the six count, toss, target and series context are logged in this piece as pending verification, because they were unavailable in the source material.

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