Highest Individual Score in Ranji Trophy

B. B. Nimbalkar's unbeaten 443 for Maharashtra against Kathiawar in 1948–49 remains the highest individual score in the Ranji Trophy. It is the tournament's recognised quadruple-century benchmark and a record distinct from Brian Lara's 501 not out in English county cricket.

Recent batters have moved close to the 400-run mark without reaching it. Prithvi Shaw's 379 for Mumbai against Assam stands ahead of Sanjay Manjrekar's 377, while two Hyderabad batters share the score of 366.

Highest Ranji Trophy Innings

An asterisk means not out. Sridhar and Agarwal are tied on runs, even though their innings came in different seasons and match circumstances.

Nimbalkar's Enduring Benchmark

The first requirement for an innings of this size is staying at the crease. A batter must continue scoring after reaching the usual milestones of a century, double-century and triple-century, while avoiding dismissal across a very long innings.

The table also shows why records should be described precisely. Agarwal's 366 included a record-breaking rate of scoring, but it did not become the highest Ranji innings. Shaw's 379 surpassed Manjrekar's total without overtaking Nimbalkar. Each landmark deserves its own wording.

Ranji and First-Class Records

Every Ranji match in this table is first-class, but not every first-class record was set in the Ranji Trophy. Lara's 501 not out belongs to the wider first-class record book. Nimbalkar's 443 not out is the appropriate answer to a Ranji-specific question.

The Match Behind Nimbalkar's 443 Not Out

The innings came at Poona Club Ground in December 1948. Archival records identify the fixture as Maharashtra against Kathiawar and record Maharashtra winning by concession. That result explains why the story cannot be treated as an ordinary drawn match after a large declaration.

At the end of the first day, Nimbalkar was 24 not out. By the next close he had reached 301 not out, with Maharashtra on 587/2. His eventual 443 therefore developed across successive stages rather than arriving as a single uninterrupted day's score.

He shared a 455-run second-wicket partnership with K. V. Bhandarkar, who made 205. Another stand of 242 with S. D. Deodhar helped carry the innings further. Those partnerships explain how the team supported an individual record that required extended time at the crease.

Why the Asterisk Is Part of the Record

Nimbalkar was not dismissed. The asterisk after 443 preserves that fact and distinguishes his innings from another batter finishing on the same score after losing a wicket. It should not disappear when the record is shortened for a headline or table.

Being unbeaten does not mean additional runs can be estimated or credited. The record remains 443, regardless of what might have happened had play continued. Historical discussion can describe the circumstances, but the official score stops where the scorecard stops.

The same principle applies to declarations. A batter on 300 not out does not receive an assumed 350 because the captain ended the innings. Records use completed recorded performances, not projected outcomes.

Shaw's 379 and Manjrekar's 377

Prithvi Shaw's 379 moved him above Sanjay Manjrekar's 377 in the Ranji innings list. The two scores are separated by only two runs, yet each belongs to a different Mumbai generation and match context.

Shaw's innings came against Assam in 2022–23. Manjrekar made his 377 against Hyderabad in 1990–91, when the team was still officially named Bombay. Using the historical name in a scorecard table avoids creating the impression that Bombay and Mumbai represent unrelated record books.

Neither innings passed 400. Nimbalkar's lead over Shaw is 64 runs, leaving a clear gap between the top score and the next listed performance despite the enormous totals involved.

Two Scores of 366, Different Stories

M. V. Sridhar's 366 was part of Hyderabad's 944/6 declared against Andhra in 1993–94. The team innings became a record in its own right, linking his individual contribution to the tournament's highest total.

Tanmay Agarwal also finished on 366, but his innings against Arunachal Pradesh in 2023–24 was distinguished by speed and boundary hitting. He reached 300 in 147 balls and struck 26 sixes across the completed innings.

Their equal run totals therefore produce a tie in a highest-score table, not an identical cricketing achievement. Balls faced, opponent and match situation provide the details that the shared score cannot.

Highest Score, Fastest Score and Match Aggregate

The highest innings is ranked by runs. The fastest century or triple-century is ranked by the deliveries required to reach the milestone, where reliable ball counts exist. A match aggregate adds the batter's two innings.

A player scoring 220 and 225 would have 445 match runs but no individual innings above 225. Such a performance would belong in a match-total discussion, not above Nimbalkar in the highest-innings table.

For a reliable answer, retain the full combination of batter, score, team, opponent and season. That makes it possible to distinguish a tournament record from a wider first-class record, and a single innings from a two-innings aggregate.

Maharashtra and Mumbai Are Separate Teams

Nimbalkar represented Maharashtra, while Shaw represented Mumbai in his 379-run innings. Their shared state geography does not make the performances records for the same association. The Ranji field contains several distinct regional cricket bodies within some states.

That distinction also matters for Manjrekar's Bombay innings. Bombay and Mumbai are treated together across the name change, but Maharashtra remains a separate team. A table identifying only the city or state loosely can therefore assign an innings to the wrong record book. Retaining the scorecard's team name resolves the issue without changing any of the individual scores.