IPLStatsIndeed

Top 10: Batters with Most Runs in Losing Cause in IPL History

Every batter wants to contribute to a team’s winning cause by scoring heaps of runs. However, on some occasions, things don’t go as planned, and despite accumulating significant runs, the team might end up on the losing side.

The Indian Premier League (IPL) has seen some of the finest T20 superstars wield their willows for their teams. But they experienced their batting performances going down the drain as the team couldn’t cross the winning line.

In this article, we’ll look at the top 10 batters with the most runs in losing causes in IPL history.

Most Runs in Losing Cause in IPL

PlayerRunsInningsHigh ScoreAvgSR
Virat Kohli3625123113*32.07125.08
Shikhar Dhawan2780107106*27.80120.03
David Warner27671008628.52125.14
Rohit Sharma2660118105* 23.13125.47
Dinesh Karthik245112097*22.69127.39
Robin Uthappa23381067523.14121.58
MS Dhoni223610484*33.37124.63
KL Rahul220965100*36.81126.01
AB de Villiers20349289*23.11134.52
Sanju Samson19958111925.90134.25

Key Insights

Virat Kohli is leading the run chart with over 3500+ runs coming in losing causes for Royal Challengers Bengaluru in the IPL.

20 batters have 1500 or more runs that came in a losing cause in the IPL’s history.

Kohli and David Warner have scored 25 or more fifties that ultimately ended on the losing side for their respective teams. Apart from them, 5 more batters — Shikhar Dhawan, KL Rahul, Manish Pandey, Suresh Raina, and Rohit Sharma — have 15 or more half-centuries in losing causes in the IPL.

Speaking of centuries, Kohli, Hashim Amla, and Sanju Samson have 2 or more hundreds that didn’t materialise in a win for their teams. (Check out Virat Kohli’s IPL centuries here.)

Jacques Kallis has the worst strike rate of 107.31 among the batters with 1000+ runs in losing causes in the IPL. No other batter has a strike rate lower than 110.

Advertisements
Inarticle 80

Kohli, Karthik, Rohit, Dhawan, Uthappa, and Dhoni have been part of 100+ losses in the IPL as individual players.

Leave a Reply

Your email address will not be published. Required fields are marked *