The NFL season is in full swing. As happens every year, injuries are rearing their ugly heads. As fantasy football managers prepare to set Week 13 lineups, it’s important to stay informed on the latest injury news. Bam Knight was limited at practice this week due to injury. What is his current status and outlook for this week?

Check out the FREE Start/Sit Optimizer from PFSN to ensure you are making the right decisions for your fantasy lineup every week!Check out the FREE Start/Sit Optimizer from PFSN to ensure you are making the right decisions for your fantasy lineup every week!

Is Bam Knight Playing Week 13?

Knight injured his knee during overtime in last week’s game against Jacksonville. The running back left the contest after sustaining the injury, though it remains unclear if he could have returned as the game ended shortly afterward. The timing of the injury made it impossible to assess whether Knight would have been able to continue had the game gone longer.

Knight has been on the injury report for most of the past month, dealing with various ailments throughout the stretch run. He has oscillated between avoiding final injury designations entirely and being listed as questionable, creating uncertainty about his status on a week-to-week basis.

Despite the frequent injury report appearances, Knight has yet to miss a game this season. His durability and ability to play through minor issues has been impressive given the physical nature of his role in Arizona’s backfield.

Knight practiced all three days this week, which represents an encouraging sign for his availability against Tampa Bay. However, he was limited in each session and did not get in a full practice at any point during the week. The consistent limited participation suggests the knee is still bothering him to some degree.

The Cardinals tend to err on the side of caution when it comes to injury designations. The organization frequently lists players as questionable even when they are expected to play, preferring to maintain flexibility rather than ruling anyone in definitively.

The fact that Knight practiced all three days suggests he will play this week. His track record of suiting up despite injury designations and the consistent practice participation throughout the week both point toward him being active Sunday.

Despite being a west coast team, fantasy managers catch a break this week with the Cardinals playing in Tampa. We will know Knight’s status at 11:30 AM EST when inactives are announced, rather than having to wait until the typical 1:00 PM window for west coast home games.

On Saturday night, Adam Schefter reported that Knight is expected to play.

Knight’s Fantasy Football Outlook

Knight will continue starting and technically serving as the lead back despite underwhelming recent performances. He saw 15 opportunities last week against Jacksonville, converting them into just 32 total yards. Without a touchdown salvaging his fantasy day, the output would have been catastrophic for managers desperate enough to deploy him.​

The rushing efficiency hit rock bottom. Knight carried the ball 10 times for a mere 12 yards, averaging 1.2 yards per attempt. He added four catches on five targets for 20 yards through the air, demonstrating his expanded receiving role in passing situations. The touchdown came on a short plunge that provided his only path to fantasy relevance.​

MORE: Free Fantasy Football Start/Sit Optimizer

His snap share has declined precipitously over recent weeks. Knight has failed to reach 50% playing time in three consecutive games. He touches the ball more than his backfield counterparts, but he isn’t on the field as much as his starter designation suggests. This creates a problematic dynamic where volume remains steady but opportunities per snap don’t materialize.​

The Cardinals might make a change given his abysmal production. Arizona has shown zero allegiance to either back, preferring whoever performs better on game day. Knight functions as a touchdown-or-bust RB3 whose fantasy value lives and dies with short-yardage scores. His explosive run rate and yards-after-contact metrics remain among the worst qualified runners.