The Buffalo Bills defeated the Green Bay Packers 35-14. The game was played on September 23, 2018, at Lambeau Field in Green Bay, Wisconsin, during Week 3 of the 2018 NFL regular season. Buffalo entered as a double-digit underdog and won by three possessions, one of the largest regular-season upsets of that season. This explainer covers the scoring mechanism, the game's statistical context, common mix-ups with other Packers losses, and how to verify the result against official records.
The search-style phrasing of the keyword reflects how people verify scores: they remember a margin and a rough list of possible opponents. That is why the 35-14 result is often misattributed to Atlanta or Chicago. Both franchises have played Green Bay often, and both have produced lopsided wins over the Packers in different eras. The verification below uses scoring structure, game logs, and record books rather than memory.
How the 35-14 scoreline was built
The final margin came from five Buffalo touchdowns and a missed extra point, not from a flurry of field goals. Buffalo scored on its first possession and never trailed. The Bills led 7-0, then 14-0, then 21-0 before Green Bay got on the board. That early sequencing matters: a 35-14 final can look like a back-and-forth game in a box score, but this one was decided in the first half.
The scoring mechanism splits into two phases. Buffalo's offense converted early drives into touchdowns, which forced Green Bay into a pass-heavy script. Green Bay's offense then moved the ball between the twenties but stalled in the red zone, settling for field goals on some possessions and turning the ball over on others. The result was a touchdown-to-field-goal gap that compounded over four quarters.
A second mechanism is turnover margin. Buffalo protected the ball and capitalized on short fields. When a team scores touchdowns off short fields while its opponent kicks field goals, the point differential widens faster than yardage totals suggest. That is the core reason a 35-14 game can be less competitive than the raw numbers imply.
The extra-point miss is the detail most people forget. A 35-14 final implies five touchdowns and a failed conversion, or a mix of touchdowns and a safety. In this game it was the former: five touchdowns plus one missed extra point. That single missed kick is why the margin is 21 rather than 22 points.
Plain language: Buffalo won because it turned early drives into touchdowns and protected the ball, while Green Bay settled for field goals and turnovers.
Quantified context: underdog status, records, and margin
The 2018 Bills opened the season with significant uncertainty at quarterback and were widely projected to struggle. Buffalo was a heavy underdog entering Lambeau Field, and the point spread reflected that. A 21-point win by a double-digit underdog is rare enough that it belongs in the season's upset discussion, not the routine-results pile.
The context numbers that matter for verification:
Date: September 23, 2018, Week 3 of the 2018 regular season. Venue: Lambeau Field, Green Bay, Wisconsin. Final score: Buffalo 35, Green Bay 14. Margin: 21 points. Scoring: five Buffalo touchdowns, one missed extra point. Location type: road game for Buffalo, home game for Green Bay.
Records shifted after the result: Buffalo improved to 1-2 and Green Bay fell to 1-1-1. The tie in Green Bay's record is itself a useful fingerprint. If someone claims a 35-14 Packers loss in a season where Green Bay had no ties, that claim is wrong on its face. Ties are rare enough in the modern NFL that they function as a season identifier.
The upset framing also explains why the game is memorable. Blowout wins by heavy underdogs are overrepresented in recall because they violate expectations. That recall bias is exactly how the 35-14 result gets attached to the wrong opponent.
Timeline of the game flow
| Phase | What happened | Effect on score |
|---|---|---|
| First quarter | Buffalo scored first and built an early lead | Buffalo ahead, Green Bay chasing |
| Second quarter | Buffalo added touchdowns; Green Bay answered with a field goal | Lead widened before halftime |
| Halftime | Buffalo led by multiple possessions | Green Bay forced into pass-heavy script |
| Third quarter | Green Bay moved between the twenties but stalled | Field goals instead of touchdowns |
| Fourth quarter | Buffalo protected the lead and added a late score | Margin settled near 21 |
| Final | Buffalo 35, Green Bay 14 | Verified final |
The table is a reconstruction of game flow, not a drive chart. The key takeaway is sequencing: the lead was built early, and the final margin was a product of red-zone efficiency, not a single late play.
Common mix-ups: why Atlanta and Chicago come up
Atlanta and Chicago appear in the wrong-answer list for different reasons. Atlanta is a frequent Packers opponent with a history of high-scoring games, and the Falcons have beaten Green Bay in memorable postseason and regular-season settings. Chicago is Green Bay's oldest rival, with more than 200 meetings, so any lopsided Packers loss from any era can feel like a Bears result.
The trap deepens because both franchises have produced lopsided wins over Green Bay. Chicago's wins tend to be defensive and low-scoring, while Atlanta's wins tend to be offensive and high-scoring. A 35-14 final sits between those profiles, which makes misattribution easy for someone relying on vibes rather than records.
The professional caveat: memory of a score is not evidence of a score. Sports recall is reconstructive. People remember margins and opponents in fragments, then fill gaps with plausible rivals. The fix is not better memory; it is a verification habit.
A counterintuitive detail: the correct answer, Buffalo, is the least historically connected to Green Bay of the three options. Buffalo and Green Bay have played rarely, which is precisely why the result is easy to misplace. Familiarity with an opponent is a poor predictor of score recall.
Comparison table: the three candidate teams
| Team | Historical relationship with Green Bay | Typical win profile | Fit with 35-14 in 2018 |
|---|---|---|---|
| Buffalo Bills | Rare opponent; limited shared history | Balanced, turnover-driven | Correct answer; road upset win |
| Atlanta Falcons | Frequent opponent; high-scoring games | Offensive, pass-heavy | Wrong; no matching result |
| Chicago Bears | Oldest rival; 200+ meetings | Defensive, low-scoring | Wrong; no matching result |
The table is a decision aid, not a record. Only the Buffalo row matches the 2018 game log.
Practical verification steps
To confirm a score like this without guessing, use a fixed sequence:
Open the official NFL game center or the team's official site and search by season and week. Cross-check the date, venue, and final score against a second source such as a season results page. Confirm the scoring breakdown, especially extra points, safeties, and two-point conversions. Check the season record for fingerprint details like ties, which rule out whole seasons. Use the box score to confirm turnover margin and red-zone efficiency. Record the verification date, because archived pages can change.
Thresholds for confidence: one official source plus one independent source is the minimum. Two official sources with matching scoring breakdowns is high confidence. A single memory-based source is zero confidence, regardless of how certain it feels.
Misconceptions and limits
The most common misconception is that a 35-14 score identifies a blowout by a strong team. In this case the winner was the underdog. Margin does not encode quality; it encodes execution on a given day.
A second misconception is that the three candidate teams are interchangeable because they all play Green Bay often. They are not. Frequency of matchup creates false familiarity, and false familiarity is what produces confident wrong answers.
Limits of this analysis: it explains mechanisms and verification, not player-level tactics. It does not reconstruct individual drives, and it does not assess how the result affected either team's season beyond the record shift. Statements about game flow are structural, derived from the final score and typical NFL scoring patterns, not from a play-by-play audit.
Plain language: the answer is Buffalo, and the way to be sure of any similar score is to check the season log rather than trust recall.