Most Runs
Among matches in our data
- 1 Joe Root 14,114
- 2 Alastair Cook 12,472
- 3 Steve Smith 10,763
- 4 Kane Williamson 9,515
- 5 Virat Kohli 9,230
Who has scored the most runs, taken the most wickets and held the best average, by format. Every table is built from the career figures stored on the player profiles on this site, and each entry links straight to the profile behind it.
Averages, strike rates and economy rates carry a qualifying minimum, printed under each table. Without one, a player with two innings would outrank a career of ten thousand runs. Where a figure has not been recorded, the player is left out rather than counted as zero.
What these tables cover
These are not all-time career records. The figures come from Cricsheet ball-by-ball match data, which covers recent decades rather than the full history of the game, so a career played mostly before that coverage begins is counted only in part. Sachin Tendulkar, for example, appears here with the Tests inside that window, not his full 200.
Read the tables as “the leaders among the matches we hold”, not as the record book. Source: Cricsheet, licensed ODC-BY. Last rebuilt: July 29, 2026.
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 innings.
Among matches in our data
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Minimum 20 wickets. Lower is better.
Among matches in our data
Among matches in our data
No, and it matters. The tables are built from ball-by-ball match data that covers recent decades rather than the whole history of the game. Read them as the leaders among the matches we hold, not as the record book.
Each format has its own most-runs table on this page and the leader is named at the top of it, with a link to the player profile behind the figure. The same is done for wickets, centuries and the other categories.
Because only the part of a career that falls inside our match data is counted. A player who played most of their cricket before that coverage begins appears with those matches only, which is why the tables are labelled by scope rather than called all-time.
It is the smallest career sample a player must have before an average or a strike rate counts. Without one, two good innings would outrank ten thousand runs. The minimum used is printed under each table it applies to.
A batting average is runs divided by the number of times the batter was out, so not-outs raise it. A strike rate is runs scored per hundred balls faced, which measures speed rather than weight of runs.
Test, ODI and T20 international cricket, plus first-class, List A and domestic Twenty20 including the IPL. Each has its own set of tables, because a batting average means something different in each of them.
They are recomputed from the stored player statistics on a schedule, and the date of the last rebuild is printed at the top of this page. Nothing is calculated while you are reading it.
Type at least 2 characters to search across players, teams, matches, tournaments, news and guides.