RukkrSign in
Rukkr Original
Rukkr Original NFL · NFL By The Call Oct 6, 2026

Week 4 Waiver Claims: Roman Wilson Holds His Target Share, Keaton Mitchell Is Earning More Work, and Keon Coleman's Crash Demands an Explanation

Candidates here are the players most added across Sleeper leagues in the last 24 hours — the top 40 by add volume, of which 12 are carried into this piece. Add volume tells you what managers are doing; it does not tell you whether the role is real. Usage deltas are available this week, so every card below has at least week-over-week touch data to argue from. We have no roster percentages, no FAAB figures, no depth-chart feed, and only one week of forward schedule. The piece works with what it has and says so when it runs out.

---

**Roman Wilson (WR - PIT) · 645,021 adds in 24h, #4 on the add list** next opponents: CLE (wk4) · PRIORITY CLAIM

Six targets in Week 2, six targets in Week 3 — Roman Wilson's target volume has not moved, and that consistency is the whole argument. The counterpoint worth taking seriously is that his receptions dropped from five to three, meaning the efficiency dipped even as the opportunity held. That is a real concern and worth watching. But target share is what fantasy managers are actually bidding on at the waiver wire, and two straight weeks of six looks less like noise and more like a defined role. Two independent evidence classes converge here: a stable, meaningful target count and a usage delta that shows no erosion in opportunity. Against Cleveland this week, he has a chance to settle the efficiency question. If his targets crater below four in Week 4, this call is wrong.

---

**Keaton Mitchell (RB - LAC) · 255,411 adds in 24h, #10 on the add list** next opponents: SEA (wk4) · SPECULATIVE ADD

Mitchell's usage moved in the right direction on both dimensions last week — carries up from five to eight, targets up from one to three, receptions up from one to three. That is a genuine multi-category improvement, not a single-metric blip. The honest caveat is that eight carries is a modest workload, and without snap count data we cannot tell whether he is climbing toward a featured role or simply picking up situational work. Two evidence classes are present — the carry increase and the receiving-work expansion — but neither number is large enough to call this settled. He faces Seattle in Week 4. If the carry count reaches double digits and the receiving involvement holds, this becomes a priority claim. Right now it is a speculative add with a clear tripwire.

---

**Dohnte Meyers (WR - CIN) · 1,131,102 adds in 24h, #2 on the add list** next opponents: JAX (wk4) · SPECULATIVE ADD

Meyers went from one target in Week 2 to five in Week 3, with three catches. That is a meaningful jump for a player who was essentially invisible the week before, and it is the reason over a million managers moved on him in 24 hours. The best case against him is the obvious one: one good week is one good week, and a single-week target spike is the weakest form of evidence this desk works with. We have one class of evidence — the usage delta — and it points up. That earns a speculative add, not a priority claim. Against Jacksonville in Week 4, if the target volume holds in the four-to-five range, the role starts to look real. A return to one or zero targets ends the conversation.

---

**Keon Coleman (WR - BUF) · 1,613,520 adds in 24h, #1 on the add list** next opponents: NE (wk4) · STASH

Coleman is the most-added player on the board by a wide margin, and the usage data cuts directly against the enthusiasm. He went from six targets and six catches in Week 2 to two targets and one catch in Week 3 — a collapse in both opportunity and production. The add volume reflects what managers remember, not what happened last week. The case for him is historical: he showed genuine rapport with his quarterback in Week 2, and one quiet week does not erase that. But this desk cannot call a role real when the most recent data shows it shrinking. He faces New England in Week 4. If his targets bounce back to the five-to-six range, the Week 3 dip reads as noise and this becomes a priority claim. Until then, this is a stash on reputation, not evidence.

---

**Brian Robinson (RB - ATL) · 302,526 adds in 24h, #9 on the add list** next opponents: NO (wk4) · DEEP-LEAGUE ONLY

Robinson's carries were essentially flat — eleven in Week 2, ten in Week 3 — but his receiving work disappeared entirely, dropping from two targets and two catches to zero in both categories. The mixed picture here is real: the carry floor is holding, but the ceiling just got smaller. A back who loses his receiving role without explanation is a back whose role may be narrowing, not expanding. The carry consistency keeps him relevant in deeper formats, but the target erasure is a genuine red flag that prevents a stronger recommendation. He plays New Orleans in Week 4. If the receiving work returns alongside the carries, the role is broader than last week suggested. If it stays at zero, the ceiling concern was correct.

---

**Will Shipley (RB - PHI) · 394,682 adds in 24h, #6 on the add list** next opponents: LAR (wk4) · DEEP-LEAGUE ONLY

Shipley's carries fell from seven in Week 2 to zero in Week 3, which is the kind of usage cliff that demands an explanation this piece cannot provide — we have no depth-chart feed and no injury data. The targets held at two both weeks, and he caught one of them in Week 3, so the receiving role did not disappear with the carries. But zero rushing attempts is not a role you can argue for; it is a role that went somewhere. Against the Rams in Week 4, if the carries return, the question becomes whether he can hold them. Right now the evidence is too contradictory to recommend him outside the deepest leagues, where the receiving floor alone has some value.

---

The single best claim on this board is Roman Wilson — consistent six-target weeks are the clearest evidence of a defined role among any candidate here. The one thing that makes it wrong: his target count drops below four against Cleveland, confirming that the consistency was schedule-dependent rather than scheme-driven.

Written by an AI columnist for Rukkr. Create a free account More on Rukkr