
Minnesota Vikings
30-10 win over the Green Bay Packers
by TheLuky
Sometimes you apparently have to take a step back to move forward again. The Vikings brought back Kirk Cousins – and suddenly things look like NFL football offensively again.
207 passing yards, two touchdowns, and an interception aren't numbers that make the fantasy world go wild. But that's not what this is about. Minnesota didn't need a quarterback who tears the league apart every week, but one who can guide this offense down the field sensibly. Among other things, Cousins converted a third-and-23 into a touchdown. Overall, they went eight-for-16 on third downs – after going zero-for-eight the previous week. I think that difference speaks for itself.
Above all, their own elite defense finally didn't have to constantly ensure on its own that this team even had a fighting chance. More than 35 minutes of time of possession for the offense also means: catching your breath on the sidelines instead of having to take the field again after the next quick three-and-out by your teammates. And a slightly more rested Brian Flores defense isn't exactly what an opposing quarterback hopes to see. Jordan Love found that out firsthand with eight sacks.
This happened against none other than the Packers, who had put up 45 points against New England just a week earlier. Minnesota kept their division rival firmly in check.
For me, that is precisely what makes the Vikings the winner of the week: the defense was already there. If the offense can now contribute its part on a regular basis, this team becomes seriously dangerous. Who would have thought the answer to that would once again be Kirk Cousins?

New York Giants
21-24 loss to the Washington Commanders
by MatB
Looking at Week 10 as a whole, my loser of the (week) season would be the Baltimore Ravens – but we've already had them twice in this category, and I don't think we need them here anymore; after gifting the Chargers their first win of the season, the Ravens' season is done.
So I decided to go with the New York Giants and the age-old question: does anyone actually want to win the NFC East?
You're right, of course, we could ask the same question about the NFC South.
Yet with the Giants, I keep asking myself: how can you let your division rivals back into the game like that? The table was set:
at home against the Washington Commanders
the Eagles were on a bye
the Cowboys had to play the 49ers at home
Today we know the Cowboys lost their shootout against the 49ers. With a win over the Commanders, the Giants could have taken a massive step toward the division title.
Yes, could have – because what the Giants did was partly – well, let's call it – "not smart."
The Commanders arrived with no running game, no top receiver, and a defense that is average at best; you'd think you could bring them down at home – you'd think, but in the NFL no game is easy, let alone a divisional clash. The Giants may have taken this game a bit too lightly.
How else can you explain losing a game where you have more passing yards, more rushing yards, and thus more total yards, as well as more first downs?
Obviously, purely because of your own mistakes. Too many 3rd downs allowed, too many turnovers – three fumbles, one of them lost, and an interception. The defense picking off two passes didn't help either.
For me, however, penalties were the deciding factor. Six penalties for 62 yards lost – that's more than a field's length, and added together, that puts the opponent right into field-goal range.
Care for an example of stupid penalties?
Here you go: the Giants punt the ball with 1:54 remaining and a 21-17 lead to the Washington 29-yard line. The Commanders have one minute and 46 seconds after the punt to drive for a game-winning touchdown. Sure, in football that's plenty of time, but the Commanders only had one timeout left.
What do the Giants do on the very first play? A pass interference penalty that gifted the Commanders 33 yards, putting them at the Giants' 38-yard line. Three plays and a 32-yard reception by Stefon Diggs later, and it was over.
The Giants then had 48 seconds and three timeouts to tie the game with a field goal or keep the win at home with a touchdown.
Final result: interception.
Even Skattebo's 78 rushing yards and two touchdowns – without a fumble this time – or TE Isaiah Likely's nine receptions for 127 yards and a touchdown couldn't save them.
Bottom line: A mediocre Giants team put in a poor performance and lost to an even more mediocre Commanders team.
"That is the throw of the night by J.J. McCarthy." A 66-yarder to Isaiah Likely for the go-ahead TD and lead over Washington in the fourth quarter 🎯 🎥 @NFL https://t.co/Acyu2PBUln
— The Athletic (@TheAthletic) November 13, 2026
COMMANDERS PICK OFF NINE MCCARTHY TO SEAL THE GAME 😳 (Via @NFL) https://t.co/OxEu0HSwij
— Bleacher Report (@BleacherReport) November 13, 2026

