My Take: Five Chiefs Who Told the Story of a 20-3 Loss in Seattle

Kansas City Chiefs Merchandise - https://kansascitychiefs-mytake.blogspot.com/p/kansas-city-chiefs-merchandise.html

Kansas City’s first loss of the 2026 season was not close. The Chiefs fell 20-3 to Seattle on October 25 at Lumen Field, finishing with 213 total yards, converting 3 of 11 third downs and holding the ball for only 24:09. Seattle gained 410 yards and converted 11 of 16 third downs. The Chiefs’ official recap confirms that Seattle led wire to wire.

Finding three standouts in a 17-point loss requires some perspective. These were not game-winning performances. They were the clearest examples of individual value in a game Kansas City collectively failed to control.

Standout No. 1: Nohl Williams

1. Production: Williams recorded 10 total tackles—four solo and six assisted—and intercepted Sam Darnold in the end zone, returning it 65 yards to the Seattle 44. The box score and play-by-play confirm the interception and return.

2. Efficiency: Seattle attempted 28 passes, and Williams turned one into Kansas City’s only takeaway while remaining active as a tackler. That does not prove he won every coverage rep, but it does show he delivered the defense’s biggest high-leverage play.

3. Situation: The interception came with 23 seconds left in the second quarter after Seattle reached the Kansas City 2. Instead of entering halftime down at least 13-0, the Chiefs briefly had a chance to steal points before the break.

4. Expectations: Williams entered Week 7 without an interception in 2026. This was his first, and it came during an otherwise difficult night for the secondary.

Takeaway: Williams made the one defensive play that gave Kansas City a realistic chance to change the game’s direction before halftime.

Standout No. 2: Noah Gray

1. Production: Gray caught all three targets for 44 yards, tying Travis Kelce for the team lead in receiving yards despite seeing five fewer targets.

2. Efficiency: Three catches on three targets is a 100% catch rate and 14.7 yards per target. Kansas City’s wide receivers combined for only 39 yards on 13 targets, according to the Week 7 snap review.

3. Situation: Gray had a 19-yard catch in the first quarter to move Kansas City into Seattle territory and another 19-yarder in the fourth quarter on one of the Chiefs’ final meaningful drives.

4. Expectations: Gray entered Week 7 with 114 receiving yards through five games. His 44 yards in Seattle represented a meaningful increase in impact for a player whose normal role does not guarantee volume.

Takeaway: Gray did not rescue the offense, but he was efficient and dependable every time Mahomes looked his way.

Standout No. 3: R Mason Thomas

1. Production: Thomas had one solo tackle, but the PFF-based snap analysis credited him with four pressures, including one quarterback hit, on only 20 defensive snaps.

2. Efficiency: He was on the field for 15 pass plays and dropped into coverage on three, implying 12 pass-rush opportunities. Four pressures in that limited role is notable production, though that percentage is an inference from reported deployment rather than an official NFL metric.

3. Situation: Early in the fourth quarter, Thomas stopped Jaxon Smith-Njigba after a two-yard catch on third-and-7, forcing a punt and giving Kansas City another possession while the score was still 13-3.

4. Expectations: Thomas played a season-low 20 snaps after larger workloads earlier in the year, yet still produced pressure. His narrower passing-down role may be allowing him to attack more aggressively.

Takeaway: His snap count shrank, but his impact did not disappear.

Did Not Play Well: L’Jarius Sneed

1. Production: Sneed recorded two solo tackles and no passes defensed. The PFF-based review charged him with five catches allowed for 83 yards and four first downs.

2. Efficiency: Sneed played only 14 defensive snaps, including 11 coverage snaps. Five receptions in that workload is the central issue. Coverage stats do not explain every assignment, but the production against him was difficult to ignore.

3. Situation: Seattle converted early third downs against his coverage, and another completion late in the first half helped move the Seahawks near the goal line before Williams’ interception ended the drive.

4. Expectations: Sneed entered the game questionable with a knee injury, which matters. Even with that context, Kansas City reduced his workload as the night went on.

Takeaway: One poor game does not define Sneed, especially while dealing with an injury, but Seattle found too much success when throwing his way.

