
Nick Foles: Latest News, Rumors and Speculation on QB's Future with Rams
Quarterback Nick Foles is a candidate to be traded or cut by the Los Angeles Rams after a disappointing 2015 season and with the Rams trading up for the No. 1 pick in the 2016 NFL draft.
Continue for updates.
TOP NEWS
.jpg)
Colts Release Kenny Moore

Projecting Every NFL Team's Starting Lineup 🔮

Rookie WRs Who Will Outplay Their Draft Value 📈
Rams Have Target Date for Foles Trade
Monday, June 6
Bleacher Report's Jason Cole reported that the Rams hope to trade Foles before the start of the regular season:
Foles Linked to Jets
Monday, June 6
Cole reported on Monday that the New York Jets have not yet inquired about trading for Foles as they continue to negotiate a contract with Ryan Fitzpatrick.
The Huffington Post's Jordan Schultz reported on April 30 that the Rams were discussing a trade with the Jets.
Trade Market Reportedly Nonexistent for Foles
Wednesday, June 1
Nick Wagoner of ESPN reported the Rams "have been unable to find a taker for Foles on trade market." Wagoner noted that keeping Foles on the roster "offers insurance against injury" and could lead to a possible trade in the future.
Fisher Comments on Foles' Absence from OTAs
Wednesday, June 1
"I've had conversations with Nick, we're on the same page and we're trying to work things out, that's all I can say," head coach Jeff Fisher told reporters, according to NFL Network's Patrick Claybon.
Foles Missing from Training Sessions
Wednesday, June 1
ESPN.com's Jim Trotter, citing multiple sources, reported that "Foles, a regular when offseason workouts began April 18, has not participated in a team-run training session since the Rams took [Jared Goff] first overall. The fifth-year pro even skipped the start of organized team activities on Tuesday."
Multiple Teams Considering Foles
Monday, April 25
ESPN's Adam Schefter, citing a source, reported that "several teams [are] interested" in Foles and that where he winds up is among the storylines to track during draft week.
Buzz Building That Foles Won't Be a Ram in 2016
Sunday, April 10
Foles could be "the odd man out" on the Rams' depth chart at the position, according to a report from Mike Florio of ProFootballTalk.
"One source with knowledge of the dynamics already has predicted that Foles likely will be gone by the start of training camp, and that he definitely will not be on the team before Week 1," according to the report.
Florio also noted that Foles appears to have fallen behind Case Keenum and Sean Mannion on the quarterback depth chart, just a year after being traded to the Rams in the deal that sent Sam Bradford to the Philadelphia Eagles.
Rams Trading Foles Would Make Sense
Trading Foles would be more appealing than simply cutting him, however, since his $1.75 million base salary for 2016 is fully guaranteed.
He has also already received a $6 million roster bonus for the upcoming season, so cutting him now would represent a pretty big financial commitment from the team without getting a thing in return.
Whether a market will ever develop for his services is quite another factor entirely. After a breakout 2013 season with the Eagles (2,891 passing yards, 27 touchdowns and just two interceptions in 13 games), Foles has struggled mightily in his last two seasons and lost his starting gig with the Rams last year.
| 2014 | Eagles | 8 | 2,163 | 13 | 10 | 59.8 |
| 2015 | Rams | 11 | 2,052 | 7 | 10 | 56.4 |
Those numbers don't exactly scream "NFL starter."
So if a team does strike a deal for Foles, it may be under the assumption that he'll be a backup quarterback and not the starter, which will severely limit the compensation the Rams would receive in return.
But the issue with that mentality is that Foles is due $10.75 million in 2017, a pretty sizable cap hit for a backup.
Either way you slice it, teams will likely be wary of paying a substantial price for Foles in a deal. Nonetheless, any compensation the Rams receive would still be superior to cutting the quarterback and gaining nothing in the process.
You can follow Timothy Rapp on Twitter.

.png)





