Cricket

List of Most Runs by a Captain in IPL

A list of IPL captains who have scored the most runs while leading their teams, combining leadership responsibility with batting excellence.

4 itemsUpdated Mar 23, 2026

Leading a T20 franchise while also being the primary run-scorer is one of cricket's most demanding roles. Virat Kohli, who captained RCB from 2012 to 2021, scored 4,994 runs as captain — the all-time IPL record for a captain. Rohit Sharma's 4,000+ runs as MI captain across five title wins is the second-most. MS Dhoni, David Warner, and Gautam Gambhir are the other major run-scorers among IPL captains.

#	Name	Team	Record	Nationality	Runs as captain
1	Virat Kohli — 4,994 Runs as Captain Royal Challengers Bangalore \| All-Time Record Virat Kohli scored 4,994 runs as RCB captain — the all-time IPL record for a captain. He captained RCB from 2012 to 2021, including his record-breaking 973-run season in 2016 as captain.	RCB	Most runs as IPL captain	Indian	4,994
2	Rohit Sharma — 4,000+ Runs as Captain Mumbai Indians \| 5-Time Champion Captain Rohit Sharma scored 4,000+ runs as Mumbai Indians' captain across 5 title-winning campaigns. His runs as captain include many decisive match-winning innings that set the tone for MI's dynasty.	Mumbai Indians	—	Indian	4000+
3	MS Dhoni — 3,500+ Runs as Captain Chennai Super Kings \| 5-Time Champion Captain MS Dhoni scored 3,500+ runs as CSK captain, primarily as a finisher at number 6-7. His runs as captain were more impactful than any statistical measure can capture — many were match-winning contributions in crucial moments.	CSK	—	Indian	3500+
4	David Warner — 3,000+ Runs as Captain Sunrisers Hyderabad \| Orange Cap Leader David Warner scored 3,000+ runs as SRH captain, including his dominant 2016 (848 runs) and 2019 (692 runs) seasons. He led SRH to their only title in 2016 while simultaneously dominating the Orange Cap race.	Sunrisers Hyderabad	—	Australian	3000+

This list is compiled from verified public records and reference sources. Last verified: March 23, 2026.

Found an error? Report it here