10
Loading video...
By Michael Gallagher
Sports Content Coordinator
0
Share
Newsweek is a Trust Project member
See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.
The Green Bay Packers were dealt quite the scare during Sunday’s game against the New York Jets when star receiver Jayden Reed went down with what looked like a spinal injury.
Speculation on social media was that Reed possibly damaged his spinal cord after colliding with Jets linebacker Demario Davis and falling limp to the ground.
He was stretchered off and taken to the hospital for further evaluation, and the Packers announced some good news about Reed’s condition that had fans breathing a little easier.
Read More on NFL
“Update: WR Jayden Reed has feeling and movement in all extremities. He will stay overnight for further testing and observation,” the Packers announced on X.
On Monday, ESPN’s Adam Schefter reported that Reed will undergo more testing to determine his prognosis, but all signs seem to be pointing toward his injury not being the kind of career-threatener that it was initially feared to be.
“Packers WR Jayden Reed injured his back Sunday, per source,” Schefter added. “After spending the night in New Jersey, he soon will be returning to Green Bay, with the team still evaluating the best treatment and recovery time frame.”
...
Part of the reason the Packers let Romeo Doubs walk in free agency and traded Dontayvion Wicks to the Philadelphia Eagles is because of the team’s young, budding wide receiver corps led by Reed, Christian Watson, and Matthew Golden.
Now the burden falls on Watson, who’s dealt with his own injury struggles over the years, and Golden, who hasn’t quite carved out a role for himself in Green Bay’s offense, to carry the passing game until Reed returns.
Through two games, Watson and Golden are tied for the team lead with 10 catches apiece, and they’re separated by just 35 receiving yards. Watson also leads the Packers with three touchdown catches.
View 0 Comments
Submit Correction
View Editorial & AI Guidelines