The Highest Test Scores, With the Records Kept Separate

Brian Lara holds the record for the highest individual score in a men’s Test innings: 400 not out, against England at St John’s, Antigua, in April 2004. If “highest Test match runs” means a batter’s combined runs across both innings of one match, the answer is Graham Gooch’s 456: 333 plus 123 against India at Lord’s in 1990. These are separate records, not competing entries in the same ranking.

For runs accumulated across a whole career, use our men’s Test career run leaders.

Choose runs or scoring pace to compare the top ten innings; expand a batter’s name for match details.

The Ten Highest Individual Men’s Test Innings

Lara’s 400* leads Cricinfo’s men’s Test high-score records, checked on 3 October 2026. The list below ranks individual innings by runs scored. It does not add together a batter’s two innings, rank career totals, or include domestic first-class cricket and other international formats.

These are ten innings, not ten different players. Lara appears twice: his unbeaten 400 and his earlier 375 are separate performances, each entitled to its own position. Removing repeat players would produce a different list and would no longer show the ten highest scores.

Lara and Sobers represented West Indies; Hayden represented Australia. Jayawardene and Jayasuriya represented Sri Lanka, Mulder South Africa, Hutton and Hammond England, and Hanif Pakistan.

An asterisk means not out, not an extra run or an adjustment to the score. Lara’s 400* ranks above Hayden’s 380 because Lara scored more runs. The ranking would be unchanged if the asterisk were removed from the display, although that would lose information about how the innings ended.

The comparison tool also retains the available balls-faced figures from the record table: 582 for Lara’s 400*, 437 for Hayden, 538 for Lara’s 375, 572 for Jayawardene, 334 for Mulder, 847 for Hutton and 578 for Jayasuriya. The table does not supply balls faced for Sobers, Hanif or Hammond. Their missing values are shown as dashes, not zeros.

Lara’s 400* Is a Personal Innings Total

Lara faced 582 balls, hit 43 fours and four sixes, and batted for 778 minutes. West Indies declared at 751/5 with him unbeaten. England then made 285 and, following on, 422/5; the match was drawn. These details are recorded in the archived match scorecard.

The distinction between 400* and 751/5 is fundamental. The first number is Lara’s contribution with the bat in that innings. The second is West Indies’ team total, with five wickets lost. A team score includes the contributions of other batters and extras; it is not interchangeable with an individual record.

Nor is 400* a batting average. An innings score describes one performance. A batting average relates accumulated runs to dismissals over a selected set of innings. The unbeaten status matters when calculating batting average, because a not-out innings adds runs without adding a dismissal to the denominator.

For this high-score table, however, dismissal status does not change the ordering. All runs count at their face value. An unbeaten score does not receive a bonus, and a dismissed batter’s score is not discounted.

The declaration also defines the limit of the recorded performance. Lara finished on 400; the record does not credit runs he might have made had West Indies continued batting. “Not out” describes the scorecard outcome, not a projection of an eventual total.

The drawn result is another separate fact. Lara holds the innings record regardless of whether West Indies won. The score establishes how many runs he made; the match result describes what the teams achieved. Neither should be substituted for the other when interpreting the record.

Gooch’s 456 Adds Two Innings Together

Graham Gooch’s 456 against India at Lord’s in 1990 is the highest individual match aggregate in men’s Tests. His record listing identifies the combined total: 333 in one innings and 123 in the other.

That is why 456 does not appear above Lara’s 400* in the innings table. Gooch did not make 456 in a single innings. Adding his two scores answers the match-total question, whereas Lara’s entry answers the single-innings question.

The arithmetic is straightforward, but the unit being counted changes the record: an individual match aggregate is the batter’s first-innings runs plus second-innings runs in that match. It is not the sum of the team’s scores, and it is not the batter’s cumulative total across a series.

A batter need not have two substantial scores for a match aggregate to be large. Nevertheless, the definition allows both innings to contribute, so it gives a different opportunity to accumulate runs from a single-innings ranking. Comparing 456 directly with 400 without identifying those units obscures the achievement each number measures.

Use the two-innings match record when the question is who scored most across one complete Test. Use this table when the question is who made the largest individual innings. Career-run rankings require a third dataset covering all of a player’s Tests.

Mulder’s 367* Shows How Declarations Limit the List

