Most Sixes in a Ranji Trophy Innings

Tanmay Agarwal hit 26 sixes for Hyderabad against Arunachal Pradesh in 2023–24, setting the recognised Ranji Trophy innings benchmark. He finished with 366, an innings that also included the fastest recorded triple-century in first-class cricket at the time.

The sixes total belongs to one innings. It should not be presented as the highest career tally or the most across an entire season; those require different datasets.

Tanmay Agarwal's Record Innings

Those sixes contributed 156 runs, or about 42.6% of his innings total. The calculation shows how much of the scoring came from clearing the boundary, without overlooking the runs made in other ways.

Why the Innings Stood Out

First-class batting usually asks players to manage the new ball, changes in bowling and long periods at the crease. Agarwal combined an enormous score with repeated boundary clearing. Reaching a triple-century so quickly made the innings unusual in both size and tempo.

The Plate setting remains relevant context. Arunachal Pradesh were Hyderabad's opponents, and the performance should be described with that fact intact. It is still a recognised Ranji innings; the division explains the setting rather than changing the score.

Comparing Six-Hitting Records

A match aggregate adds a player's sixes across both innings. A season aggregate adds every eligible innings in that campaign. A career tally covers all Ranji appearances. None can be compared directly with Agarwal's 26 unless the heading states which category is being measured.

A Boundary Breakdown of the 366

Agarwal's completed innings contained 34 fours as well as 26 sixes. The fours contributed 136 runs, and the sixes 156, giving a combined boundary contribution of 292. The remaining 74 runs came through other scoring outcomes credited to the batter.

That means approximately 79.8 percent of his runs came from fours and sixes. The figure describes his personal innings, not Hyderabad's entire team score. Extras belong to the team total and must not be added to a batter's boundary contribution.

He faced 181 balls for his 366, producing a strike rate of approximately 202.21. In other words, he scored just over two runs per delivery faced across a very large first-class innings. The scale makes the rate particularly striking.

The Triple-Century Milestone Came Earlier

Agarwal reached 300 from 147 balls. His eventual 181-ball innings included the deliveries faced after that milestone, so the two ball counts should never be substituted for one another.

Reports from the first day recorded him unbeaten on 323 from 160 balls. He resumed and extended the innings to 366, adding to the sixes tally before being dismissed. A first-day report and the final scorecard can therefore display different correct numbers because they describe different stages.

This is a common source of record errors. An overnight boundary count may be copied as the completed total, or a milestone ball count may be attached to the final score. Both mistakes disappear when the innings timeline is preserved.

How the Sixes Record Changed

The earlier first-class benchmark was Colin Munro's 23 sixes for Auckland against Central Districts in 2015. Agarwal went beyond it with 26. Munro's performance belongs in the wider first-class comparison, not in a Ranji-only table.

The distinction gives Agarwal's achievement two relevant descriptions. It was a Ranji innings record, and it surpassed the existing first-class innings sixes benchmark at the time. Those claims have different scopes even though they refer to the same performance.

A current all-time world-record claim needs a fresh check for subsequent performances. The historical statement that Agarwal broke the benchmark in January 2024 remains valid regardless of what later players do.

Hyderabad's Team Position

Hyderabad declared at 615/5 in 59.3 overs. In cricket notation, 59.3 means 59 overs and three balls, not 59.3 decimal overs. That is 357 legal deliveries for the team innings.

The 366 contributed about 59.5 percent of Hyderabad's total. Other batters and extras supplied the remainder, so the innings was dominant without accounting for every run on the scoreboard.

The opposition and division should remain visible: this was a Plate fixture against Arunachal Pradesh. A scorecard record does not require pretending that all attacks offer identical challenges. Readers can recognise the achievement while understanding its competitive setting.

Sixes Are Only One Part of Batting Value

A batter can produce a decisive Ranji innings without clearing the boundary at all. Protecting wickets, rotating strike and building partnerships can matter more than six-hitting in particular conditions. The sixes record measures a specific skill outcome rather than overall batting quality.

Even within an attacking innings, a boundary total does not reveal the exact shot selection. Claiming that all the sixes came from straight drives, sweeps or pulls would require delivery-level evidence. The scorecard alone establishes the count.

For comparisons, specify whether the question concerns one innings, both innings of a match, a season or a career. Agarwal's 26 directly answers the first question. It should not be stretched into a career leaderboard that the available evidence does not establish.

The Twenty-Six Were in One Innings

Pant's twenty-one sixes against Jharkhand in 2016–17 came across two innings, with eight in the first and thirteen in the second. That match aggregate is a different category from Agarwal's twenty-six in one innings.

A table comparing the two can still be useful, provided it makes the units visible. It would be misleading to label Pant's twenty-one as a single-innings return or to assume Agarwal needed two innings to build his total. The record's scale is already clear from the completed scorecard: twenty-six boundary clearances contributed 156 runs within the same 366-run innings.

Team sixes are another total again. Other Hyderabad batters' hits must not be added to Agarwal's personal count.