WR · BAL
injury
Rashod Bateman — Active
Sleeper status change for Rashod Bateman (7571). Before: status=Active, injury_status=Questionable. After: status=Active, injury_status=
Rashod Bateman
WR · BAL · 26 yrs · exp 5 · Minnesota
Status
- Game status
- Active
Keep Trade Cut (SF TEP)
From latest snapshot · trend vs ~7d prior when data allows.
Value
2,062
Rank
#278
Pos rank
#100
7d trend
—
Value history (90d)
One snapshot point per calendar day (shown in your timezone).
Latest: May 22, 2026 · 2,062
News
Stories linked to this player — newest first.
analyst
Is Ja'Kobi Lane the Pass-Catching Answer the Ravens Have Been Seeking?
Rookie WR Ja'Kobi Lane could step into a significant role for the Ravens in 2026, potentially starting opposite Zay Flowers. The team has lacked a consistent No. 2 receiver, and Lane's size and red-zone ability make him an attractive option for Lamar Jackson, especially after Isaiah Likely's departure
general
Jesse Minter on Diego Pavia: Show us what you can do
The Ravens have given Diego Pavia a chance
WR · BAL
analyst
Rashod Bateman a Cut Candidate in All Dynasty Leagues?
Baltimore Ravens wide receiver Rashod Bateman has been extremely underwhelming in fantasy football throughout his five-year career. Despite having high draft capital as a former first-round pick, Bateman has never finished higher than WR40 in fantasy football. He has finished as WR69 or worse in four of his five pro seasons. Most recently, in 2025, Bateman was held to just 19 catches, 224 yards, and two touchdowns. Sure, he missed four games due to injury, but the per-game averages are still putrid. Plus, fantasy managers don't want receivers who struggle to produce and can't stay healthy. The only good news about Bateman's situation is that the Ravens made a coaching change this offseason, replacing John Harbaugh with Jesse Minter. Still, there's not enough optimism behind Minter to justify getting back on board the Bateman hype train. After five years of disappointment, managers can drop Bateman in all dynasty leagues
You're caught up — end of feed.
Data comes from cached Sleeper and KTC snapshots. Values update when the sync jobs run.