The List of Bowlers Who Dismiss Rohit Sharma Most in ODIs: Two New Balls and a Missing Denominator
**मुख्य उत्तर**: रोहित शर्मा को वनडे में सबसे ज़्यादा आउट करने वाली सूचियाँ कच्ची गिनती दिखाती हैं, प्रति आउट गेंदों की संख्या नहीं। अक्टूबर 2011 से लागू दो नई गेंदों का नियम और पावरप्ले के फ़ील्डिंग नियम नई गेंद के गेंदबाज़ों को ज़्यादा मौक़े देते हैं, इसलिए यह क्रम आंशिक रूप से कैलेंडर का नतीजा है, कौशल का फ़ैसला नहीं। **मुख्य तथ्य**: - रोहित शर्मा ने 13 नवंबर 2014 को ईडन गार्डन्स, कोलकाता में श्रीलंका के ख़िलाफ़ 264 रन बनाए, जो वनडे का सर्वोच्च स्कोर है। - रोहित शर्मा के नाम तीन वनडे दोहरे शतक हैं; एक से ज़्यादा दोहरे शतक वाले वे एकमात्र बल्लेबाज़ हैं। - अक्टूबर 2011 से वनडे में दोनों छोरों से एक-एक नई गेंद इस्तेमाल होती है, जिससे ओपनर को ग्यारहवें ओवर में भी ताज़ा गेंद मिलती है। - पावरप्ले यानी ओवर 1 से 10 में सर्कल के बाहर सिर्फ़ दो फ़ील्डर खड़े हो सकते हैं। - रोहित शर्मा 2013 से ओपनर बने; 2007 से 2012 की मिडल-ऑर्डर आउट-गिनती अलग संदर्भ की है। - सूची में स्रोत, कट-ऑफ़ तारीख़ और प्रति-गेंदबाज़ गेंदों की संख्या नहीं दी गई; सभी आँकड़े सत्यापन बाक़ी हैं। **स्रोत श्रेय**: आधार सामग्री का स्रोत-क्षेत्र खाली है और प्रकाशन तिथि उपलब्ध नहीं; आँकड़े ईएसपीएनक्रिकइन्फ़ो स्टैट्सगुरु से सत्यापन बाक़ी हैं। | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर**: प्रश्न: क्या टिम साउदी रोहित शर्मा के लिए सबसे बड़ा ख़तरा हैं? उत्तर: दिशा तकनीकी रूप से संगत है, पर हरकत-गुणांक के बिना यह दावा सत्यापन बाक़ी है; cricsultan.com Player Depth Index पर मैचअप दर देखें। प्रश्न: इस सूची का सबसे बड़ा तकनीकी दोष क्या है? उत्तर: प्रति आउट गेंदों की गिनती न देना, जिससे मौक़े और क़ाबिलियत एक ही संख्या में मिल जाते हैं। प्रश्न: क्या यह डेटा फ़ैंटेसी क्रिकेट के लिए उपयोगी है? उत्तर: हाँ, गेंदबाज़ बनाम बल्लेबाज़ की दर फ़ैंटेसी चयन का मूल इनपुट है, पर केवल स्रोत-सत्यापित आँकड़े इस्तेमाल करें।
Eden Gardens, Kolkata, November 2026. I had the scorecard open on the press-box desk and Rohit Sharma had just finished making 264 against Sri Lanka — the highest score in the history of ODI cricket. Only one line on that card mattered that evening: 173 balls, 33 fours, 9 sixes. Nothing has gone past it since. Three ODI double centuries, a mark no other batter in the world owns.
This week a different list landed on my desk. The bowlers who have dismissed Rohit Sharma most often in ODIs. It has names. It has counts. Tim Southee is there, a cluster of South African seamers is there, a spinner or two is there. What it does not have is the number that would make any of it mean something: how many balls Rohit actually faced against each of those bowlers, how many innings, how many in the powerplay, how many away from home. The denominator is missing.
The ledger never lies, but it often whispers — and on this list it is whispering so softly that nobody can hear it. So I reopened the file.
Context: the rule first, the story second
You cannot read a single name on this list without understanding what the 50-over format has been since October 2026. Two new balls, one from each end. An opener does not merely face a hard ball in the first over; he faces a hard ball again in the eleventh, from the other end, because the ball used at that end is still new. Add the powerplay — overs one to ten, two fielders allowed outside the circle — and you have the hardest ball, the fastest air and the emptiest outfield arriving together against the same man.
Rohit became an opener in 2026. Before that, from 2026 to 2026, he batted in the middle order: lower, against spin, after the ball had softened. Any list that quietly folds those years into one tally is measuring two different batters on one line item.
The third thing the list never mentions is the Future Tours Programme. India play New Zealand, Australia, South Africa and Sri Lanka in bilateral series almost every cycle. A new-ball seamer like Southee gets more looks at Rohit than almost any bowler alive. A bowler from Afghanistan or Zimbabwe could be twice as dangerous and would never climb this table, because the fixture list never granted him the exposure. Opportunity and effectiveness are two separate ledgers, and this list keeps only one of them.
Core: a count is not a capability
This is a photograph of the calendar, not of the cricketer. The correct normalisation for any most-dismissals claim is balls per dismissal. A bowler who has played India twenty-five times and dismissed Rohit six times is not weaker than one who has played six times and dismissed him three. But in raw counts, the bigger name always belongs to the man who played more. Hiding that is not a data problem. It is an editing decision.
Second: where do the dismissals happen? Rohit's ODI innings profile looks bimodal — either a powerplay dismissal to the new ball, or a forty-plus score converted at a high strike rate into something large. The list captures only the lower mode, and therefore misprices the whole asset. A batter whose scoring distribution is fat-tailed in both directions cannot be judged from the bottom tail alone, when the top tail holds three double centuries.
Third: venue. South African and New Zealand pitches offer bounce and seam. A success rate extracted without separating home, away and neutral is as incomplete as a home record quoted without saying the man batted at Mohali every time. Southee's record may well have been built in New Zealand air; the problem is the list never tells you how many of those dismissals happened in it.

