Tamil Nadu Ranji Trophy Records: Titles and Batting Milestones

Tamil Nadu have two Ranji Trophy championships, including the 1954–55 victory under the Madras name and the 1987–88 title. Historical naming matters here: omitting Madras would understate the side's championship record.

The team also produced one of the tournament's largest innings, 912/6 declared against Goa in 1988–89. That total remains a central part of Tamil Nadu's Ranji batting history.

Tamil Nadu's Major Milestones

The 900-Plus Innings

Tamil Nadu's 912/6 was a declared innings, meaning the side closed its batting before losing all ten wickets. It sits below Hyderabad's 944/6 declared in the leading historical team totals.

Large innings create an opportunity, but they do not explain the result by themselves. A records article should retain the score and declaration status without assuming that every 900-plus total produced an outright victory.

Bowling and Batting Careers

Venkataraghavan's 530 Ranji wickets place him behind Rajinder Goel in the recognised career wickets comparison. His tournament tally should remain separate from his Test and overall first-class totals.

Badrinath's 7,850 Ranji runs are a tournament career figure across the teams he represented. They are useful when discussing a prominent Tamil Nadu player, but should not be described as runs exclusively for Tamil Nadu without a team-specific filter.

Historical Names and Current Records

Madras and Tamil Nadu refer to the team's earlier and later names for championship counting. That straightforward continuity differs from more complex predecessor-association cases elsewhere in the tournament, where a counting convention needs explanation.

Madras's Title Is Part of the Same Record

The 1954–55 championship was won under the Madras name. The later Tamil Nadu name should not cause that title to disappear from the association's total, which stands at two alongside 1987–88.

Historical scorecards retain the name used at the time. A modern team overview can explain the continuity while leaving the original match labels intact. This makes the history easier to follow without rewriting archival records.

The same care is needed with opponents. Mysore appears in older records where modern readers may expect Karnataka, but a scorecard's historical label remains useful evidence of its period.

The 912/6 Declared Against Goa

Tamil Nadu's 1988–89 total passed 900 with only six wickets lost. The declaration means the captain voluntarily ended the innings before all ten wickets fell.

Hyderabad later reached 944/6 declared, exceeding Tamil Nadu's total by 32. Holkar's earlier 912/8 declared shares the same run total as Tamil Nadu but differs in wickets lost and historical setting.

A highest-score ranking focuses on runs. The declaration and wickets provide context; they do not turn the two 912-run innings into different numerical totals. The score should always retain its full notation to avoid suggesting the side was all out.

Vijay and Mukund's Opening Stand

Murali Vijay and Abhinav Mukund added 462 for the first wicket against Maharashtra in 2008–09. Vijay made 243 and Mukund 300 not out in the innings, producing one of the tournament's outstanding opening partnerships.

The stand finished two runs short of Delhi's 464-run benchmark. It remains a major Tamil Nadu record without being described as the highest opening partnership in the entire competition.

Their completed individual scores add to more than the partnership because the surviving opener continued after the first wicket. Partnership totals include the team's runs during the pair's time together, not simply both final personal scores.

Venkataraghavan's Place in the Wickets List

Venkataraghavan's 530 Ranji wickets sit behind Goel's 637 in the recognised historical comparison. The difference of 107 shows the scale of Goel's lead while preserving Venkataraghavan's substantial domestic record.

His Test career and wider first-class figures belong to other statistical scopes. A profile can display all of them, but a Tamil Nadu Ranji page should identify which total it is discussing.

The distinction is particularly important with five-wicket hauls and bowling averages, where a career summary can easily mix tournament and overall figures. The competition filter must remain consistent across every column.

The 2014–15 Final Shows a Different Side of the History

Tamil Nadu reached that final against Karnataka but lost by an innings and 217 runs. Their first innings of 134 was followed by Karnataka's 762, built around Karun Nair's 328.

Tamil Nadu then made 411, a stronger second effort that still left their combined 545 below Karnataka's single innings. The calculation explains the margin: 762 minus 545 equals 217.

A final appearance belongs in the team's competitive history, but it is not another championship. This is why the title total remains separate from lists of finals reached.

Badrinath's Runs Need a Team Filter

Badrinath's 7,850 Ranji runs span the associations he represented. His importance to Tamil Nadu does not make all later appearances part of a Tamil Nadu-only aggregate.

A team history can discuss his complete career while clearly labelling the number. A record table claiming runs specifically for Tamil Nadu requires the corresponding team-level dataset.

Reading the Team's Achievements Together

Two titles, a 900-plus innings, a 462-run opening stand and Venkataraghavan's career wickets describe different strengths and periods. They should remain separate records rather than being forced into one measure of success.

That approach also avoids confusing Tamil Nadu's Ranji history with the Tamil Nadu Premier League, a different T20 competition. The state connection is shared, but the formats, teams and records are not interchangeable.

Two Competitions Share a State Connection

The Tamil Nadu Premier League is a T20 franchise competition, while Tamil Nadu's Ranji team plays first-class association cricket. A TNPL hundred or wicket does not enter these Ranji totals. The shared regional connection can help fans discover players, but the statistical records remain separate.