Across 1,169 IPL matches and 13,801 dismissals between 2008 and 2025, exactly 1,153 batters have been run out — and the rate at which it happens has fallen by nearly two-thirds. In the league's first season, 12.3% of every wicket that fell was a run-out. In 2025, that number was 4.5%. No other mode of dismissal in IPL history has changed this dramatically, and almost nobody talks about it.
The run-out is cricket's only self-inflicted wound. Nobody beats you. Nobody finds the edge. You simply run out of ground, and the scorecard records it without a bowler's name attached. On 21 May 2008 at the Wankhede Stadium, Mumbai Indians chased 189 against Kings XI Punjab and lost by one run — because three of their last four wickets were run-outs, all inside the final over. That single over is the entire story of this dismissal in miniature: desperation, a converted single that wasn't there, and a margin measured in one run.
The Dismissal That Is Disappearing
Run-outs account for 8.4% of all IPL dismissals across the full ball-by-ball record. That places them third — behind caught (62.8%) and bowled (17.0%), ahead of lbw (6.2%), caught-and-bowled (2.8%) and stumped (2.7%). But the aggregate hides the trend completely.
2008–2016: the scrambling era
The league's first nine seasons averaged well above one run-out per match. The 2010 season remains the high-water mark: 93 run-outs in 60 matches, a rate of 1.55 per game and 12.9% of all dismissals. Boundary riders were slower, direct hits were rarer, and batters were still importing 50-over running habits into a 20-over format where the two runs you steal in the 14th over rarely decide anything.
The 2016 season produced a late spike — 74 run-outs at 11.1% of dismissals — but it was the last time the number would climb. Everything after 2017 moves in one direction.
2019 onwards: the collapse
The 2019 season broke the pattern hard: 42 run-outs in 60 matches, 6.1% of dismissals, a rate of 0.70 per game. That was a 40% single-season fall from 2016. Six seasons later, the 2025 edition set the all-time low on every measure — 39 run-outs across 74 matches, 0.53 per match, and just 4.5% of all wickets.
Put plainly: an IPL match in 2010 was roughly three times more likely to feature a run-out than an IPL match in 2025.
Why the decline is real, not noise
Three forces compound here. Fielding standards rose — franchise fielding coaches, dedicated throwing programmes and a generation raised on the format have made the direct hit an expectation rather than an event, which paradoxically deters the risky single before it is attempted. Second, batting strategy shifted from rotation to boundary-hitting; a team hunting 220 takes fewer twos than a team hunting 160, and a ball not run is a ball you cannot be run out on. Third, the Impact Player rule from 2023 deepened batting orders, reducing the number of tail-enders scrambling in the final over.
The one place the run-out has refused to die is exactly where it was born.
Where Run-Outs Actually Happen
The distribution across a 20-over innings is violently lopsided. Of the 1,153 run-outs in the record, 621 — 53.9% — occurred in the death overs (16–20). The middle overs contributed 338 (29.3%) and the powerplay only 194 (16.8%).
Zoom in further and it gets starker. The 20th over alone produced 322 run-outs. That is 27.9% of every run-out in IPL history, generated in 5% of the deliveries. The 19th over produced 113; the 18th, 80. The final over of an innings is roughly three times more lethal than the one before it.
Of those 322 final-over run-outs, 143 came on the sixth legal delivery or later — the last-gasp scramble for a second run, or a bye off the keeper, with the innings already over in every sense but the arithmetic.
There is also a near-even split in who pays. The striker was the batter dismissed 606 times (52.6%); the non-striker 547 times (47.4%). Almost half of all run-outs punish the player who did not face the ball.
The Data Deep-Dive
Every dismissal type in IPL history (2008–2025)
| Dismissal | Count | Share |
|---|---|---|
| Caught | 8,665 | 62.8% |
| Bowled | 2,345 | 17.0% |
| Run out | 1,153 | 8.4% |
| LBW | 853 | 6.2% |
| Caught and bowled | 388 | 2.8% |
| Stumped | 376 | 2.7% |
| Hit wicket | 18 | 0.1% |
| Obstructing the field | 3 | 0.0% |
The season-by-season decline
| Season | Matches | Run-outs | Per match | % of dismissals |
|---|---|---|---|---|
| 2008 | 58 | 85 | 1.47 | 12.3% |
| 2009 | 57 | 76 | 1.33 | 10.9% |
| 2010 | 60 | 93 | 1.55 | 12.9% |
| 2011 | 73 | 74 | 1.01 | 9.1% |
| 2012 | 74 | 85 | 1.15 | 9.9% |
| 2013 | 76 | 79 | 1.04 | 8.7% |
| 2014 | 60 | 67 | 1.12 | 10.0% |
| 2015 | 59 | 64 | 1.08 | 9.3% |
| 2016 | 60 | 74 | 1.23 | 11.1% |
| 2017 | 59 | 58 | 0.98 | 8.2% |
| 2018 | 60 | 58 | 0.97 | 8.1% |
| 2019 | 60 | 42 | 0.70 | 6.1% |
| 2020 | 60 | 45 | 0.75 | 6.6% |
| 2021 | 60 | 46 | 0.77 | 6.4% |
| 2022 | 74 | 61 | 0.82 | 6.7% |
| 2023 | 74 | 55 | 0.74 | 6.0% |
| 2024 | 71 | 52 | 0.73 | 5.9% |
| 2025 | 74 | 39 | 0.53 | 4.5% |
The executioners — most run-outs effected
Cricsheet credits a fielder on 972 of the 1,153 run-outs; the remaining 181 carry no fielder attribution in the source data, so these totals are floors rather than absolutes.
| Fielder | Run-outs effected |
|---|---|
| MS Dhoni | 27 |
| Ravindra Jadeja | 20 |
| Virat Kohli | 18 |
| Sanju Samson | 17 |
| Dinesh Karthik | 17 |
| Suresh Raina | 13 |
| AB de Villiers | 13 |
| Manish Pandey | 13 |
| Wriddhiman Saha | 12 |
| Dwayne Bravo | 12 |
Dhoni's 27 is the outright record and it is not close. What makes it remarkable is that a wicketkeeper is credited for the collection-and-break, meaning his tally is largely composed of moments where somebody else threw and he finished the job faster than the batter could finish the run.
The victims — most times run out
| Batter | Times run out |
|---|---|
| Shikhar Dhawan | 16 |
| Gautam Gambhir | 16 |
| Suresh Raina | 15 |
| Dinesh Karthik | 15 |
| Ambati Rayudu | 15 |
| AB de Villiers | 14 |
| Faf du Plessis | 12 |
| Murali Vijay | 12 |
| Yusuf Pathan | 11 |
| Rohit Sharma | 11 |
Note the overlap. Raina, Karthik and de Villiers appear on both lists — the same aggressive running instinct that lets you effect run-outs in the field is the instinct that gets you run out at the crease.
Franchise ledgers — effected minus conceded
Records below merge franchise renames (Delhi Daredevils into Delhi Capitals, Kings XI Punjab into Punjab Kings, Royal Challengers Bangalore into Bengaluru).
| Franchise | Effected | Conceded | Net |
|---|---|---|---|
| Delhi Capitals | 158 | 141 | +17 |
| Chennai Super Kings | 122 | 105 | +17 |
| Mumbai Indians | 137 | 128 | +9 |
| Sunrisers Hyderabad | 95 | 86 | +9 |
| Kolkata Knight Riders | 134 | 131 | +3 |
| Gujarat Titans | 23 | 22 | +1 |
| Rajasthan Royals | 121 | 123 | −2 |
| Royal Challengers Bengaluru | 129 | 131 | −2 |
| Lucknow Super Giants | 17 | 22 | −5 |
| Punjab Kings | 112 | 139 | −27 |
Punjab's −27 is the worst running record in league history by a distance — 139 wickets surrendered without a bowler earning them.
Venues — where the stumps get hit
| Venue | Run-outs | Matches | Per match |
|---|---|---|---|
| Arun Jaitley Stadium, Delhi | 114 | 97 | 1.18 |
| Rajiv Gandhi International Stadium, Hyderabad | 92 | 83 | 1.11 |
| M Chinnaswamy Stadium, Bengaluru | 104 | 99 | 1.05 |
| Eden Gardens, Kolkata | 105 | 100 | 1.05 |
| Sawai Mansingh Stadium, Jaipur | 65 | 64 | 1.02 |
| MA Chidambaram Stadium, Chennai | 91 | 91 | 1.00 |
| Narendra Modi Stadium, Ahmedabad | 44 | 45 | 0.98 |
| PCA Stadium, Mohali | 55 | 61 | 0.90 |
| Wankhede Stadium, Mumbai | 101 | 125 | 0.81 |
Delhi's ground leads at 1.18 run-outs per match — slower outfields historically meant more twos attempted, and more twos attempted means more twos declined a fraction too late.
The five-run-out matches
Only five matches in IPL history have produced five run-outs:
- Mumbai Indians vs Kings XI Punjab, Wankhede Stadium, 21 May 2008 — Punjab won by 1 run
- Royal Challengers Bangalore vs Delhi Daredevils, M Chinnaswamy Stadium, 25 March 2010 — Delhi won by 17 runs
- Delhi Daredevils vs Chennai Super Kings, Feroz Shah Kotla, 10 April 2012 — Delhi won by 8 wickets
- Kolkata Knight Riders vs Kings XI Punjab, Eden Gardens, 4 May 2016 — Kolkata won by 7 runs
- Gujarat Lions vs Mumbai Indians, Rajkot, 29 April 2017 — tied, decided in a Super Over
Four of those five were decided by 17 runs or fewer. The Rajkot match of 2017 finished with Mumbai's last three wickets all run out — two of them by Jadeja in the 20th over — with the scores level on 153.
Legacy Impact — What the Run-Out Ledger Means Now
The run-out has quietly become a specialist event rather than a routine one, and that reframes how the final over should be read. When a modern IPL innings reaches the 20th over, the historical base rate says a run-out is the single most likely non-boundary catastrophe available to the batting side — 322 of them in that over alone, against a league-wide decline everywhere else on the card. Teams have optimised away the middle-over single without optimising away the death-over scramble, because the death-over scramble is not a choice. It is what the arithmetic forces.
That has direct competitive consequences. Royal Challengers Bengaluru won back-to-back titles in 2025 and 2026, closing out the latter with a five-wicket win over Gujarat Titans at the Narendra Modi Stadium on 31 May 2026 — a chase completed with two overs to spare, which is precisely the profile of a side that never had to gamble on a second run. The franchises carrying negative run-out ledgers, Punjab most of all, have historically been the ones forced into last-over improvisation because they arrived at the 18th over behind the required rate.
CricMind's Oracle treats this asymmetry as a live input rather than trivia. The Micro layer — the per-ball state machine that recalculates win probability after every delivery — weights a death-over wicket far more heavily than an identical wicket in the eighth over, and a run-out specifically carries a compounding penalty because it usually removes a set batter without costing the bowling side a single scoring ball. The historical distribution above is what calibrates that penalty.
For a fielding side, the strategic read is narrow but clear: the marginal value of a specialist boundary fielder is concentrated almost entirely in overs 16 to 20, where 53.9% of all run-outs live. For a batting side, the read is that the second run in the 19th and 20th overs has been, across eighteen seasons, the most expensive unit of currency in the competition.
Three Takeaways
- The run-out is vanishing. From 12.3% of dismissals in 2008 to 4.5% in 2025 — a 63% relative decline driven by better fielding, boundary-first batting and deeper orders under the Impact Player rule.
- It has concentrated, not spread. Over half of all run-outs (53.9%) occur in overs 16–20, and the 20th over alone accounts for 27.9% of the all-time total from 5% of the deliveries.
- Running is a team skill with a permanent ledger. Punjab's −27 net across eighteen seasons and Delhi's and Chennai's +17 are not noise; they reflect durable differences in how franchises value the second run.
Frequently Asked Questions
How many run-outs have there been in IPL history?
There have been 1,153 run-outs across 1,169 IPL matches from 2008 to 2025, out of 13,801 total dismissals — 8.4% of all wickets. That makes it the third-most-common mode of dismissal after caught and bowled.
Who has effected the most run-outs in the IPL?
MS Dhoni, with 27 run-outs credited to him in the ball-by-ball record — comfortably the most in league history. Ravindra Jadeja follows on 20, then Virat Kohli on 18, with Sanju Samson and Dinesh Karthik tied on 17.
Which batter has been run out most often in the IPL?
Shikhar Dhawan and Gautam Gambhir share the record at 16 dismissals each. Suresh Raina, Dinesh Karthik and Ambati Rayudu are next on 15.
In which over do most IPL run-outs happen?
The 20th over, by an enormous margin — 322 run-outs, or 27.9% of the all-time total. The 19th over produces 113 and the 18th produces 80. The death overs (16–20) collectively account for 621 run-outs, 53.9% of every run-out in IPL history.
Which IPL team has the worst run-out record?
Punjab Kings, including their Kings XI Punjab era, with a net of −27: 112 run-outs effected against 139 conceded. Delhi Capitals and Chennai Super Kings lead the other way at +17 apiece.
Has any IPL match had more than five run-outs?
No. Five is the maximum, achieved in five separate matches: MI vs Kings XI Punjab (2008), RCB vs Delhi Daredevils (2010), Delhi Daredevils vs CSK (2012), KKR vs Kings XI Punjab (2016) and Gujarat Lions vs MI (2017).
Is the striker or the non-striker run out more often?
It is close to an even split. The striker has been dismissed 606 times (52.6%) and the non-striker 547 times (47.4%) — meaning nearly half of all run-outs punish the batter who did not face the delivery.