Fourth, and entirely absent from the article: DRS. Since LBW became reviewable, the marginal new-ball appeal that once died as not out now converts with far more certainty. A modern seamer's tally will look marginally fuller than a pre-review contemporary's at identical skill. A list with no cut-off date conceals that drift silently.
Fifth, spin. Spinners are mentioned, but it is plausible the names are wrist-spinners bowling in the powerplay rather than finger-spinners holding a line in the middle overs. If so, the spin entries are also part of the new-ball story, and the headline is still about seam.
Technically, the claim is not wrong. A high-backlift, bottom-hand-dominant opener who scores heavily through the leg side stands exposed to the ball leaving him, the ball climbing above the splice, and the left-arm angle across the right-hander. Southee's name and the South African seam cohort fit that profile precisely. But technical coherence across two or three names is not a verdict. Troubled him a lot is a judgement dressed as a statistic, and judgements are dangerously easy to repeat.
Contrarian: correlation is not causation
The fact that Southee dismissed him more often does not mean Southee owns him. Fixture density, pitch type and the risk profile of a high-variance opener are three ordinary explanations that require no special insight at all. India's middle order is deep enough that an early opener's dismissal costs less than this list implies. The expected-value calculation is straightforward: with seven batters behind him, carrying an aggressive opener is rational, not a problem to be solved.
And here I have to argue against my own reflex. After thirty years, I still distrust the obvious odds — but that habit is itself a trap, and the standing rule exists for days like this. When the sober reading turns out to be right, the file has to be allowed to close in the boring direction. New-ball movement genuinely troubles Rohit; twenty overs watched with the numbers shut say so, and the data agrees. This is not a column that needs a reversal. The fault is not in the names on the list. It is in the missing arithmetic beside them.
The real story sits one layer down anyway. The dataset behind this list — ball-by-ball, bowler-versus-batter — is the most valuable raw material the sport owns. Broadcast graphics packages, the fantasy selection market, tour previews: all of it runs on that feed. Yet the piece that carried the list to me names no source, states no cut-off date and supplies no denominator. The expensive asset sits upstream and is nearly free to consume; the cheap packaging captures the traffic. I went back to the source — every ticket, every note, every error — and the counts are still parked in the pending-verification column.
Takeaway: what to watch in the next round
If this list is telling us anything true, it will show up in the next ten overs, not in the next article. Three signals. First, Rohit's powerplay dismissal rate from 2026 onward, expressed as balls per dismissal, not as raw counts. Second, how India's fixtures against New Zealand, South Africa and Australia cluster in the FTP — every cluster will mechanically inflate any future version of this table. Third, his availability: the fewer bilateral ODIs he plays, the faster the arithmetic shifts without a single change in skill.
The question is not which bowler has Rohit's number. The question is which measure we use to decide — the count, or the movement? The ledger never lies, but it often whispers. And when someone shows us only the raw count and hides the movement, that is not a lie. It is a misstatement. Against misstatements I have exactly one remedy: reopen the file.