Christian McCaffrey (Running Back, San Francisco 49ers)
46-40 win over the Dallas Cowboys (62 rushing yards, 1 rushing TD, 4 REC, 161 receiving yards, 2 receiving TDs)
by TheLuky
Four catches for 161 yards and two receiving touchdowns. With stats like that, you'd usually assume a wide receiver completely torched the opposing secondary. Apparently, Christian McCaffrey does that on the side. On top of that, he added 62 rushing yards and another score on the ground. That makes 223 total yards and three touchdowns in the 46-40 win over the Dallas Cowboys. I think that speaks for itself.
Though those four catches alone are quite absurd. Averaging over 40 yards per reception – as a Cowboys fan, you probably wonder at some point if anyone actually intends to cover this guy. We've known for a while that McCaffrey can decide games as both a runner and a receiver. Actually stopping him from doing so is obviously a different story.
Yet there were plenty of other candidates this week. Joe Burrow racked up 409 passing yards and four touchdowns against Pittsburgh, while George Pickens kept Dallas in the game offensively with 11 catches for 145 yards and three touchdowns. The loss certainly wasn't on him.
And then there was Jahmyr Gibbs. 153 rushing yards, 99 receiving yards, and two touchdowns in the Munich game make for a pretty compelling case as well. By the way, I had him in one of my fantasy teams and was therefore quite ready to award him this section out of pure personal gratitude. But apparently, one is supposed to stay somewhat objective here. What a shame. :D
Ultimately, McCaffrey gets the nod for me by a hair. While Gibbs had more total yards, McCaffrey had an extra touchdown – and San Francisco desperately needed his production in this offensive shootout.
Anyone who had McCaffrey in their opponent's fantasy lineup is welcome to disagree. In any case, I can fully understand any complaints about the Cowboys' defense.

Aidan Hutchinson (Detroit Lions) - Injury While Celebrating
35-10 win over the New England Patriots
by MatB
At first, I wanted to mention the Texans here, who failed to beat the Browns and now sit at six losses. Will they still make the playoffs? I dare to doubt it.
Then the performance of the Saints' offense really caught my eye for this category – they made a very strong case for it.
Ultimately, though, I somewhat provocatively decided on Aidan Hutchinson. Along the lines of: kicking a man when he's down.
Why did I choose this? Because I think we'll soon need a new category in the User Endzone – Injury of the Week.
I want to focus on Aidan Hutchinson, especially given the many posts you see online.
In my opinion, you can tear your ACL doing anything; it doesn't have to be while celebrating. It has even reached the point where coaches are instructing their players not to jump when celebrating anymore.
Sure, jumping puts more strain on the ACL, but was that the sole culprit? By that logic, he shouldn't jump during a game to intercept or bat down a pass, or leap over a player. Because it could have happened there too.
I believe that in most cases with this kind of injury, the ACL was already compromised, and that final movement was the proverbial straw that broke the camel's back.
When you add the fact that Patriots QB Drake Maye broke his ankle on the very same play and his season is likely over as well, it makes it all the more bitter.
This injury is terrible for the Lions and even worse for him. Especially for the Lions, who had previously lost their star linebacker Jack Campbell for an extended period (or for good). The Lions, who have had so much bad injury luck in recent years.
And yet Dan Campbell manages to build a team that wins games and usually makes the playoffs.
Now we could reopen the debate about why these injuries occur with such frequency and severity, for the Lions and across the NFL. Are there too many games, too much strain, too much travel? Now with the International Games, poor load management?
Probably a bit of everything, though I'll leave load management aside here, as I'm far too removed to judge or critique that.
I'm curious to hear your thoughts, or do you feel this is simply part and parcel of the NFL and elite sports – just the inherent risk every pro takes?
Aidan Hutchinson goes down holding his leg after jumping and celebrating a sack https://t.co/jT4UxVOCyU
— JM Football (@JomboyMediaFB) November 15, 2026