Overlooked Contributor: Evan Johnson

1. Production: Johnson returned three kickoffs for 81 yards, averaging 27.0 yards, and caught two of three targets for 17 yards. The play-by-play also credits him with special-teams involvement.

2. Efficiency: His return average consistently gave Kansas City better field position than a touchback baseline, while his two receptions added useful depth production.

3. Situation: His longest return was 41 yards in the fourth quarter, taking the ball to the Kansas City 42. He also caught a 12-yard pass on second-and-20 to help set up a third-down conversion.

4. Expectations: Johnson is a reserve running back, so neither receiving nor return production is guaranteed. On a night when Kansas City generated only 213 yards of offense, his hidden yardage mattered.

Takeaway: Johnson’s contribution was easy to miss in the box score, but he was one of the few Chiefs consistently improving field position.

My Take

The uncomfortable truth is that Kansas City’s standouts were mostly trying to keep a bad night from becoming worse. Williams erased a goal-line scoring opportunity. Gray made the most of limited targets. Thomas generated pressure in a reduced role. None of it could overcome an offense that never reached the red zone and a defense that allowed Seattle to convert 11 of 16 third downs.

The contrast between Williams and Sneed is especially useful. One defensive back produced the biggest Chiefs play of the night; another struggled enough that Kansas City reduced his snaps. That does not mean one game defines either player. It does mean performance and health have to matter more than reputation when roles are decided.

My biggest concern is not that Kansas City finally lost. It is how little resistance the Chiefs offered once their early drives stalled. The proper response is not to dismiss Seattle as one bad night. It is to build on the players who still created value while fixing the execution that turned a competitive first half into a 20-3 loss.

My Take: Five Chiefs Who Defined the 22-6 Win Over the Chargers

Kansas City Chiefs Merchandise

The obvious headline from Kansas City's 22-6 Week 6 win over the Los Angeles Chargers was another huge afternoon from Kenneth Walker III. But this weekly spotlight has already spent plenty of time on what Walker is doing to this offense, so I wanted to look one layer deeper this week.

The Chiefs moved to 5-0 on October 18 at Arrowhead Stadium, outgaining Los Angeles 422-259 and keeping the Chargers out of the end zone. The official Chiefs recap also noted that Kansas City forced two takeaways and recorded four sacks after going three straight games without one. Those numbers tell us this was not merely another Walker game. It was a win built on receiving reliability, defensive depth, an emergency offensive-line response and one special-teams issue that still deserves attention.

Standout No. 1: Xavier Worthy

1. Production: Worthy caught seven passes for 73 yards, leading Kansas City in both receptions and receiving yards. The Chiefs' postgame review identified both totals as season highs. He did not score, but he supplied three gains of at least 15 yards and became the most dependable receiving option in a game in which Patrick Mahomes did not throw a touchdown.

2. Efficiency: Worthy caught all seven passes thrown his way, a 100% catch rate, and averaged 10.4 yards per reception. That matters because his value was not limited to one deep shot. He entered Week 6 having caught four passes for 70 yards against Las Vegas in Week 4; against the Chargers, the yardage was similar but the volume and reliability increased. With Rashee Rice unavailable, Worthy's seven-for-seven performance showed he could handle a larger share of the passing game without becoming inefficient.

3. Situation: Two catches stand out in the full play-by-play. On third-and-2 from the Kansas City 41 with 9:21 left in the first quarter, Worthy gained 17 yards to extend a drive that ended with Walker's 33-yard touchdown. Then, with only 14 seconds remaining in the first half, he caught a 19-yard pass to the Chargers' 32. Seven seconds later, Harrison Butker made a 50-yard field goal that sent Kansas City into halftime up 19-3.

4. Expectations: Worthy's role was always going to grow with Rice sidelined, but increased opportunity does not automatically produce efficient football. This was Worthy's highest-volume receiving game of the season, and he handled it without a wasted target. That is a meaningful step from being viewed primarily as an explosive-play threat toward becoming a receiver Mahomes can use to keep an offense on schedule.

