PF
Getting things ready
Loading player details and market context…
· QB· Age 34
Nick Foles
Trade value 0· 0 30d
KTC 1QB
· Overall #775
Market rank · 2026
KTC SF
· Overall #1379
Market rank · 2026
KTC Redraft
· Overall #573
Market rank · 2026
QB171
QB rank
FantasyPros expert consensus · Overall #681
Lower rank numbers are better.
Player view
Combined overview: current-season rankings, long-term value, recent trade movement, and player news.
Rankings first
Nick Foles fantasy football rankings
Fantasy Red Zone blends the latest available ranking rows for this player into one quick read. Source-specific rows below show the individual rankings behind it.
Fantasy Red Zone ranking
#852
Overall · site avg
QB171
Positional avg
2026
FP
Expert consensus rank
#681
QB171
KTC 1QB
Market rank
#775
Source disagreement
Why sources may differ
Expert/ADP rows and market-value rows are kept separate. KTC now appears in both layers when Dynasty Daddy provides rank fields: first-class market-rank rows plus the underlying trade-value signal for dynasty/market context.
Rank / ADP inputs
4 sources · consensus #852
Spread 806 spots
FP
Expert consensus rank · Approved live
#681
Pos #171
KTC 1QB
Market rank · Internal only
#775
KTC SF
Market rank · Internal only
#1379
KTC Redraft
AI manager read
Today’s fantasy decision signals
Content · trades · market · health
A compact manager-focused read refreshed from Fantasy Red Zone data. Use it as the first pass before asking Water Boy for roster-specific advice.
Manager read
No sharp market, injury, or content signal yet. Treat as a baseline hold until fresh news or trade volume changes.
Action: Hold
Trade values
Compare players inside the same source. Higher number = higher market value.
KeepTradeCut
Dynasty · One-QB
0
Updated 1d ago+0 30d
Dynasty Process
Dynasty · One-QB
0
Updated 1d ago+0 30d
Dynasty Superflex
Dynasty · One-QB
0
Updated 1d ago+0 30d
Recent news & analysis
Source-backed player mentions link to the content receipt, source archive, and original report so injury/news context can flow both ways.
PF
FF
FF