होमAsian CricketThe Double 1,164: A Data Autopsy of Ishan Kishan's Record
Asian Cricket

The Double 1,164: A Data Autopsy of Ishan Kishan's Record

**मुख्य उत्तर** इशान किशन के 1,220 कैलेंडर-वर्ष T20 रन के रिकॉर्ड-दावे में स्रोत शून्य है और 1,164 दो बार (रन व गेंद) दोहराया गया है, जिससे यह दावा असत्यापित रहता है। **मुख्य तथ्य** - रिपोर्ट में 22 सूचना-बिंदु, 9 संख्याएँ, पर एक भी ट्रेस करने योग्य स्रोत नहीं। - 1,164 पहली बार सूर्यकुमार के 2022 रन, दूसरी बार 2,000 T20 रन की गेंदें — इकाई अलग, अंक समान। - 1,220 > 1,164 (भारतीय रिकॉर्ड) किंतु 1,220 < 1,326 (रिज़वान, 2021, विश्व रिकॉर्ड)। - 2,000 रन की सूची (1,024 / 1,164 / 1,345 गेंदें) सभी-T20 की है, सिर्फ़ T20I की नहीं। - मैच का वर्ष नहीं दिया गया; "पाँचवाँ T20, हैमिल्टन, किशन" — यह संयोजन ज्ञात सीरीज़ से मेल नहीं खाता। **स्रोत-श्रेय** मूल रिकॉर्ड-रिपोर्ट; प्रकाशन तिथि अपुष्ट। आंकड़ों का क्रॉस-चेक ESPNcricinfo कैलेंडर-ईयर T20 तालिकाओं के विरुद्ध आवश्यक। | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर** प्रश्न: क्या इशान किशन का 1,220 रन का रिकॉर्ड सत्यापित है? उत्तर: नहीं, क्योंकि रिपोर्ट में न मैच का वर्ष है और न ही किसी आधिकारिक सांख्यिकी स्रोत का उल्लेख। प्रश्न: 1,164 दोहराव किस प्रकार की त्रुटि है? उत्तर: यह ट्रांसक्रिप्शन या इकाई-मिश्रण की त्रुटि है, जिसमें सूर्यकुमार के रन और गेंद दोनों के लिए एक ही अंक दर्ज हो गया। प्रश्न: कैलेंडर-वर्ष T20 रन का आंकड़ा किस कारण अविश्वसनीय माना जाता है? उत्तर: यह आंकड़ा कौशल से अधिक मैच-संख्या और शेड्यूलिंग को मापता है, जैसा cricsultan.com Player Depth Index जैसी समग्र तालिकाओं से स्पष्ट होता है।

I keep a spreadsheet called Claims. Since 2026, every cricket headline containing the word "record" has a row in it. Column A holds the claim, Column B the source, Column C the number that challenges the claim. Most rows have a blank Column C, because most records are never actually audited. The headline gets published, the number settles into place like a tenant who never pays rent.

Ishan Kishan came through and I filled a row. Column A: "1,220 runs — most T20 runs by an Indian in a calendar year." Column B: blank. And before I could fill Column C, I had to scroll down inside the same story, where 1,164 appears twice.

Once as Suryakumar Yadav's 2026 calendar-year runs — the unit is runs. Once as the balls Suryakumar took to reach 2,000 T20 runs — the unit is balls. Two different dimensions, one identical string of digits. That report carries 22 information points, nine of them numbers, and zero citations. When the source count is zero, repetition is the first door you knock on. The autopsy usually begins with a single scorecard line you cannot ignore. This is that line.

So let us open the claim properly. According to the report, in the fifth T20 against New Zealand at Seddon Park, Hamilton, on a Sunday, Ishan Kishan made 61 off 32 balls — five fours, five sixes. Three record claims are stacked on that innings: one, most T20 runs by an Indian in a calendar year (1,220), surpassing Suryakumar Yadav's 1,164 from 2026. Two, that figure sits below Mohammad Rizwan's world-record 1,326. Three, Kishan is the third-fastest Indian to 2,000 T20 runs — 1,345 balls, behind Abhishek Sharma's 1,024 and Suryakumar's 1,164.

