/>

Root quickest to 6,000 Test runs in terms of time

Root got to the landmark in five years and 231 days of his Test career, surpassing former England captain Alastair Cook's mark of five years and 339 days.

Published : Aug 01, 2018 19:51 IST

Joe Root raises his bat after hitting a fifty on Day one of the first Test against India.
Joe Root raises his bat after hitting a fifty on Day one of the first Test against India.
lightbox-info

Joe Root raises his bat after hitting a fifty on Day one of the first Test against India.

England captain Joe Root became the quickest batsman to 6,000 Test runs in terms of time from his debut when he reached the landmark on the first day of the series opener against India at Edgbaston on Wednesday.

A streaky four off spinner Ravichandran Ashwin saw the 27-year-old Root, in his 127th Test innings, to the 40 runs he had needed to reach 6,000.

It meant Root, who won the toss, had got to the landmark in five years and 231 days of his Test career, surpassing former England captain Alastair Cook's mark of five years and 339 days.

It is perhaps unsurprising that two England batsmen are at the top of this list given how much Test cricket their side plays, with Wednesday's match their 1,000th fixture at this level.

To put Root's achievement into perspective, Donald Bradman remains the quickest batsman to 6,000 Test runs in terms of innings, the Australia great needing just 68 knocks to achieve the feat.

Yet such were the infrequency of Test matches, then played by far fewer countries, it took Bradman more than 19 years to appear in the 45 Tests that yielded those 68 innings.

Sign in to unlock all user benefits
  • Get notified on top games and events
  • Save stories to read later
  • Access to comment on every story
  • Sign up / manage to our newsletters with a single click
  • Get notified by email for early bird access to discounts & offers to our products
Sign in

Comments

Comments have to be in English, and in full sentences. They cannot be abusive or personal. Please abide to our community guidelines for posting your comment