Week 1 route rate leaders - ROOKIE WRs 97% - Denzel Boston (CLE) 92% - Carnell Tate (TEN) 87% - Caleb Douglas (MIA) 85% - Makai Lemon (PHI) 83% - Ted Hurst III (TB) 73% - Bryce Lance (NO) 65% - KC Concepcion (CLE) 62% - Malachi Fields (NYG) 55% - Ja'Kobi Lane (BAL) (80% rate before injury) 54% - Chris Bell (MIA) 39% - De'Zhaun Stribling (SF) (69% before injury) 38% - Kevin Coleman Jr. (MIA) 29% - Antonio Williams (MIA) 28% - Josh Cameron (JAX) 26% - Brenen Thompson (LAC) 23% - Zachariah Branc...

Insight page Source View post on X

NegativeInjurySep 14, 2026Baltimore Beatdown

Lane was sidelined after 27 snaps with a wrist injury; his first NFL touchdown catch was called back due to a penalty, limiting his Week 1 impact and creating depth chart uncertainty.

Insight page Source Original

NegativeInjurySep 14, 2026Yahoo Sports NFL

Lane was sidelined after 27 snaps with a wrist injury. His first NFL touchdown catch was called back due to a penalty, and he did not return to the game, creating depth chart uncertainty at wide receiver.

Insight page Source Original

NegativeInjurySep 14, 2026Yahoo Sports NFL

Ja'Kobi Lane, the Ravens' rookie standout wide receiver, was ruled out of Week 1 with a wrist injury. NFL Media's Mike Garafolo reported that the early diagnosis was a wrist fracture, which could cause the Southern California product to miss additional time beyond Week 1.

Insight page Source Original

PositiveInjurySep 14, 2026Baltimore Beatdown

The rookie tight end is set to miss time with a wrist injury, creating uncertainty around his availability and role in the Ravens' offense. His absence opens opportunities for other pass-catchers like Chris Moore and impacts the target distribution in the passing game.

Insight page Source Original

NegativeInjurySep 14, 2026Baltimore Beatdown

Ja'Kobi Lane had one 11-yard catch before leaving the game early with a wrist injury in Week 1. Lane would have had his first career touchdown reception, but it was called back due to a holding penalty.

Insight page Source Original

NegativeInjurySep 14, 2026Yahoo Sports NFL

Ja'Kobi Lane had one 11-yard catch before leaving the game early with a wrist injury. He would have had his first career touchdown reception, but it was called back due to a holding penalty, limiting his impact in Week 1.

Insight page Source Original

NegativeInjurySep 14, 2026FantasyPros Articles

Promising Ravens rookie Ja'Kobi Lane sustained what appeared to be a significant wrist injury in Week 1 and is expected to miss some time. He was a worthwhile dart throw in drafts, but it's not worth waiting for him to return given the scarcity of bench spots.

Insight page Source Original

NegativeInjurySep 14, 2026FFin60

Ja'Kobi Lane possibly suffered a fractured wrist in Week 1, creating uncertainty around his availability going forward.

Insight page Source Original

NegativeInjurySep 14, 2026Fantasy Life Articles

Rookie WR Ja'Kobi Lane was getting peppered in the red zone during Week 1 but left the game early with a wrist injury, limiting his opportunity to establish fantasy viability despite early offensive involvement.

Insight page Source Original

NegativeInjurySep 14, 2026Yahoo Sports NFL

Rookie receiver Ja'Kobi Lane missed the second half of the Ravens' 41-23 win over the Colts with a wrist injury.

Insight page Source Original

PositiveInjurySep 14, 2026Fantasy Life Articles

Lane impressed in his first NFL action as the Ravens' planned No. 2 option behind Zay Flowers, but left early with a wrist injury later announced as a fracture that will cost him several weeks. He finished with 1 catch for 11 yards on 3 targets and had a TD called back due to penalty. The source views him as a great stash with major upside down the stretch and recommends picking him up only if you have an IR spot.

Insight page Source Original

NegativeInjurySep 14, 2026Yahoo Sports NFL

Lane was injured in Week 1, further limiting the Ravens' passing game depth alongside Zay Flowers' hamstring injury. His absence reduces upside cases for the Ravens' pass offense and supports the team's shift toward a run-first identity.

Insight page Source Original