Takeaway: The thing I liked most was not the 73 yards. It was how those yards arrived. Third down. End-of-half offense. Chain-moving catches. Worthy gave Kansas City something it badly needed: reliability without sacrificing explosiveness.

Standout No. 2: Ashton Gillotte

1. Production: Gillotte recorded his first sack of the season and was credited with three pressures — a hurry, a quarterback hit and a sack — plus two defensive stops. According to an analysis of the Chiefs' Week 6 snap counts using PFF data, he played 52% of the defensive snaps, his largest share of the season.

2. Efficiency: Three pressures and two stops in a 52% rotational workload is exactly the kind of production Kansas City needs from its non-every-down edge rushers. The Chiefs had generated pressure in previous weeks without finishing sacks; Gillotte helped turn that pressure into an actual drive-ending result. The important denominator here is his role: he did this without playing a full-time share of the defensive snaps.

3. Situation: Gillotte's afternoon was not perfect. With 13:38 left in the second quarter, he was flagged for roughing Justin Herbert, wiping out what would have been a Christian Roland-Wallace interception. But he responded. At 10:58 of the same quarter, the play-by-play credits Gillotte with pressure on Herbert's pass that Jack Cochrane intercepted and returned 48 yards to the Chargers' 17. Later, with 3:45 left in the third quarter, Gillotte sacked Herbert for a six-yard loss on second-and-7. Los Angeles faced third-and-13 on the next snap and punted two plays later.

4. Expectations: This was Gillotte's biggest defensive workload and most productive game of the season to this point. That makes the performance more interesting than the sack alone. Kansas City needs more than George Karlaftis and Chris Jones to create pressure, and Week 6 offered evidence that Gillotte can become a meaningful part of that rotation.

Takeaway: I actually like this performance more because it included a mistake. Gillotte had a costly penalty erase a takeaway, then came back and directly influenced another takeaway before recording a drive-killing sack. That is the response you want from a developing pass rusher.

Standout No. 3: Joshua Ezeudu

1. Production: Ezeudu was not expected to be one of the important names in this game. He became one when starting right tackle Jaylon Moore left with a concussion. Ezeudu stepped in and played 30 offensive snaps, including 17 pass-play snaps, and remained at right tackle for the rest of the afternoon. The Week 6 snap review says PFF charged him with only one pressure/hurry in that work.

2. Efficiency: One credited pressure over 17 pass-play snaps is a solid emergency performance, especially for a player entering the lineup without the benefit of starting the game. Offensive-line evaluation is more complicated than one pressure statistic, so I am not going to pretend that number proves every block was clean. What it does show is that the Chargers did not suddenly turn Kansas City's replacement right tackle into an obvious pressure point.

3. Situation: The situation is the story here. Moore's concussion forced Kansas City to change right tackles during the game, and Ezeudu handled the position throughout the second half while the Chiefs protected a 19-3 halftime lead. There was no dramatic touchdown or turnover attached to his name. For an emergency offensive tackle, that is often the point — the offense did not have to fundamentally change because the backup entered.

4. Expectations: Ezeudu arrived in Kansas City after a preseason trade from the New York Giants and had not previously been part of the Chiefs' regular offensive-line rotation. Against the Chargers, he was suddenly asked to protect Mahomes at right tackle for 30 snaps. Compared with that normal role, simply preventing the injury from becoming a defining weakness was a meaningful positive.

Takeaway: Backup offensive linemen usually become famous for the wrong reason. Ezeudu did not. If Moore has to miss time, this game at least gives Kansas City evidence that its next option can step into a difficult spot without the entire protection plan collapsing.

Did Not Play Well: Harrison Butker

1. Production: Butker made three of four field-goal attempts and one of two extra points, accounting for 10 Kansas City points. He connected from 44, 50 and 30 yards, but missed a first-quarter PAT and a 52-yard field goal in the fourth quarter. His NFL season splits show him at 10-for-13 on field goals through five games, including 1-for-4 from 50-59 yards.