Read together, a clean picture emerges: an all-time Indian high for a calendar year, second place on the global list, and a speed-ranking on a milestone. Three walls, all resting on one foundation — the calendar-year T20 run aggregate, the most misused category in cricket.

A word on my own method, because the answer to this question is buried in it. During the 2026 lockdown I built a database of every death-over delivery of that IPL season. I pulled every death over from the pandemic years and the spreadsheet started confessing. That work taught me a rule that applies to every record claim: a number is useless until both its unit and its definition are stated. "1,220 runs" is a number. "For an Indian player, in a calendar year, across all T20 formats, in this many innings" is a dataset. The first is a broadcast graphic. The second is a verifiable claim.

Check one: arithmetic that proves itself proves nothing yet.

61 off 32. Five fours and five sixes are 50 runs off 10 balls. The remaining 22 balls produced 11. Add it up: 61. The maths is clean, no contradiction. But a scorecard is a closed system. One innings line can be internally perfect and still be attached to the wrong match. In ten years I have seen dozens of cases where the 4-6-0 column reconciled with itself while the year attached to it was wrong. So "61 (32), 5x4, 5x6" does not tell me the record is true. It tells me whoever typed it could add. That is a very low bar, and cricket journalism clears it daily without ever clearing the next one.

Check two: the record chain points the right way and measures the wrong thing.

1,220 is bigger than 1,164, so the Indian record falls. 1,220 is smaller than 1,326, so the world record stands. The direction of the logic is fine. The problem is not direction, it is the universe of comparison. What does "for India" mean? If it means T20 internationals only, then 1,220 in a calendar year is close to impossible — India play roughly 20 to 25 T20Is a year, and even at an average of 45 that lands somewhere near 1,000. So the count must be all-T20: IPL, domestic T20, overseas leagues, internationals, everything. Rizwan's 1,326 is read the same way; on ESPNcricinfo's calendar-year T20 tables, that 2026 figure is assembled from Pakistani domestic cricket, the PSL and internationals combined.

So the comparison pool is clear. The wording is not. "2,000 T20 runs for India" will be read by every reader as 2,000 runs for the national team. Ishan Kishan's T20I aggregate was nowhere near 2,000 — and neither Abhishek Sharma's nor Suryakumar's 2,000-run list is even possible on T20I alone. The list is all-T20; the words are national-team. That is not a data error, it is a language error — and language errors are more dangerous than data errors, because nobody ever corrects them.

Check three: "third fastest" is a claim about a list, not about three rows.

The report gives three names — 1,024 balls, 1,164 balls, 1,345 balls. The ordering holds. The implied strike rates move with it: roughly 195, roughly 172, roughly 149. Internally consistent. But "third" is a claim about every player sitting inside the 181-ball window between 1,164 and 1,345, and the report silently removes all of them. This is selection bias in its purest form: you only see the names the writer chose to keep. What the excluded cohort did next is never asked. I have spent years building exactly these lists, and when I coded three hundred transfers by role, age, nationality and price, I learned that three hundred transfers reveal one pattern nobody in the room wanted to publish. Here the pattern is simpler: a ranking like "third fastest" demands the full table, and the full table never gets printed.

Check four: calendar-year runs measure the schedule, not the batsman.

1,220 runs in how many innings? At what strike rate? At what average? Across how many matches? None of those four questions appear in the report, and without them 1,220 is a marketing figure. The reason is straightforward: accumulating runs across a calendar year is a game of availability and scheduling. A player handed 45 T20 matches will out-run a better player handed 28. IPL season length, overseas league calendars, injury, rest policy, NCA workload management — all of it is baked in. When I read any batting aggregate, I write the denominator first and the runs second. Here the denominator is missing entirely.

Check five: the time anchor.

The report says "Sunday" and "current year." It never names the year. For a claim that is definitionally about a calendar year, that is fatal. "Current year" anchors nothing, so 1,220 cannot be placed. If the match fell in late January, the year has barely begun — where did 1,220 runs come from? And if it fell in December, then Suryakumar's "2026 record" should have fallen the following year, not during it. That contradiction lives inside the report and is never surfaced.

