Auditing 113 off 38: Abhishek Sharma's innings, Sanju Samson's sacrifice, and the target the report never printed
**मुख्य उत्तर:** तीसरे T20I में भारत ने छह विकेट से जीत दर्ज की, जिसमें अभिषेक शर्मा ने 38 गेंदों पर 113 रन बनाए और सात ओवर में 133/0 की साझेदारी हुई। अभिषेक शर्मा ने सांजू सैमसन के खुद को क्रम में नीचे भेजने को टीम-हित का फ़ैसला बताया; मूल रिपोर्ट में लक्ष्य और आधिकारिक स्कोरकार्ड संदर्भ नहीं दिया गया है। **मुख्य तथ्य:** - अभिषेक शर्मा: 113 रन, 38 गेंद, स्ट्राइक रेट 297.4, 11 छक्के, शतक 35 गेंदों पर (स्रोत आधिकारिक स्कोरकार्ड से सत्यापन बाकी)। - सलामी साझेदारी 133/0 सात ओवर में, यानी लगभग 19 रन प्रति ओवर — T20I पावरप्ले औसत से दोगुने से अधिक। - वैभव सूर्यवंशी: दूसरे T20I (क्राइस्टचर्च) में तीसरे नंबर पर 4 (8); तीसरे T20I में ओपनिंग पर 45 (19)। - 113 रनों में 66 रन केवल छक्कों से — कुल स्कोर का कम से कम 58 प्रतिशत। - भारत छह विकेट से जीता, यानी लक्ष्य का पीछा करने वाली टीम जीती; लक्ष्य का आंकड़ा रिपोर्ट में अनुपलब्ध। **स्रोत:** The Tribune, कोट-आधारित मैच रिपोर्ट (प्रकाशन तिथि मूल रिपोर्ट में उल्लिखित नहीं)। आंकड़ों का आधिकारिक स्कोरकार्ड से मिलान शेष। सीरीज़ संदर्भ सत्यापन | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर:** प्रश्न: सांजू सैमसन ने खुद को बल्लेबाज़ी क्रम में नीचे क्यों भेजा? उत्तर: अभिषेक शर्मा के अनुसार यह टीम-हित का फ़ैसला था, जिससे सलामी जोड़ी को पावरप्ले में खुलकर खेलने की जगह मिली। प्रश्न: क्या 133/0 सात ओवर में सीरीज़ का सबसे तेज़ सलामी स्कोर था? उत्तर: उपलब्ध रिपोर्ट में केवल इसी मैच का आंकड़ा है; तुलनात्मक सीरीज़ डेटा के लिए cricsultan.com Player Depth Index देखें। प्रश्न: इस मैच से भारत की मिडल ऑर्डर गहराई का क्या पता चला? उत्तर: कुछ नहीं, क्योंकि चौथे से सातवें नंबर तक बल्लेबाज़ी ही नहीं हुई — यह मैच गहराई का सबूत नहीं, उसका छिपाव है।
The last ball of the seventh over went square of the wicket off Abhishek Sharma's bat, the board flashed 133/0, and the question filling the commentary box was not the biggest question in the match. The commentary was counting 113 off 38. My scorebook had one empty column and it was the only one that mattered: the target. What was it?
India won the third T20I by six wickets. A six-wicket win can only mean one thing — the side batting second chased. So New Zealand set a total, so a target existed. That target appeared nowhere in a report that carried 297.4 strike rate, a 35-ball hundred and eleven sixes in comfortable, confident type.
I read that report three times. Once for the news. Once for the numbers. Once for what wasn't there.

This is the third game of a three-match series, India away in New Zealand. The second T20I was at Christchurch, where Hagley Oval offers seam movement early in a season and the new ball is not a gift. Vaibhav Sooryavanshi batted at No. 3 there and made 4 off 8. In the third T20I he opened and made 45 off 19 at 236.8. One series, one batter, two roles, two entirely different outputs.