Wiaan Mulder made 367 not out from 334 balls against Zimbabwe at Bulawayo in July 2025. South Africa declared at 626/5, leaving him fifth on this innings list rather than allowing him to continue towards Lara’s score.

The ICC’s account of Mulder’s decision records why he chose not to pursue the record. At 367, he was 33 runs short of equalling 400 and 34 short of breaking it. South Africa ultimately won by an innings and 236 runs, as shown in the match scorecard.

Those gaps distinguish matching a record from taking sole possession of it. Reaching the same number would produce a tie on runs; exceeding it would establish a higher score. The asterisk would not change either threshold.

Mulder’s innings also shows why this ranking is an observed-results table, not a ceiling on batting ability. His recorded total is 367*. There is no defensible score to enter for an innings that continued beyond the declaration, because those deliveries and runs never occurred.

Declarations affect opportunities to build exceptionally large scores. They can end an unbeaten innings while a batter still has time, partners or momentum. The record table preserves the outcome but does not quantify those unused opportunities.

Lara and Mulder both finished unbeaten, yet their teams stopped at different individual and team totals. That shared asterisk does not establish that their situations were equivalent. The scorecards and the declaration decision supply context that the runs column alone cannot.

Hanif’s 337 Was a Different Batting Assignment

Hanif Mohammad’s 337 against West Indies at Bridgetown in 1958 came after Pakistan were dismissed for 106, replying to West Indies’ 579/9 declared. Pakistan followed on with a 473-run deficit. Hanif occupied the crease for 970 minutes in a six-day Test that ended in a draw, according to the match scorecard.

His ninth-place score therefore arose from a different task from building a dominant first-innings total. Pakistan were batting again after a large deficit, and occupying time was part of the match situation. The score of 337 measures his runs, but does not by itself describe the pressure under which those runs were made.

Minutes and balls faced must also remain separate. The record table supplies no balls-faced figure for Hanif. His 970 minutes cannot be substituted into a strike-rate calculation, which requires deliveries faced rather than elapsed time.

That missing figure prevents a complete scoring-pace comparison across all ten entries. It does not make Hanif’s innings unrankable by runs: his score is known, so its place in the high-score list is clear. Missing evidence limits only the comparisons that depend on it.

This is the central distinction between a record ranking and an assessment of an innings. The ranking has one fixed measure. An assessment needs the match situation, opposition, conditions, available time and era alongside that measure.

Scoring Pace Is a Separate Comparison

Lara’s record innings had a batting strike rate of 68.73 runs per 100 balls, rounded to two decimal places. The calculation is: batting strike rate = 400 ÷ 582 × 100 = 68.73.

The tool applies the same calculation to the other entries with known balls faced. Switching from runs to scoring pace changes the ordering because it changes the question. Runs identify the largest innings; strike rate identifies the fastest accumulation per delivery among the entries with sufficient data.

Mulder leads that available-data pace comparison at 109.88 runs per 100 balls, calculated from 367 runs and 334 balls. That does not make him the highest scorer: he remains fifth when the list is ordered by runs. Nor does it establish a record for the fastest innings across all Test cricket, because the tool contains only these ten high scores.

A pace comparison must retain all three missing balls-faced values. Treating a missing denominator as zero would produce an invalid calculation; treating it as a guessed number would manufacture evidence. Sobers, Hanif and Hammond therefore remain marked as unavailable in the pace view rather than receiving invented rates.

Strike rate also does not adjust for opposition strength, pitch conditions or match purpose. A quicker innings and a longer innings can represent different demands. The calculation describes scoring speed, not difficulty, quality or the value of the performance to the team.

The Ranking Establishes Size, Not Greatness

The table supports a precise verdict: Lara’s 400* is the highest individual men’s Test innings in the cited records, while Gooch’s 456 is the highest individual total across a single match. Keeping those definitions separate resolves the ambiguity in “highest Test match runs.”

Beyond that verdict, the numbers need context. Lara’s record came in a draw; Mulder’s unbeaten innings ended with a declaration in a match South Africa won by an innings; Hanif’s score came while following on. These outcomes and circumstances are not adjustments to the runs. They are reasons not to treat a runs-only ranking as a list of the greatest innings.

Read each entry as a documented score with a defined scope. Use runs to compare size, known balls faced to compare pace, and the scorecard to understand the assignment. None of those measures replaces the others.