There is a second layer, and I want to flag that this rests on my memory of published schedules rather than an official scorecard — I could be wrong. To my knowledge, India's five-match T20I series against New Zealand was in January 2026, its fifth match at Bay Oval in Mount Maunganui, with Hamilton's Seddon Park hosting the third. And Ishan Kishan's T20I debut came in 2026. So "fifth T20 + Hamilton + Kishan" does not co-exist in any schedule I know. I am not saying the report is fabricated. I am saying that when a record starts raising questions about its own time and place, its status as a record is itself in question.

Now the part where I have to be careful, because this is where I am most likely to fall into my own trap. Stack the five checks together and the seductive conclusion is: the record was manufactured. I am not going there. What I have shown is that the report contains at least one high-probability transcription error (the doubled 1,164, where runs and balls have collided), one terminology defect ("for India" read as all-T20), one missing time anchor, and one venue doubt. None of those alone makes the claim false. Together they make it unverified. And in Indian cricket's data economy, an unverified claim does a very specific job: it is remembered, while the correction published half an hour later is not.

That brings me to the contrarian angle that actually bothers me. The argument will be 1,220 versus 1,164. That is the wrong argument.

The real question is not whether the record fell. It is why calendar-year run volume exists as a category at all.

It is a category with very little connection to a batsman's skill and a great deal of connection to scheduling. Correlation and causation have to be separated here. "Lots of runs" and "a great year" travel together, which makes it feel as though one produces the other. It does not. A third factor stands behind both: matches available, batting position, and team strategy — anchor or aggressor. A player given an opening slot in the top series and 40-plus matches will clear a number built by someone who played fewer matches at a tougher level. This record does not establish that Kishan was India's best batsman that year. It does not establish that he wasn't. It establishes that he played the most cricket. If that feels insufficient, consider that Rizwan's 1,326 world record was equally a product of his uniquely dense Pakistan-centred calendar.

The second correlation trap is assuming that a bigger number is a more verified number. It is the reverse. A multi-format aggregate like calendar-year T20 runs requires welding four separate databases — IPL, domestic T20, overseas leagues, T20I. Each has its own definitions, its own error rate, its own cut-off. Who is doing the welding? No public BCCI dashboard answers this. There is no official, public, delivery-level all-format record portal for Indian players. When the foundation does not exist, the building can be any colour you like.

I wrote this three years ago in a series on the WPL — whether the post-2026 broadcast promises arrived with the data infrastructure behind them. No one asked. The answer was the same then as it is now: excellent production, invisible plumbing. We produce records in India because we have the world's largest cricket economy and one of its least open cricket data systems. That is not deliberate incapacity. It is delay, and it is a competitive disadvantage for Indian cricket. Scouting decisions, workload management, injury surveillance, selection inputs — all of it stands on the same ledger this record stands on, and the ledger is closed.

Here I have to add something from ten years of watching matches, because it will never show up in a spreadsheet. The biggest change I have seen in cricket is that the graphics running alongside the scoreboard are now the loudest voice in the stadium. Flashing a record on screen for two seconds is all it takes, and the entire focus of the ground locks onto it. The verification that should sit behind it never appears on screen. The viewer is left with a record to remember and nothing to ask. That, I think, is why the 1,164 versus 1,220 fight swallows every flaw in both numbers.

The Double 1,164: A Data Autopsy of Ishan Kishan's Record

One last thing, and it cuts against my own argument. What if the record is entirely correct, and the only failure is the reporting? That is completely possible. Most records are true; most reporting carries no proof of them. Column C of my sheet exists precisely for that gap. I have to believe the five-check list sitting inside this story is not a story about one journalist's laziness — it is a story about a profession that never built a shared verification standard. Cricket journalism has no citation norm. The ball moves fast, and the claim moves just as fast.

So the next time a number arrives that supposedly breaks Suryakumar's mark, I have five benchmarks ready, and I would like them to stop being unusual: the match date and year, from an official scorecard; the format scope of the figure — T20I only or all T20 — stated in one clear word; innings and matches alongside strike rate and average; the full ranked list behind every word like "fastest," "most," and "third," hidden rows included; and whether the record still stands, or whether someone restored it the moment the calendar turned. Five benchmarks, three minutes of work.

I am waiting for the day that list stops feeling like a benchmark and starts feeling like ordinary journalism. Until then, a record with no year is a claim and only a claim.

Now I go back to my sheet. The Ishan Kishan row still has Column C empty, and today I have written only one thing in it: "1,164. Twice. Why?"

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