Fastest Century in Ranji Trophy

Rishabh Pant's 48-ball century for Delhi against Jharkhand in 2016–17 is the fastest reliably documented Ranji Trophy hundred in the standard record lists. The balls figure marks when he reached 100, rather than the number of balls in his completed innings.

That qualification matters because Shakti Singh's older hundred has been reported as taking 42 or 45 balls. The count was not established by official scorers, so it should be described as disputed rather than placed above Pant without explanation.

Fastest Documented Ranji Hundreds

Historical balls-faced coverage is not complete, so the table is explicitly limited to documented records.

Pant's Acceleration

Reaching a century in 48 balls means averaging more than two runs per delivery to the milestone. The performance belongs to first-class cricket despite its scoring speed; the format is determined by the match, not by how quickly the batter scores.

Fast innings can help a captain build a target or recover time lost earlier in a game. Their value depends on the match situation, so the balls-to-century record should accompany the opponent and season rather than stand as a context-free number.

The Disputed Shakti Singh Claim

The reported 42- or 45-ball hundred came for Himachal Pradesh against Haryana in 1990–91. Because the ball count was kept by teammates rather than established officially, record summaries commonly retain Pant as the documented benchmark. Readers should see the reason for that distinction.

Pant Finished With 135 From 67 Balls

The record hundred formed part of a completed innings of 135. Pant hit eight fours and thirteen sixes, giving him 110 boundary runs. The remaining 25 runs came through other scoring outcomes credited to him.

His final strike rate was approximately 201.49, calculated from 135 divided by 67 and multiplied by one hundred. That is different from using the forty-eight deliveries required to reach the century.

Attaching “135 from 48 balls” would therefore be inaccurate. The innings continued for another nineteen deliveries after he reached the milestone, and the completed scorecard preserves that additional batting.

He Also Scored a Hundred in the First Innings

Pant made 117 in Delhi's first innings against Jharkhand. The later 135 gave him centuries in both innings and a match aggregate of 252.

Those figures create three separate descriptions: a forty-eight-ball hundred, twin centuries and 252 match runs. None should be substituted for another. The match aggregate is not a double-century innings because the runs were split across two visits to the crease.

BCCI's report records the game at St. Xavier's KCA Cricket Ground in Thiruvananthapuram and states that it ended in a draw, with Jharkhand taking the first-innings lead. The record innings did not produce an outright Delhi win.

Why Balls to the Milestone Matter

A fastest-century list uses the deliveries needed to reach at least 100. A batter can reach the milestone with a boundary that carries the score beyond exactly one hundred, but the record still refers to that delivery count.

Overall strike rate is calculated from the completed innings. It can increase or decrease after the century depending on how the batter continues. That is why fastest-century and highest-strike-rate tables are not identical.

Minutes-based records are another category. Time at the crease can include interruptions and factors unrelated to balls faced, so a fastest hundred by minutes should not be mixed into a balls-based ranking.

Shakti Singh's Claim Needs Its Qualification

Reports of a forty-two- or forty-five-ball hundred describe an earlier Himachal Pradesh innings against Haryana. The difficulty is the provenance of the count: it was reportedly maintained by teammates rather than established by the official scorers.

That uncertainty does not justify pretending the innings never happened. It does justify separating the reported claim from the documented benchmark. Readers should see both the achievement and the reason for the distinction.

A precise-looking number is not automatically a verified number. Historical scoring coverage varies, particularly for delivery-by-delivery milestones.

Do Not Mix Domestic Competitions

V. B. Chandrasekhar's famous fifty-six-ball first-class hundred came in the Irani Cup. Yusuf Pathan's fifty-one-ball Duleep Trophy hundred belongs to that competition. Neither is a Ranji innings simply because it occurred in Indian domestic cricket.

A broader Indian first-class comparison can include those performances with the competition labels visible. A Ranji-only table must retain the narrower filter.

The same applies to T20 centuries. Their format and innings limits differ, and a rapid IPL hundred does not alter the Ranji record.

What a Fast Hundred Can Do for a Match

Rapid scoring can give a captain more time to seek wickets, reduce a deficit or change a chase. Its value depends on the match position rather than speed alone.

Pant's example is especially useful because the record and the result point in different directions: an extraordinary individual innings occurred in a drawn game where the opposition held the first-innings advantage.

A complete account therefore needs the final score, balls to the hundred, opposition and result. Those details explain the performance without turning every fast innings into an assumed match-winning one.

The Two Hundreds Produced Twenty-One Sixes

Pant hit eight sixes in his first-innings 117 and thirteen in his second-innings 135. The combined twenty-one is a match total, not the boundary count in either individual innings.

That distinction is useful when comparing his performance with Agarwal's twenty-six sixes in one innings. Both achievements belong to the first-class record discussion, but they use different units. A fast-century article can include the match total as context while keeping the forty-eight-ball milestone tied specifically to Pant's second innings against Jharkhand.