The Ravens just walked into Lambeau without Lamar Jackson and put up 41 points with just 107 passing yards.

Read that again, because it still doesn’t sound real.

Baltimore didn’t fluke their way into a win with a couple of busted coverages and a pick-six. They won the most old-school way possible: by turning the game into a Derrick Henry endurance test until Green Bay tapped out.

Henry’s night was the headline, obviously — 36 carries, 216 yards, four rushing TDs — and John Harbaugh called it one of the best performances he’s ever seen.

But the more interesting part is what it means next. Because the Ravens didn’t just stumble onto a weird box score. They may have just found the exact gameplan they’ll need again in Week 18 in Pittsburgh, with the division on the line and Lamar’s status still up in the air.

Still the King

This wasn’t “run-heavy.” This was run-obsessed — the kind of game plan where everyone in the stadium knows what’s coming and it still doesn’t matter.

Baltimore finished with:

• 53 rushes

• 307 rushing yards

• 4 rushing TDs

• 40+ minutes of possession

That’s not balance. That’s a statement.

There was only one punt in the entire game. Baltimore scored on its first five possessions, took a 27–14 lead into halftime, and spent most of the night forcing Green Bay to defend the same problem over and over — tackling Derrick Henry with tired legs.

To Green Bay’s credit, the Packers did make it interesting for a moment. They showed a pulse in the third quarter, trimmed the lead to 27–24, and for a few minutes, the game felt like it could slip away.

Baltimore’s response was exactly what a run-first team has to be able to do in that spot: slow the game back down. No panic. No chasing points. Just control. A long, clock-eating drive — 12 plays, 85 yards — ended with Tyler Huntley hitting Zay Flowers for a short touchdown to push the lead back to 34–24 and take the air out of the building.

From there, it was academic. Henry put the finishing touch on it with a late 25-yard touchdown run, a fitting end to his spectacular night.

Matt LaFleur’s postgame line summed it up better than any stat could:

"That was a humbling night. Give Baltimore a ton of credit. They came in here and were in complete control the whole game."

Just How Rare Is It?

The modern NFL is built to make passing easier and scoring higher. Rules favor it. Schemes lean into it. If you want to score a bunch of points in today’s league, the default assumption is that your quarterback is going to have a big night.

That’s why a game like this feels like it dropped out of a different decade.

Since 2000, there have only been 12 games where a team scored 40 or more points while its quarterback threw for under 110 passing yards.

Twelve. In 25 seasons. In an era where 300-yard passing games barely raise an eyebrow anymore.

And even within that tiny group, most of those games come with an asterisk. A pick-six here. A kick return there. Short fields stacked on top of each other until the score gets out of hand.

That’s usually how you get to 40 without throwing — by stealing points in unconventional ways.

What makes Baltimore’s night different is that it didn’t feel fluky at all. There wasn’t some weird turnover avalanche or special-teams chaos doing the heavy lifting. The Ravens lined up, ran the ball, stayed ahead of the chains, and kept scoring the old-fashioned way. That’s what makes this one stick out, even among the other 11.

The Only Two Games This Century With a 200-Yard Rusher

When you add one more condition — a 200-yard rusher — that already tiny list basically disappears.

There have been only two games since 2000 where a team scored 40+, the quarterback threw for under 110 yards, andone player ran for at least 200:

• 2025 Ravens at Packers: Tyler Huntley threw for 107 yards, Derrick Henry ran for 216 yards and four touchdowns, and Baltimore scored 41.

• 2009 Browns at Chiefs: Brady Quinn threw for 66 yards, Jerome Harrison exploded for 286 yards and three touchdowns, and Cleveland scored 41.

That’s it. That’s the list.

And the comparison matters, because the Harrison game has lived on for years as one of those “how did that even happen?” afternoons. Harrison essentially ran for 300 yards by himself, the Browns barely threw the ball, and somehow the scoreboard still ended with a 41.

The Ravens finished with 300-plus rushing yards as a team, something that hadn’t happened in this specific statistical lane since that 2009 Browns game, when Cleveland ran for 351 yards.

And it wasn’t just a fun footnote for Henry, either. His 216 rushing yards were reportedly the most ever by a visiting player at Lambeau Field, and it was his seventh career 200-yard rushing game, pushing him past Adrian Peterson and O.J. Simpson for the most in NFL history.

Now Comes Pittsburgh, and the Blueprint Is Sitting Right There

Week 18 has Ravens at Steelers on Sunday night, with the AFC North title and a playoff spot riding on it.

For Baltimore, the path to a win is pretty clear, but it comes with one important caveat: don’t become predictable. Even in a Henry-first game plan, you can’t just line up and run the same look over and over and expect it to hold up for four quarters. You need a few answers baked in — a couple timely play-action shots, some quick-game throws to punish stacked boxes, maybe a designed keeper or two just to keep edge defenders honest. Not an air raid. Just enough to make the defense hesitate.

That balance matters even more when you look at the other sideline. The Steelers are down a weapon — DK Metcalf will miss his second straight game due to suspension — which only makes the limit possessions and force long drivesapproach even more appealing. The fewer total drives this game has, the better it is for Baltimore. Make Aaron Rodgers be patient. Make the Steelers execute 10- and 12-play marches without mistakes. That’s usually where flags, sacks, or a mistimed throw creep in.

And then there’s the real wrinkle: Lamar.

John Harbaugh hasn’t sugarcoated it. He’s called Lamar Jackson’s back contusion “very painful,” and that’s not the kind of injury you just tape up and run around on. Lamar’s game is built on movement — sudden acceleration, escaping pressure, turning broken plays into chunk gains — and when your back isn’t right, all of that isn't nearly as impactful.

If Lamar can’t go again — or if he’s out there but clearly limited — the Ravens aren’t walking into Pittsburgh guessing or scrambling for answers. They’ve already shown the outline of the plan, and it looks a lot like what we just watched at Lambeau:

• Make it a Derrick Henry game. Not 18 carries. Not 22. The kind of workload that forces the Steelers to tackle him over and over, deep into the fourth quarter.

• Stay out of 3rd-and-long. The fastest way to lose in Pittsburgh is to let the pass rush tee off. Even if T.J. Watt can’t go, the Steelers still have enough bodies up front to make life miserable for an immobile or backup quarterback.

• Limit possessions. Aaron Rodgers is far less dangerous when he’s watching from the sideline.

• Win the red zone and protect the ball. If you’re not throwing much, you can’t afford empty trips.

And if you need a reminder of why avoiding chaos matters against Pittsburgh, just look back at the first meeting. The Steelers beat the Ravens 27–22 in Baltimore in a game where the Ravens actually outgained them 420–318 and won time of possession 33:44 to 26:16. On paper, that looks like a Ravens win. In reality, one late replay reversal wiped out what felt like a game-changing touchdown and flipped the entire night.

That’s Steelers football. They hang around. They force you into one or two high-stress moments. And they dare you to be perfect when it matters most.

Now Baltimore gets a chance to take their blueprint on the road, into Pittsburgh, under the brightest lights, with the division at stake.

Run it. Protect it. Make it miserable.

All stats courtesy of NFL Pro.