Did Jacob Bethell Make History as the Second Youngest to Score an Ashes Century in the 21st Century?
Synopsis
Key Takeaways
Sydney, Jan 7 (NationPress) Jacob Bethell, a 22-year-old cricketer from England, made his mark in the record books by achieving a remarkable century during the final Test of the Ashes series at the Sydney Cricket Ground on Wednesday. This feat places him as the second youngest player to score a century in this historic rivalry.
Bethell stepped into the No. 3 batting position, taking over from seasoned player Ollie Pope, who faced difficulties in the current tour. Upon his arrival at the crease in England's second innings, the team had already lost opener Zak Crawley on the fifth ball and trailed Australia by 179 runs.
He began with an 81-run partnership alongside Ben Duckett, who scored 39 runs before being dismissed in the 20th over. Following the quick exit of Joe Root, Bethell built a strong 100-run partnership with vice-captain Harry Brook.
Bethell reached his first Test century off 162 balls, celebrating the achievement with a slog over wide long-on. At just 22 years and 78 days, he became the second-youngest player to record an Ashes hundred in the 21st century, following in the footsteps of former England captain Alastair Cook, who did so at the age of 21 in 2006.
This century marked the first Ashes hundred by an England No. 3 in 14 years, since Jonathan Trott. Since 2001, only Michael Vaughan and Mark Butcher have also achieved centuries while batting in the No. 3 position during the Ashes series.
Having played five Tests, Bethell has amassed 312 runs at an average of 34.66 over 10 innings, in addition to scoring 1,172 runs in first-class cricket.
However, England faced a significant setback on Day 4's first session as captain and all-rounder Ben Stokes left the field early due to a right adductor issue. Stokes bowled just 10 deliveries at the beginning of Wednesday's play before experiencing discomfort in his right groin, leaving the field during the 28th over of Australia’s second innings. The team later confirmed that he was dealing with an adductor concern.
While he did come out to bat in the second innings, scoring just a run off five balls before being dismissed, it remains uncertain if he will bowl again in the match as the hosts pursue their final target.