Washington WR John Ross Sets NFL Combine Record in 40-Yard Dash

The story of Saturday at the Combine was speed

Washington wide receiver John Ross set a NFL Scouting Combine record by running an official 4.22 40-yard dash on Saturday afternoon, which overtook running back Chris Johnson's previous record of 4.24, which was set in 2008.

"When I got there, everything kind of got quiet. I had so much adrenaline," Ross told ESPN's Josina Anderson. "I was nervous right before I went, so I was up on my hands. Everything got quiet; I couldn't hear anything. And I just took off. I held my breath ... and it just went on from there."

Ross didn't run a second attempt because he said he "cramped up," but when the NFL came back and confirmed his official record-setting run, history had already been made.

Johnson took to social media to let people know he was watching.

Ross, who is considered a first-round prospect, had 81 receptions for 1,150 yards with 17 touchdowns last season for Washington.

Here's part of the NFL.com scouting report on Ross:

"Ross is an instant-impact weapon who scored 23 touchdowns in just 112 touches. He should be able to step right in as a kick returner and a slot receiver, but teams with speed at tight end might utilize him outside to create extreme vertical stress on opposing safeties. If his knees check out as healthy, Ross is a likely first-round pick with the rare ability to become a high-volume slot receiver or a lesser-targeted, high-yield deep-ball threat."

It wasn't just speed at the receiver position on Saturday as the tight ends also showed out in a big way.

With last year's fifth-round pick Tyreek Hill already proven to be the fastest player in the NFL on the field last year with a top speed of 22.77 miles per hour, the question becomes what would a receiver's group look like that had both Ross and Hill together?

Fast, that's what. Really, really fast.

Tyreek Hill hit 22.77 mph during this return, the fastest speed of any player in the NFL this season. #TouchdownTuesday #KCvsATL pic.twitter.com/GQ5SJW8l6O — Kansas City Chiefs (@Chiefs) November 30, 2016

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.

Related Content

Advertising