Nick Keller's 57-yard try was blocked with 15 seconds left in Louisville, Devin Cook fell on the ball, and Wake Forest walked out of an ACC road stadium with a 30-27 win over a ranked team. It was the best afternoon of the season. It was also a game the Deacs spent all day making harder than it needed to be. There were 10 penalties for 85 yards, including an unsportsmanlike-conduct flag on third-and-goal that turned a touchdown chance into a field-goal attempt, and a Carlos Hernandez fumble that was the team's only giveaway. Jake Dickert's postgame line was "I own these penalties."
That is the season in one paragraph, and it is why Saturday matters more than an 82% win probability suggests. Stanford visits Winston-Salem at noon on ACC Network, and it is the most favorable matchup Wake Forest has had.
The habit that won't go away
Back in Week 1 against Akron, the game book showed 11 Wake Forest penalties for 115 yards, and Dickert declined to make a season-long judgment off one sloppy afternoon. Fair enough then. Four games in, the counts include 13 penalties for 122 yards against Miami, a total Dickert called "very costly", and 10 in the Louisville win, and the Miami game included a holding call in the end zone that handed over a safety during a comeback. That is no longer an opening-week hangover.
The rebuilt line tells a similar story. Fans watching at home can only judge it the way the box score does. How often does Gio Lopez get hit, and how often does a drive die on first-and-20.
Against Miami and Louisville, those things were survivable because the rest of the roster outran them. Against Stanford, they shouldn't need to be survived at all. That's the thing to watch, not the scoreboard, which should take care of itself, but whether the flag count gets to five instead of ten and whether Lopez finishes a series upright.
What's already working
He went 12 of 19 for 225 yards against Louisville, with a 77-yard touchdown to Carlos Hernandez, and carried 8 times for 15 yards. That version of the offense is gone.
Hernandez is the reason. He caught nine balls for 194 yards at Louisville, three short of his career high, and the 77-yard touchdown that put Wake Forest ahead. It's been like this all year. After the precautionary exit in the opener, he came back at Purdue and converted a reviewed fourth-and-15 in double overtime, a 14-yard catch flipped to a 15-yard first down at the Purdue 2 that kept the winning drive alive. He is the offense's most reliable answer, and Stanford will have to decide whether to double him.
The defense keeps arriving late. Louisville had 21 points by halftime, and then Wake Forest posted four sacks, two by Kirschke, nine tackles for loss, a first career interception from Somad Eaddy, and a scoreless fourth quarter while holding the Cardinals to 75 rushing yards on 38 carries. Aiden Hall had 11 tackles. It's a good unit after halftime and an unresolved one before it. Starting fast against a lesser opponent would be the first evidence that the pattern is a choice rather than a trait.
The stakes, honestly
Small. A win nudges Wake Forest's ACC championship-game odds to about 2%; a loss drops them to roughly 0.2%. Neither number changes a Saturday.
There's one small piece of history worth knowing. These programs have met only three times, and Wake Forest leads 2-1, including a 27-24 win in Palo Alto in 2024. Stanford's last trip to Winston-Salem was 2009. The series offers no pattern to lean on. Just a heavy favorite at home with a specific list of things to fix.
Full numbers are in the interactive guide, and the model is explained in the methodology.
Nothing else on Saturday's board moves Wake Forest's math. Turn the game on at noon and count the flags.