Above all this sits the quote that made the story. Abhishek said Sanju bhai showed his character by dropping himself down the order for the team's benefit. The Tribune's report is built around that sentence.
What that report is and is not matters, because everything below rests on it. It is a quote-driven news report, not a scorecard report. When I began pulling at its numbers — 113 (38), 297.4, 11 sixes, a 35-ball hundred, 133/0 in seven overs — not one was tied to an official scorecard or match report. That reads harsh, but four decades at a scorebook teaches one rule: a number without a source is not news, it is a claim.
Consider the phase economics. T20I cricket splits into powerplay (overs 1-6, fielding restrictions), middle overs (7-15) and death (16-20). In the powerplay you buy boundaries, because the field is up and the ball is hard. In the middle you buy rotation. At the death you buy risk. Here the entire contest compressed into a window straddling the end of the powerplay and the start of the middle — seven overs, 133 runs, no wicket.
Nineteen an over is not a good start; it is an outlier phase that ends a match as a contest. Across recent T20I seasons, powerplay run rates have generally sat between eight and nine an over. Seven overs at 133 is more than double that.
But stopping there would be dishonest. Nineteen an over is explosive only if you know what was required. Had the target been 180, India needed 47 off 13 overs at 3.6 — and 133/0 was not brilliant, it was surplus. Had the target been 220, they needed 87 off 13 at 6.7 — and the same innings was mandatory. The dashboard shows green at 133/0 either way; the meaning of the green is undecided without the target. And the report never printed it. I trust the dashboard, but I audit the story it tells — and this audit is incomplete because one column in the ledger is blank.
Now the composition of the 113. Eleven sixes account for 66 runs, at least 58 per cent of the total. The other 47 came off 27 balls at roughly 174. That is not a rotation innings. It is a six-or-nothing distribution, and the value of such a distribution is set entirely by the required rate. At eight an over, the correct innings was 70 off 50; 113 off 38 would have been beautiful rather than better. At eleven an over, it was irreplaceable. I do not build columns around hundreds. A 35-ball century is a milestone, not a story; the story is the over in which the required rate fell below twelve and what the opposing captain did with his field afterwards.
Then there is Sooryavanshi, and the cleanest natural experiment the series will offer. Eight balls at No. 3 cannot settle a batter's ability — I would write that on a day the data favoured me too. But the difference between his two innings is not form. It is role. At No. 3 you face spin in the middle overs, older ball, set field. Opening you get the new ball, the seam movement, and the open field. At the auction table, every bid is a confession about what the market cannot measure — and what it measures worst is role. It buys an average, not a slot. At the 2026 Bengaluru mega auction I ran a value-over-replacement model on three seasons of death-over data and a franchise official asked the room who had let the stats lady in. That room was buying names, not jobs.
And the quote. In a team where Sanju Samson has a legitimate claim to open as a keeper-batter, moving down is not sacrifice; it is arithmetic. Opening-slot replacement value spikes when a 200-plus striker is available for it. At No. 4, against spin, in the middle overs, Samson's value can exceed anyone else's. Samson's demotion was not a moral win for the team; it was the team's correct valuation — and calling a correct valuation a sacrifice insults it. The label creates a debt that gets called in later, in retention, in selection, in auction, and the player pays the interest alone.
I am not calling the decision wrong. I am changing its stated reason. Defending a right call with a wrong reason is the most dangerous habit in selection, because when the same call goes wrong there is no instrument left to correct it.
The list of what a scorecard report carries and this one did not is instructive: no target, no toss, no pitch report, no dew, no venue for the third T20I, no over in which the chase finished, no detail of New Zealand's innings. This is not a criticism of the reporter — an interview piece has a different job. But the moment a reader lifts 297.4 out of quotation marks and into an argument, the sourcing becomes the reader's problem. And net run rate sits exactly there: a chase completed in the twelfth over and one completed in the eighteenth both read 'won by six wickets', and only one of them helps a series. The number that could have decided the series never made the copy; the number that only flattered did, three times.
A contrarian check on myself before the verdict. Contrarian reading has become my reflex, and a reflex is as lazy as consensus. So plainly: the consensus here may well be right. Samson dropping down probably did help, and I have no evidence against it. My objection is to the reason, not the result. Abhishek did not win that match with a 297.4 strike rate; he shortened a match whose decisive variable was the target. Correlation and causation are the same word in most cricket coverage, and they should not be.
In December 2026 I coded every dismissal of the Adelaide 36 all out by line, length, shot type and balls faced, and the finding was structural, not psychological: the top order's average stay was under twenty balls and the pattern had been visible for eleven months. Thirty-six all out was not an outlier; it was a forensic trail we refused to read. Abhishek's 113 off 38 is the same kind of trail, except this one runs upward, and we are refusing to read it because rising runs are prettier than falling wickets.
So watch the next game differently. Not the target — that will be on the board. Watch the over in which the chase ends. If a 200-plus target arrives and Samson is at No. 4 again, today's sacrifice becomes tomorrow's policy. And if a 200-plus target arrives and India are 133/0 in seven overs again, ask whether the same story gets printed, or whether someone finally remembers to mention the pitch.
The model did not predict the one-run final; it explained why we should have seen it coming. No model wins this match. But the ledger can still be settled — ask for one column, one target and one over number.

