KCKingdom
Fansided

Kansas City Chiefs: Who Will Be The Number Two Receiver

facebooktwitterreddit
Prev
4 of 7
Next

Kansas City Chiefs running back De’Anthony Thomas (13) – Mandatory Credit: Denny Medley-USA TODAY Sports


De’Anthony Thomas

Okay I realize that “That’s what speed do” is totally a Royals thing and blah blah blah, but I couldn’t resist.

De’Anthony Thomas is an unlikely candidate to start along Jeremy Maclin this season. He’s just not the “typical” wide receiver you see starting in the league and that will work against him. Thomas will, however, still see plenty of playing time.

Live Feed

Jonathan Taylor Next Team Odds: 3 Contenders That Make Sense for Star Running Back
Jonathan Taylor Next Team Odds: 3 Contenders That Make Sense for Star Running Back /

Betsided

  • Should the KC Chiefs consider an extension for Harrison Butker? Arrowhead Addict
  • Danny Shelton feels ready to contribute to KC Chiefs title defense Arrowhead Addict
  • NFL Rumors: 5 Jonathan Taylor trade packages Colts can't possibly turn down FanSided
  • Caesars + FanDuel Promos: Back Chiefs in Preseason Week 3, Win $450 Bonus + $100 Off NFL Sunday Ticket! Arrowhead Addict
  • Chiefs Rumors: Pacheco injury, Shane Buechele shoutout, QB prediction FanSided
  • I wasn’t entirely impressed with Thomas last year up until he gunned it down the field on a punt return against the Raiders for a touchdown. Thomas also had his first career touchdown in San Francisco against the 49ers. Now this didn’t count as a wide receiver touchdown since Thomas is actually listed as a running back, but I think they should have given it to us. Just my opinion though.

    Thomas will continue to see time as a slot receiver as well. I’ll be curious if the team drafts Kansas State wideout Tyler Lockett how that’ll affect Thomas’ duties, but there’s a chance one of the 31 other teams in the league could land Lockett.

    Anyway, to my main point, Thomas will not be the starting wide receiver in 2015 unless a lot of injuries occur. Just my take.

    Next: No. Just no.