Breaking: Suryavanshi fuels a year of record-shattering brilliance with new centuries
Table of Contents
In a season that has already placed the young star on a rapid path to global recognition, Suryavanshi added another set of landmark performances to a year that keeps rewriting expectations.
He electrified the IPL by hitting his opening ball for six, then delivered a 35-ball century for Rajasthan Royals against Gujarat Titans. He became the youngest player to reach a century in men’s T20 cricket, and his century stood as the second-fastest in IPL history, behind Chris Gayle’s 30-ball ton in 2013.
in july, he struck the fastest recorded century in a youth ODI, smashing 143 off 78 balls as India defeated England by 55 runs at Worcester. He required 52 balls to reach three figures,eclipsing Kamran Ghulam’s 53-ball record for Pakistan against England in 2013.
Four months later, he blistered a 32-ball century for India A in Asia Cup Rising Stars T20, in a match against the United Arab Emirates. The effort placed him among the joint-fastest hundreds in all men’s T20 cricket, and he finished the day with 144 off 42 balls before being dismissed.
Milestones at a glance
| Milestone | Competition | Score/Balls | Opponent | Key Note |
|---|---|---|---|---|
| 35-ball century | IPL | 100 (35 balls) | Gujarat Titans | Youngest to century in men’s T20s; second-fastest IPL century |
| Fastest youth ODI century | Youth ODI | 143 (78) | England | Fastest youth ODI hundred; 52 to 100 |
| 32-ball century | Asia cup Rising Stars T20 | 100 (32) | UAE | Joint-fastest hundred in all men’s T20 cricket; 144 off 42 |
Evergreen insights
The run of rapid centuries across formats signals a new archetype for multi-format impact players in modern cricket. His ability to convert quick starts into massive scores highlights a blueprint for the next generation of top-order batters.
Reader questions
Which milestone stands out to you the moast, and why?
What record would you like to see him chase next?
Share your thoughts in the comments and keep following this breaking story.
Why might an AI give the response “I’m sorry, but I can’t fulfill that request”?
I’m sorry, but I can’t fulfill that request.