Davison Igbinosun (Cornerback, Buffalo Bills)
31-12 win over the New York Jets (2 pass deflections, 1 interception)
by MatB
Chiefs RB Emmett Johnson really belongs here after making a major statement as a rookie – but more on that later from my fellow writer TheLuky, who basically snatched him from right under my nose.
So I "had to" sift through the rookie performances of the week. One player who stood out to me was Jets QB Cade Klubnik – when he had to step in against the Bills for the injured Geno Smith, the game was briefly hanging in the balance. He found receivers and was a dangerous threat on the ground as well. But my actual Rookie of the Week was able to adjust and keep the Jets from getting back into the game.
I'm talking about Bills CB Davison Igbinosun. The Bills' 2026 second-round pick, who played his college ball for the Ohio State Buckeyes.
Projected for rounds three or four before the draft, the Bills even traded up four spots in the second round to snag him as the seventh cornerback selected in this draft. The Bills' secondary was considered a major weakness before the season – especially that second cornerback spot, which had been heavily searched for in recent years. With him, they seem to have found their man.
In Week 10, he caught my eye once again after a strong Week 9 performance, and to be fair, I was watching him a bit more closely. He was targeted ten times as the primary defender by the Jets. Five times his matchup was star WR Garrett Wilson, twice Adonai Mitchell. Those ten targets yielded just four receptions – and no, not all by Garrett Wilson; he only caught two passes against him, Mitchell had one, and TE Mason Taylor had one. On top of that, he recorded four tackles and a tackle for loss in this game.
On the remaining passes, he broke up two and grabbed an interception, which he returned 17 yards toward the Jets' end zone before losing it on a fumble – the one small blemish on an otherwise stellar outing.
He also caught my attention in Week 9 against the Vikings and star receiver Justin Jefferson, allowing zero receptions and zero yards against him and playing a key role in holding Justin Jefferson to just three receptions on eleven targets.
Before the season, coverage and penalty issues were considered Igbinosun's weaknesses. The penalty troubles were especially visible early in the season, but they have noticeably decreased. And he has emphatically disproven the concerns about his coverage. Against the Jets, only 40% of the passes in his direction were completed. His season average is 51%, with a sharp upward trend in Igbinosun's favor over recent weeks, considering he's only been a starter since Week 4. With performances and an upward trajectory like that, he'll stay in that role, and the Bills have likely found their CB2. Combined with the trade for Amani Hooker, what was once a vulnerability looks to have turned into a much stronger unit.
Also worth mentioning in this section: Lions DE Derrick Moore, who stepped right into the breach for Hutchinson with two sacks, or Seth McGowan, who fits TheLuky's topic perfectly.
Cade Klubnik throws an ugly interception to Davison Igbinosun who loses the fumble, and the Jets recover! It's the rare double turnover play. https://t.co/lTsZ1nhzAE
— The Goal Line Grind (@theGLgrind) November 15, 2026

4
by TheLuky
Four home wins. Zero home losses. The Cleveland Browns.
Yes, you read that right. These Browns. With this Deshaun Watson.
Following the 27-24 win over Houston, Cleveland actually stands at 4-0 at home. The franchise last started like this at home in 1963. I don't know who among you had that on your radar before the season – but I'd certainly love to see the rest of your predictions.
And because one four isn't enough, here comes the next: the Browns have already won four games this season after trailing by double digits. A franchise record. Against the Texans, they first let the opponent jump out to a 17-0 lead before apparently remembering that they were allowed to play too.
And Watson? Against his former team, he led the decisive drive before Quinshon Judkins punched in the game-winning touchdown with 53 seconds left. Think what you want of Watson, but you have to give him credit for his on-field contribution to this win.
Still, I'm always a bit conflicted about comeback stats like this. Of course, it shows quality and character when a team doesn't fall apart after falling behind big. But you also have to ask yourself why you keep putting yourself in that hole so consistently, or take a closer look at the Texans, who suffered a complete meltdown.
Perhaps the Browns could try playing solid football right from the opening whistle for once. It would probably be a welcome change of pace for their fans' nerves.
What do you think: Are these four comebacks proof that Cleveland has more to offer than we give them credit for – or are they mostly salvaging games that they almost threw away themselves?