2. Efficiency: For this game, that is 75% on field goals and 50% on extra points. Context matters: NFL.com's Week 6 review specifically noted the windy conditions at Arrowhead. But the same review also pointed out that Butker entered the afternoon having made 77.8% of his field-goal attempts. One windy miss from 52 yards would not concern me much by itself. Pairing it with a missed PAT and a season-long 1-for-4 mark from 50-plus is enough to make this worth watching.

3. Situation: Butker's missed extra point came at 7:21 of the first quarter after Walker's 33-yard touchdown, leaving Kansas City ahead 9-0 instead of 10-0. The 52-yard miss came with 11:51 left in the fourth quarter and the Chiefs leading 19-6; making it would have pushed the margin to 16. To his credit, he also hit a 50-yarder with seven seconds left in the first half and later made a 30-yard kick with 3:56 remaining to finish the scoring.

4. Expectations: This is a standards-based selection, not a claim that Butker had a disastrous game. A veteran kicker on a championship-level team is expected to make routine extra points and provide confidence when drives stall near midfield. Kansas City was good enough defensively that Sunday's misses did not become decisive. In a three-point playoff game, the same margins can look very different.

Takeaway: There is no reason to panic, but there is a reason to pay attention. Butker still made two important kicks of 44 and 50 yards. The concern is consistency, especially because the Chiefs' red-zone offense is already creating situations in which his leg may matter more than they would like.

Overlooked Contributor: Andrew Armstrong

1. Production: Armstrong's box score was tiny: one catch for 13 yards on two targets. His role was not. The Chiefs' official postgame notes confirm that the practice-squad elevation played 42 offensive snaps and nine special-teams snaps in his first regular-season action. The Week 6 snap analysis also shows that he was on the field for 15 running plays.

2. Efficiency: One reception on two targets is a 50% catch rate, but two targets are far too small a sample to make a meaningful judgment about receiving efficiency, and target results alone do not establish receiver fault. The more useful denominator is workload: 42 offensive snaps in a first career start is not an emergency cameo. Kansas City trusted Armstrong to stay on the field for a substantial portion of the game.

3. Situation: His one catch mattered. With 2:16 left in the second quarter, on first-and-10 from the Chargers' 21, Armstrong caught a 13-yard pass to the 8. Two plays later, Walker scored from two yards out to give Kansas City a 16-3 lead. Armstrong also made a special-teams tackle on the Chargers' first kickoff return after Kansas City's opening field goal, according to the play-by-play.

4. Expectations: Armstrong was elevated from the practice squad because Rashee Rice was unavailable and then made his first career start. The reasonable expectation was simply to survive the assignment and give Kansas City functional depth. Instead, he handled 42 offensive snaps, contributed on special teams and recorded the first regular-season catch of his career in a scoring drive.

Takeaway: Armstrong is exactly the kind of player this category is for. One catch will disappear in the box score next to Walker's rushing total and Worthy's seven receptions. But when a practice-squad elevation can step into the starting lineup for 42 snaps without the offense falling apart, that matters.

My Take

Walker was the best offensive player on the field Sunday. That is not really debatable. But the more interesting question for Kansas City is whether the roster around its stars is becoming strong enough to win games when injuries force the depth chart to move.

Week 6 gave us some encouraging answers. Worthy handled a larger receiving burden with perfect target efficiency. Gillotte turned a larger defensive role into pressure, a sack and a hand in a turnover. Ezeudu replaced an injured tackle without becoming the story. Armstrong went from the practice squad to 42 offensive snaps and helped a touchdown drive.

Then there is Butker. His day is the reminder that a comfortable final score can hide details that matter later. The Chiefs were good enough to miss an extra point, miss another field goal, turn the ball over twice and still win by 16. That does not make those mistakes irrelevant.

My biggest takeaway is that Kansas City's margin for error is growing because more players are contributing. The next step is making sure that greater depth is matched by cleaner execution. Against the Chargers, the Chiefs had enough of the first to overcome some of the second.

My Take: Five Chiefs Who Defined the 30-27 Win in Las Vegas