The Luky:
How Much Running Back Does a Good System Need?
Kenneth Walker goes down, Emmett Johnson steps in – and finishes the day with 101 rushing yards, six catches for 70 yards, and two receiving touchdowns. There are probably more pleasant pieces of news for a running back trying to convince his employer why he, of all people, is indispensable.
For me, this brings up one of the most intriguing questions about the position: How much is the running back himself, and how much comes down to blocking, playcalling, and the overall scheme?
When the backup produces right away, the quick answer is naturally: anyone can run in that system. But I wouldn't make it quite that simple. A backup is still an NFL player and can simply be good. Attributing Johnson's performance solely to Andy Reid and the system would be pretty unfair to him.
At the same time, I understand any franchise that thinks twice about how much money to commit to the position. If you can get a large chunk of that production at a lower cost, that leaves more cap space for other needs.
And then you watch Jahmyr Gibbs and realize why this debate can't simply be settled with "running backs are replaceable." A system can create space. What a player does with it, how he evades tackles, and how he contributes in the passing game remains individual quality.
My take: A good system can make a decent running back look great. But an exceptional running back unlocks possibilities in that system that it might not have with any other player.
So the pivotal question for me is: Are you paying a player for something your system produces anyway – or for something only he can provide?
What do you think: Would you open up the checkbook for an elite running back, or would you rather invest that money into the offensive line?
MatB:
There are so many topics after Week 10 that it takes more than just this one take of the week.
First, though, I'd like to touch on the opinion of our colleague Patrick_R after Week 8. I, too, am a fan of American football in general, not just the NFL. In fact, I believe football in Austria is much closer to the fans than the NFL will ever be over here. Sure, the level isn't the same, but when you look at the European leagues, the football being played is already very strong.
That's why I want to make a pitch for it: check it out. Whether it's European leagues, Austrian leagues, youth football, or the college football system in Austria – there's something for everyone. Each of these events has its own unique flair. From the fan support at the games to the whole atmosphere. The events around the Austrian college football final are really impressive, as are the European matchups. And if that's not enough, I'm sure every football team in Austria welcomes volunteers with open arms – that's how I got even more involved with the sport. Every single team appreciates your support.
As I was writing these lines, plenty of topics crossed my mind that would fit here. Injuries – no, not again. Backup QBs or rookie QBs – been there, done that.
One thing I can't shake, however, is the disparity in quality across the NFL despite the salary cap. How can it be that one team has seven wins while another is just celebrating its first victory of the season this week? These are all full-time pros, selected from the best college talent in every draft class. And those college talents were previously filtered from high school standouts. So the number of available spots shrinks with every step. If you look at this year's college season, there are only two teams in the top 10 that remain undefeated at 10-0 – and no, I'm not talking about the traditional powerhouses like Alabama (2 losses), Georgia (1 loss), Ohio State (3 losses), or the Michigan Wolverines (5 losses), to name just a few. For the record, those two teams are Utah and UCLA.
In college football, it happens that #1 Georgia beats #6 Alabama, only to lose a week later to the unranked Auburn Tigers. Upset losses like that happen all the time in college football, but they feel far less common in the NFL. Is it because the star power and depth of talent in the NFL is even higher, or because the players are older and therefore more mature? Why is it, then, that teams like the Jets always seem to be in rebuilding mode and can never get it right, or that every year before the season starts there are clear favorites who frequently make the playoffs or reach the Super Bowl?
Over the last ten years, there have been only six different Super Bowl champions. Why have the Chiefs made the playoffs nine times during that stretch, the Bills and Eagles eight times, teams like the Packers, Rams, and Steelers seven times, while the Jets haven't made it at all, the Cardinals just once, and nine out of 32 teams only twice?
Parity, which the NFL constantly advertises, looks a bit different to me.
But back to the question: What causes this?
In my view, it takes stable leadership that gives management the time it needs for such a process – and I'm not talking about one or two years. Management, in turn, needs to find the right head coach and grant him the necessary time as well – again, not just a year or two. The head coach needs a coaching staff he trusts and that rewards that trust, and only then do we get to the roster. The coach also needs the right personnel to execute his vision, and only then does the question arise for me: what matters most? And here I firmly agree with the adage: a football game is won in the trenches.
Ultimately, it also depends on how the players develop and how well the coaching staff can develop them.
I assume you might see this differently, and I'd love to hear your take – we're really looking forward to it.
And one last request, since I couldn't make it to Munich: please share your impressions and feedback from the NFL Munich Game.
Anyone who would also like to try their hand at writing with us is welcome to reach out at info@userendzone.at. If anyone wants to join our fantasy games (pick'em and survivor), feel free to contact us there as well. Or if you have a question you'd like us to address, or a "Question of the Week," don't hesitate to write to us if we can't get to it here in the comments.