Kansas City’s Week 4 win over Las Vegas was not a clean wire-to-wire performance. The Chiefs trailed 13-10 entering the fourth quarter, were outgained 437-399, and possessed the ball for only 24:18. Yet they still left Allegiant Stadium 4-0 after a 30-27 win because a handful of players changed the game in very different ways. The official Chiefs recap confirms the final score and the late-game sequence, while the NFL’s Week 4 review highlights the same central theme: explosive plays and special teams tilted a game that otherwise stayed on a razor’s edge.

Sources: Chiefs.com game recap, NFL Week 4 review, CBS Sports box score and play-by-play, and PFF Week 4 grading notes.

Standout No. 1: Kenneth Walker III

1. Production: Walker carried 22 times for 177 yards and two touchdowns, adding one reception for 2 yards. His 76-yard run was the longest offensive play of the game for Kansas City, and both of his touchdowns came in the final 3:25. The box score shows he finished the day with 537 rushing yards through four games.

2. Efficiency: He averaged 8.0 yards per carry on 22 attempts. That is not just a product of one explosive run: even removing the 76-yarder, Walker still gained 101 yards on his other 21 carries. Entering the game he had 360 rushing yards on 65 attempts, about 5.5 per carry, so Week 4 was a major step above an already strong early-season baseline.

3. Situation: His biggest run came with 0:30 left in the third quarter, when he burst 76 yards from the Kansas City 16 to the Las Vegas 8. Two plays later, the Chiefs scored to take their first lead. Then, after Tyquan Thornton’s 55-yard catch put the ball at the 2, Walker scored with 3:25 left. Nineteen seconds later, after Kansas City recovered a Raiders kickoff fumble, Walker went 22 yards for another touchdown to make it 30-19.

4. Expectations: Walker entered Week 4 as the engine of Kansas City’s running game, so a productive afternoon was expected. What was not expected was this degree of explosiveness against an undefeated division opponent. He did more than accumulate yards; he supplied the plays that changed the geometry of the game.

Takeaway: This was the performance that kept Kansas City from having to ask Patrick Mahomes to solve every problem. Walker turned a close road game into a game the Chiefs could win with balance.

Standout No. 2: Tyquan Thornton

1. Production: Thornton caught 5 of 8 targets for 111 yards and two touchdowns. His touchdowns covered 2 and 8 yards, and his final catch was a 55-yard gain that set up Walker’s go-ahead touchdown late in the fourth quarter.

2. Efficiency: Thornton averaged 22.2 yards per reception and 13.9 yards per target. Through the first three games he had six receptions for 108 yards and no touchdowns, so in one afternoon he exceeded his previous season total in receiving yards and scored his first two touchdowns of 2026.

3. Situation: His first touchdown came on third-and-goal from the 2 with 2:26 left in the first quarter, tying the game 7-7. His second came at 14:54 of the fourth quarter, immediately after Walker’s 76-yard run, giving Kansas City its first lead. His most important non-touchdown play came on third-and-5 from the Kansas City 40 with 3:35 left: Mahomes found him for 55 yards to the Raiders 5. Thornton was injured at the end of that play, but the catch directly set up the touchdown that put Kansas City back in front.

4. Expectations: Thornton had flashed as a vertical threat before Week 4, but this was a much larger role and a much more complete impact than he had provided in the first three games. The unfortunate ankle injury changes the outlook going forward, but it should not overshadow how decisive his performance was in this win.

Takeaway: Thornton gave the Chiefs the explosive receiving element they needed at exactly the right moments. His box score was strong; his timing was even more valuable.

Standout No. 3: George Karlaftis

1. Production: The traditional box score gives Karlaftis five total tackles and no sack, which badly understates his impact. PFF charted him with 11 pressures on 54 pass-rush snaps, including seven quarterback hits and four hurries, plus three defensive stops. PFF gave him an 89.5 overall grade, the highest mark in the game.

2. Efficiency: Eleven pressures on 54 pass-rush snaps means he generated pressure on roughly one of every five pass-rush opportunities. That matters because Kansas City did not need a sack total to validate the disruption. The Raiders threw 52 passes, and Karlaftis repeatedly affected the pocket without finishing the play himself.

3. Situation: The play-by-play credits Karlaftis with pressure on a third-and-7 incompletion at the Kansas City 23 early in the third quarter, then again on the ensuing fourth-and-2 incompletion after Las Vegas chose to keep its offense on the field. Most importantly, on the Raiders’ final possession with 0:10 remaining, the official play-by-play notes Karlaftis affecting Kirk Cousins on the pass that Xavier Nwankpa intercepted to seal the win.

4. Expectations: Karlaftis is expected to be one of Kansas City’s primary edge disruptors, but this was an unusually productive pressure game even by that standard. He entered Week 4 with one sack on the season. Against Las Vegas, the sacks were absent, but the disruption was not.

Takeaway: This is why evaluating edge play only by sacks can be misleading. Karlaftis consistently hurried the quarterback and helped force the kinds of decisions that eventually ended the game.

Did Not Play Well: Jalen Royals

1. Production: Royals finished with no receptions on two targets. He played 38 offensive snaps, according to the postgame snap-count analysis, but did not record a receiving yard.

2. Efficiency: Zero catches on two targets is a 0 percent catch rate, but that number should not be treated as proof that both incompletions were his fault. The play-by-play shows one target on first-and-10 in the first quarter and another on third-and-3 in the second quarter with pressure noted on Mahomes. The fair conclusion is narrower: Royals had an expanded role and did not turn those opportunities into production.

3. Situation: His first target came with 4:46 left in the first quarter from the Las Vegas 48 and fell incomplete. His second came with 11:34 left in the second quarter on third-and-3 from the Raiders 45, and that incompletion ended the drive with a punt on the next play. That second opportunity mattered because Kansas City was still trying to stabilize an offense that would score only 10 first-half points.

4. Expectations: Royals entered the game with three catches for 17 yards and a touchdown through the first three weeks. With injuries expanding his workload, 38 snaps represented a meaningful chance to establish himself in the rotation. He did not do that statistically in Las Vegas, even though the limited target quality means the performance should be viewed as a missed opportunity rather than an indictment.

Takeaway: Royals was the fairest choice for the below-expectations spot because the role increased and the production disappeared. The next step is not “catch everything”; it is to turn a larger snap share into more reliable involvement.

Overlooked Contributor: Matt Araiza

1. Production: Araiza punted five times for a 47.6-yard average, placed all five inside the 20, and allowed only 4 punt-return yards. He also converted a fake punt with a 12-yard run.

2. Efficiency: Five punts and five inside the 20 is perfect placement efficiency for the category, and the Raiders produced only 4 return yards on those kicks. By comparison, Araiza entered Week 4 with four of seven punts inside the 20 through the first three games. This was his best placement game of the season.

3. Situation: The fake punt came with 13:21 left in the first quarter on fourth-and-9 from the Kansas City 30, after a penalty erased an initial punt. Araiza ran 12 yards for the first down and kept the possession alive. Later, with 1:26 left and Kansas City protecting a 30-27 lead, he dropped a 52-yard punt at the Las Vegas 1. That forced the Raiders to begin the potential game-winning drive 99 yards from the end zone.

4. Expectations: Araiza entered the week averaging more than 55 yards per punt, so raw distance was already part of his value. What stood out against Las Vegas was control. He traded some gross average for field position and still produced one of the game’s most consequential hidden-yardage performances.

Takeaway: Araiza did not score a point, but he repeatedly made Las Vegas play on a longer field. In a three-point road win, that is not background work. It is part of the reason the Chiefs survived.

My Take

The easiest version of this game to remember is Walker’s rushing total and Thornton’s breakout. That would miss what made the win interesting. Kansas City won because several different forms of value stacked together: Walker created explosive runs, Thornton converted high-leverage targets, Karlaftis produced pressure without sacks, and Araiza controlled field position. Even the Royals section matters because it shows where the next layer of the offense has to come from as injuries change the receiver rotation.

The Chiefs did not dominate the Raiders. They were outgained, lost the time-of-possession battle badly, and needed a frantic fourth quarter. But the best players in the biggest moments did enough. That is a much more useful takeaway than simply calling the win “clutch.”