Kansas City Chiefs vs Washington Commanders Match Player Stats
The kansas city chiefs vs washington commanders match player stats from the October 28, 2025, NFL matchup tell the story of a convincing 28-7 Kansas City Chiefs victory. The Chiefs combined efficient passing, productive rushing, and timely defensive plays to secure a 21-point win over the Washington Commanders. Patrick Mahomes delivered three touchdown passes, Travis Kelce finished just short of the 100-yard mark, and Kareem Hunt added a rushing touchdown. Washington showed flashes of offensive potential through Marcus Mariota and receiver Jeremy McNichols, but the Commanders struggled to sustain scoring drives after halftime.
This game is especially useful for understanding how passing efficiency, rushing production, turnovers, and second-half adjustments can shape an NFL result. Kansas City finished with 299 passing yards and 148 rushing yards, while Washington recorded 213 passing yards and 60 rushing yards. The difference was not simply the final score. Kansas City generated more offensive production, spread the ball among multiple playmakers, and scored 21 unanswered points in the second half. The following breakdown examines the key player performances, team statistics, scoring progression, and tactical lessons from the matchup.
Kansas City Chiefs vs Washington Commanders Match Player Stats: Game Overview
The Chiefs entered this matchup looking to strengthen their position in the AFC, while Washington aimed to improve its record with a competitive road performance. The supplied ESPN box-score data records Kansas City as the home team and Washington as the visiting team.
| Game Information | Details |
| Matchup | Washington Commanders vs Kansas City Chiefs |
| Date | October 28, 2025 |
| Venue designation | Kansas City home game |
| Final score | Chiefs 28, Commanders 7 |
| Winning team | Kansas City Chiefs |
| Winning margin | 21 points |
| Chiefs record listed | 5-3 overall, 4-1 at home |
| Commanders record listed | 3-5 overall, 1-4 away |
| Kansas City quarterback | Patrick Mahomes |
| Washington quarterback | Marcus Mariota |
| Game status in supplied data | Final |
Kansas City’s 21-point victory reflected a strong all-around performance. The offense produced consistently through the air and on the ground, while the defense recorded two interceptions and limited Washington to seven points.
The most important turning point came after halftime. Both teams scored seven points in the second quarter, leaving the contest tied 7-7 at the break. Kansas City then scored 14 points in the third quarter and seven more in the fourth. Washington failed to add another point.
Data note: This article analyzes the statistics supplied for the October 28, 2025, game. The figures below are based on that dataset and have not been independently reconciled against every original play-by-play entry. The supplied box-score extraction may contain inconsistencies in certain team totals or individual rows, so totals and individual statistics should be interpreted in that context.
Patrick Mahomes vs Marcus Mariota: Quarterback Comparison
Quarterback performance provides one of the clearest ways to understand the outcome. Patrick Mahomes produced more passing yards, more touchdown passes, and a higher passer rating than Marcus Mariota. Both quarterbacks threw two interceptions according to the supplied statistics, but Kansas City created more scoring opportunities and maintained a much stronger offensive rhythm.
| Passing Statistic | Patrick Mahomes | Marcus Mariota |
| Completions | 25 | 21 |
| Pass attempts | 34 | 30 |
| Completion percentage | 73.5% | 70.0% |
| Passing yards | 299 | 213 |
| Yards per attempt | 8.8 | 7.1 |
| Passing touchdowns | 3 | 1 |
| Interceptions | 2 | 2 |
| Sacks taken | 3 | 2 |
| Sack yardage | 15 | 13 |
| QBR listed | 56.4 | 55.2 |
| Passer rating | 104.9 | 73.3 |
Patrick Mahomes: Efficient Production and Three Touchdown Passes
Mahomes completed 25 of 34 passes for 299 yards and three touchdowns. His completion percentage of approximately 73.5% shows that he consistently connected with his receivers, while his 8.8 yards per attempt indicates that Kansas City gained meaningful yardage from its passing opportunities.
His three touchdown passes were central to the Chiefs’ offensive success. Kansas City did not rely on a single receiver to generate production. Travis Kelce, Rashee Rice, and Xavier Worthy all contributed as pass catchers, giving the offense different options for moving the chains and creating scoring opportunities.
The 299-yard performance also placed Mahomes close to the 300-yard threshold. Although the difference between 299 and 300 yards has little tactical significance, the number illustrates how consistently Kansas City moved the football through the air.
There is an important qualification: Mahomes also threw two interceptions. A strong final score does not mean every decision was successful. Turnovers can create opportunities for opponents, and they remain an area worth examining even in a convincing victory.
The decisive factor was that Mahomes combined his touchdown production with enough passing efficiency to help Kansas City build a substantial lead. His passing performance worked alongside a productive rushing attack rather than carrying the offense alone.
Marcus Mariota: A Competitive First Half but Limited Scoring
Mariota completed 21 of 30 passes for 213 yards and one touchdown. His 70% completion rate was respectable, and his 7.1 yards per attempt suggests that Washington found some opportunities to move the ball through the air.
However, the final result highlights the difference between completing passes and building a consistently productive offense. Washington scored only once, and its passing game did not generate another touchdown after the second quarter.
Mariota’s two interceptions also hurt Washington’s ability to sustain momentum. Although Kansas City recorded the same number of interceptions as Washington in the supplied data, the Chiefs converted their broader offensive advantage into four touchdowns.
Mariota’s performance should not be judged exclusively by the final score. Quarterback production depends on protection, receiver separation, rushing support, field position, and play-calling. Nevertheless, the available figures show that Washington needed more explosive plays and greater scoring consistency to challenge Kansas City.
What the Quarterback Numbers Reveal
Three differences stand out:
- Passing yardage: Mahomes produced 86 more passing yards than Mariota.
- Touchdown production: Kansas City’s quarterback threw two more touchdown passes.
- Passing efficiency: Mahomes recorded 8.8 yards per attempt compared with Mariota’s 7.1.
Both quarterbacks recorded two interceptions, which means interception count alone cannot explain the result. The larger distinction was Kansas City’s ability to generate more yards and convert offensive possessions into points.
Kansas City Chiefs Rushing Stats
Kansas City’s rushing game helped balance the offense and made the Chiefs less dependent on passing alone. The supplied team figures credit Kansas City with 30 carries for 148 yards, averaging 4.9 yards per attempt and scoring one rushing touchdown.
| Kansas City Rusher | Carries | Rushing Yards | Touchdowns |
| Isiah Pacheco | 12 | 58 | 0 |
| Kareem Hunt | 9 | 40 | 1 |
| Patrick Mahomes | 4 | 30 | 0 |
| Rashee Rice | 2 | 12 | 0 |
| Brashard Smith | 3 | 8 | 0 |
| Team total supplied | 30 | 148 | 1 |
Isiah Pacheco Sets the Foundation
Pacheco led the listed Kansas City rushers with 58 yards on 12 carries. His average of approximately 4.8 yards per carry provided a productive base for the offense.
A running back’s value cannot be measured by yardage alone. Successful runs can keep an offense on schedule, reduce the pressure on the quarterback, and create more manageable situations on later downs. Pacheco’s workload gave Kansas City a dependable ground option while the passing game targeted the Commanders’ defense.
His 58-yard performance was not an overwhelming individual total, but it contributed to a team rushing output that made Kansas City’s offense more difficult to defend.
Kareem Hunt Adds a Crucial Touchdown
Hunt recorded 40 yards on nine carries and scored one rushing touchdown. His role was particularly important because a rushing score complements passing touchdowns and gives the offense another way to finish drives.
When a team can threaten through the air and on the ground, defenders must account for more possibilities. That can make it harder to focus entirely on the quarterback or the primary receiving targets.
Hunt’s touchdown was one component of Kansas City’s four-touchdown performance. His contribution also demonstrates why backup and rotational players matter: an offense can benefit from multiple runners performing specific roles instead of placing the entire burden on one player.
Patrick Mahomes Adds Mobility
Mahomes recorded four carries for 30 rushing yards in the supplied figures. His mobility added another element to Kansas City’s offense.
Quarterback rushing can punish defensive coverage when defenders turn their attention toward receivers. It can also help an offense escape pressure and gain valuable yards when passing options are unavailable.
The supplied data does not establish how each individual run occurred, so it would be inaccurate to attribute all of Mahomes’ rushing production to designed runs or scrambles. The broader point is that his ground contribution gave Washington another dimension to consider.
Washington Commanders Rushing Stats
Washington recorded 20 team carries for 60 yards, averaging 3.0 yards per carry with no rushing touchdowns. This was one of the clearest statistical differences between the teams.
| Washington Rusher | Carries | Rushing Yards |
| Marcus Mariota | 8 | 28 |
| Jacory Croskey-Merritt | 9 | 25 |
| Jeremy McNichols | 1 | 4 |
| Chris Rodriguez Jr. | 1 | 2 |
| Deebo Samuel Sr. | 1 | 1 |
| Team total supplied | 20 | 60 |
Marcus Mariota Leads Washington in Rushing
Mariota led Washington’s listed rushers with 28 yards on eight carries. His average of 3.5 yards per carry gave the Commanders some additional production outside the passing game.
However, relying on a quarterback for a significant portion of rushing production can create challenges. Quarterbacks may be forced to scramble when protection breaks down or passing options are covered, and those situations do not always produce reliable gains.
The available statistics do not identify the circumstances of every carry. Even so, Washington’s overall rushing average of 3.0 yards per attempt indicates that the ground attack struggled to generate consistent forward progress.
Jacory Croskey-Merritt’s Contribution
Croskey-Merritt finished with 25 rushing yards on nine carries, averaging approximately 2.8 yards per carry. That production was limited relative to the workload.
Washington needed its running game to do more than consume plays. A productive rushing attack can help keep a defense honest, create manageable third downs, and reduce the burden on the passing game. With only 60 rushing yards as a team, the Commanders had fewer opportunities to use the ground game as a consistent offensive foundation.
Why the Rushing Gap Mattered
Kansas City gained 148 rushing yards, compared with Washington’s 60. That created an 88-yard advantage on the ground.
The Chiefs also averaged 1.9 more yards per carry. Over an entire game, a difference of that size can influence drive length, down-and-distance situations, and how aggressively an offense can approach later downs.
Washington’s rushing production was not the only reason for the loss, but it made the Commanders more dependent on Mariota’s passing. Against a defense that recorded two interceptions, that imbalance became difficult to overcome.
Kansas City Chiefs Receiving Stats
Kansas City’s receiving group produced 299 yards, three receiving touchdowns, and an average of 12.0 yards per reception according to the supplied team figures. The leading contributors were Travis Kelce, Rashee Rice, and Xavier Worthy.
| Receiver | Receptions | Receiving Yards | Touchdowns |
| Travis Kelce | 6 | 99 | 1 |
| Rashee Rice | 9 | 93 | 1 |
| Xavier Worthy | 5 | 53 | 0 |
| JuJu Smith-Schuster | 2 | 29 | 0 |
| Noah Gray | 2 | 23 | 0 |
| Kareem Hunt | 1 | 2 | 0 |
| Team total supplied | 25 | 299 | 3 |
Travis Kelce Nearly Reaches 100 Receiving Yards
Kelce led the listed Kansas City receivers with 99 yards on six receptions and one touchdown. His average was 16.5 yards per catch, demonstrating the value of his ability to gain substantial yardage when targeted.
Kelce’s contribution was important because tight ends can create matchup problems for defenses. They may face linebackers in coverage, safeties in space, or defensive backs who must account for their size and route-running ability.
The supplied numbers show a highly productive outing, but they do not provide a complete target-by-target breakdown. It would therefore be inappropriate to claim that every reception came against a particular coverage or defender.
What the figures do support is straightforward: Kelce was Kansas City’s leading receiver by yardage and scored once. His production helped the Chiefs maintain a balanced passing attack.
Rashee Rice Delivers Nine Receptions
Rice recorded nine catches for 93 yards and one touchdown. His nine receptions were the highest total among the listed Kansas City pass catchers.
Rice averaged approximately 10.3 yards per reception. That figure is lower than Kelce’s average, but reception volume also matters. Repeated completions can sustain drives, help an offense control possession, and create opportunities for additional scoring plays.
Rice’s touchdown also meant that Kansas City had multiple receivers finding the end zone. Defenses cannot focus exclusively on one player when several options are producing meaningful results.
The supplied data lists a fumble by Rice, but it was not lost. That distinction matters when evaluating turnovers: a recorded fumble does not automatically mean the opposing team gained possession.
Xavier Worthy Provides Another Receiving Option
Worthy caught five passes for 53 yards, averaging 10.6 yards per reception. Although he did not score in the supplied statistics, his production helped spread the defensive workload.
A receiving corps with multiple productive players can force defenders to divide their attention. Kelce and Rice delivered the largest individual totals, while Worthy added another option for moving the ball.
This distribution was one of Kansas City’s offensive strengths. Mahomes did not need to rely on one player for every important completion, and the Chiefs could use different receivers to attack different areas of the field.
Kansas City’s Receiving Depth
JuJu Smith-Schuster recorded 29 yards on two catches, while Noah Gray added 23 yards on two receptions. Kareem Hunt contributed one catch for two yards.
These smaller totals should not be confused with a lack of value. Short receptions can help convert third downs, extend drives, or create favorable situations for the next play. However, the supplied box-score data does not include the down, distance, or result of each catch, so the precise situational impact of these receptions cannot be confirmed.
The overall picture is clear: Kansas City combined high-volume production from Rice with substantial yardage from Kelce and contributions from several other targets.
Washington Commanders Receiving Stats
Washington’s receiving production was led by Jeremy McNichols and Terry McLaurin. McNichols recorded the highest receiving yardage total for the Commanders in the supplied data, while McLaurin scored Washington’s only touchdown.
| Receiver | Receptions | Receiving Yards | Touchdowns |
| Jeremy McNichols | 5 | 64 | 0 |
| Terry McLaurin | 3 | 54 | 1 |
| Luke McCaffrey | 3 | 24 | 0 |
| John Bates | 1 | 22 | 0 |
| Ben Sinnott | 1 | 22 | 0 |
| Zach Ertz | 4 | 16 | 0 |
| Deebo Samuel Sr. | 3 | 11 | 0 |
| Team total supplied | 21 | 213 | 1 |
Jeremy McNichols Leads Washington in Receiving
McNichols caught five passes for 64 yards, averaging 12.8 yards per reception. His receiving total led all listed Washington players.
His production is a reminder that passing-game contributions can come from several positions, including running backs. A back who catches passes can offer the quarterback another option when deeper routes are unavailable or when the defense leaves space underneath.
The available figures do not establish whether McNichols’ receptions came primarily from checkdowns, screens, or conventional receiving routes. What they do show is that he was Washington’s most productive receiver by yardage in this matchup.
Terry McLaurin Scores the Commanders’ Only Touchdown
McLaurin recorded three receptions for 54 yards and one touchdown. He averaged 18.0 yards per catch, the highest average among the listed Washington receivers with more than one reception.
His touchdown accounted for Washington’s only scoring play in the supplied quarter-by-quarter breakdown. The performance demonstrates that the Commanders could still generate meaningful receiving production despite the final result.
However, three receptions were not enough to change the direction of the game. Washington needed more consistent scoring opportunities and additional production from the offense after halftime.
McLaurin’s contribution should therefore be viewed in two ways: he was an effective individual target, but his production did not translate into a sustained team scoring threat.
Washington’s Supporting Receivers
Luke McCaffrey caught three passes for 24 yards, while John Bates and Ben Sinnott each recorded 22 yards on one reception. Zach Ertz added four catches for 16 yards, and Deebo Samuel Sr. recorded three receptions for 11 yards.
These numbers show a range of contributions, but they also reveal the limits of Washington’s passing production. Outside McNichols and McLaurin, the listed yardage totals were modest.
Ertz’s four catches, for example, indicate involvement in the passing game, although his 16 yards resulted in a relatively low average of four yards per reception. A high reception count does not always mean high offensive impact; the value depends on yardage, down, distance, and whether the play helps sustain a drive.
Comparing the Receiving Units
Kansas City recorded 299 receiving yards and three receiving touchdowns, compared with Washington’s 213 yards and one touchdown.
The 86-yard difference matched the gap in passing yardage because the supplied receiving totals correspond to each team’s reported passing output. More importantly, Kansas City converted its receiving production into three touchdowns, while Washington produced one.
That difference in finishing drives was central to the outcome. Washington had productive individual receivers, but Kansas City’s passing attack generated more scoring.
Defensive Player Stats and Turnover Analysis
The defensive figures reveal an interesting contrast. Washington recorded more total tackles and one more sack than Kansas City, yet the Chiefs won comfortably. This is an important reminder that defensive activity does not always translate into scoreboard control.
| Defensive Statistic | Washington | Kansas City |
| Total tackles | 71 | 64 |
| Solo tackles | 48 | 28 |
| Sacks | 3 | 2 |
| Tackles for loss | 4 | 3 |
| Passes defended | 3 | 3 |
| Quarterback hits | 7 | 4 |
| Interceptions | 2 | 2 |
| Defensive touchdowns | 0 | 0 |
Washington Defensive Leaders
| Player | Total Tackles | Solo Tackles |
| Quan Martin | 14 | 10 |
| Bobby Wagner | 10 | 7 |
| Jeremy Reaves | 7 | 6 |
Martin led Washington with 14 tackles, including 10 solo tackles. Wagner recorded 10 tackles and seven solo tackles, while Reaves finished with seven tackles and six solo tackles.
High tackle totals can indicate that a defender was heavily involved in stopping plays. However, they can also reflect the amount of time an opponent spent on offense or how frequently a defense had to make a stop after a completed pass or run.
Washington’s tackle totals therefore need to be considered alongside the final score and Kansas City’s offensive production. The Commanders recorded three sacks and seven quarterback hits, but they still allowed 28 points.
Kansas City Defensive Leaders
| Player | Total Tackles | Solo Tackles |
| Chamarri Conner | 10 | 5 |
| Drue Tranquill | 6 | 4 |
| Nick Bolton | 6 | 1 |
Conner led Kansas City’s listed defenders with 10 tackles. Tranquill recorded six, and Bolton also finished with six.
The Chiefs’ defensive value was not limited to tackling. Kansas City intercepted two passes and restricted Washington to one touchdown. Those outcomes helped offset Washington’s higher tackle and sack totals.
Interceptions: Two for Each Team
The supplied data credits both defenses with two interceptions.
Washington’s interceptions were recorded by Bobby Wagner and Marshon Lattimore. Wagner’s interception return covered one yard, while Lattimore’s return was listed at zero yards.
Kansas City’s interceptions were credited to Mike Danna and Jack Cochrane. Danna returned his interception for 10 yards, while Cochrane’s return was listed at zero yards.
Neither defense returned an interception for a touchdown. The figures also show that the Chiefs gained 10 interception-return yards compared with Washington’s one.
Because both teams recorded two interceptions, the difference in the final score cannot be explained by interception count alone. Kansas City had the stronger combined passing and rushing output, which gave it more opportunities to score despite the turnovers.
Tackles, Sacks, and Defensive Effectiveness
Washington’s three sacks compared with Kansas City’s two, and the Commanders recorded seven quarterback hits compared with four for the Chiefs.
Those numbers suggest Washington generated pressure and defensive involvement. Still, pressure statistics need context. A sack may end a promising drive, while a quarterback hit can disrupt timing, but neither guarantees a turnover or prevents a scoring play.
Kansas City’s defense was effective in a different way: it limited Washington to seven points and helped preserve the advantage created by the offense. A complete defensive assessment would also require drive-level data, third-down results, red-zone performance, and the timing of turnovers. Those details are not fully provided in the supplied dataset.
Quarter-by-Quarter Scoring Breakdown
The scoring progression shows how the contest changed after halftime.
| Quarter | Washington Commanders | Kansas City Chiefs |
| First quarter | 0 | 0 |
| Second quarter | 7 | 7 |
| Third quarter | 0 | 14 |
| Fourth quarter | 0 | 7 |
| Final score | 7 | 28 |
First Quarter: A Scoreless Opening
Neither team scored in the first quarter according to the supplied data. A scoreless opening can result from several factors, including defensive stops, missed scoring opportunities, or offenses taking time to establish their preferred plays.
The available quarter totals do not identify the exact reason for the scoreless period. It would therefore be speculative to attribute the opening exclusively to conservative play-calling or defensive dominance.
What matters is that neither team gained an early scoreboard advantage.
Second Quarter: Both Teams Reach the End Zone
Washington and Kansas City each scored seven points in the second quarter. The game was tied 7-7 at halftime, leaving the outcome open.
Washington’s touchdown was the team’s only score in the game. McLaurin’s receiving touchdown is identified in the supplied player statistics, while Kansas City’s scoring included Mahomes’ passing production.
The tied halftime score makes the second-half difference particularly important. Kansas City did not win because it established an early lead and simply protected it. The Chiefs created separation through their performance after the break.
Third Quarter: Kansas City Takes Control
Kansas City scored 14 unanswered points in the third quarter. Washington failed to score, and the Chiefs moved from a tied game to a 21-7 lead.
This was the most decisive quarter in the supplied scoring breakdown. A two-touchdown swing can change the way both offenses approach the remainder of a game. The team leading can lean on its rushing attack, while the trailing team may need to pass more often to recover the deficit.
The supplied data does not identify every play that created this scoring run. Still, the final quarter totals clearly establish that Kansas City produced the game’s most important scoring stretch in the third quarter.
Fourth Quarter: The Chiefs Complete the Victory
Kansas City added seven more points in the fourth quarter, bringing the final score to 28-7. Washington remained scoreless for the second consecutive quarter.
The Chiefs’ 21 unanswered second-half points transformed a competitive first half into a decisive result. Their ability to continue scoring while limiting Washington’s offense was the clearest measure of control.
Team Statistics Comparison
The team-level numbers explain why Kansas City finished with a comfortable victory.
| Team Statistic | Washington | Kansas City |
| Passing yards | 213 | 299 |
| Rushing yards | 60 | 148 |
| Total passing and rushing yards | 273 | 447 |
| Rushing attempts | 20 | 30 |
| Average yards per carry | 3.0 | 4.9 |
| Receiving touchdowns | 1 | 3 |
| Rushing touchdowns | 0 | 1 |
| Total points | 7 | 28 |
| Interceptions recorded by defense | 2 | 2 |
Kansas City Wins the Yardage Battle
Using the supplied passing and rushing figures, Kansas City produced 447 combined passing and rushing yards. Washington produced 273.
That is a difference of 174 yards. Kansas City gained more yardage through both major offensive channels, rather than relying on one unusually productive category.
The Chiefs’ advantage was especially pronounced on the ground. They gained 148 rushing yards compared with Washington’s 60. The 88-yard rushing gap accounted for a large portion of the overall difference.
Why Balanced Offense Matters
A balanced offense can force a defense to prepare for multiple threats. If a team runs effectively, defenders may need to commit additional resources to stopping the ground game. That can create opportunities for passes, while successful passing can make it more difficult for the defense to concentrate on the running back.
Kansas City demonstrated this balance through Mahomes’ 299 passing yards and the team’s 148 rushing yards. Washington’s 213 passing yards were respectable, but its 60 rushing yards provided less support.
The statistics do not prove that one particular formation or scheme caused the difference. They do show that Kansas City generated more total production across the two main offensive categories.
Scoring Efficiency Was the Biggest Difference
Yardage is valuable, but points determine the winner. Kansas City scored four touchdowns according to the supplied scoring and touchdown figures: three through the air and one on the ground. Washington scored one receiving touchdown.
That difference in scoring output explains more about the final result than tackle totals or interception counts alone. The Chiefs converted their offensive production into points and prevented Washington from responding in the second half.
Special Teams and Kicking Statistics
Special teams did not dominate the supplied statistical story, but the figures provide a fuller picture of the game.
| Special Teams Category | Washington | Kansas City |
| Kick returns | 3 | 2 |
| Kick-return yards | 67 | 46 |
| Average kick-return yards | 22.3 | 23.0 |
| Punt returns | 1 | 2 |
| Punt-return yards | 14 | 13 |
| Field goals made | 0 | 0 |
| Extra points made | 1 | 4 |
| Punts | 3 | 1 |
| Total punt yards | 142 | 56 |
| Average punt distance | 47.3 | 56.0 |
Kick Returns
Luke McCaffrey led Washington’s listed kick-return figures with one return for 37 yards. Jaylin Lane recorded two returns for 30 yards combined. Washington finished with 67 kick-return yards.
Kansas City’s Nikko Remigio recorded two returns for 46 yards, averaging 23 yards per return.
Washington gained more total kick-return yardage because it had three returns rather than two. Kansas City, however, had a slightly higher average per return. These figures describe field-position contributions but do not establish where each return ended or how many points followed.
Punt Returns
Lane recorded one punt return for 14 yards for Washington. Remigio returned two punts for 13 yards combined for Kansas City.
Washington therefore had the longer total punt-return figure despite making fewer returns. Return yardage is only one part of special-teams value, and the available statistics do not provide enough detail to assess blocking, penalties, or resulting field position.
Kicking and Punting
Matthew Wright made one extra point for Washington, while Harrison Butker made four for Kansas City. Neither team attempted a field goal in the supplied figures.
Tress Way punted three times for Washington, averaging 47.3 yards per punt. Matt Araiza punted once for Kansas City for 56 yards.
The difference in punt volume is consistent with the broad game narrative: Kansas City generated more offensive production, while Washington had more limited opportunities to sustain drives. However, punt totals alone cannot establish the exact cause of each stalled possession.
What Decided the Chiefs’ 28-7 Victory?
Several factors combined to produce the final result. No single player statistic explains the entire game, but the strongest evidence points to three major differences.
1. Kansas City Generated More Total Offense
The Chiefs recorded 447 combined passing and rushing yards, compared with Washington’s 273. This 174-yard advantage shows that Kansas City consistently produced more offense across the game.
Mahomes’ 299 passing yards gave the Chiefs a reliable source of production, while Pacheco and Hunt helped the ground game contribute 148 yards.
Washington’s offense was less balanced. Mariota passed for 213 yards, but the team gained only 60 rushing yards.
2. The Chiefs Scored More Touchdowns
Kansas City recorded three passing touchdowns and one rushing touchdown in the supplied data. Washington scored once through the air and did not record a rushing touchdown.
Touchdowns reflect the ability to turn offensive opportunities into meaningful scoreboard gains. Although both teams had two interceptions, Kansas City created substantially more scoring production.
3. Kansas City Controlled the Second Half
The teams were tied at 7-7 at halftime. Kansas City then outscored Washington 21-0 over the final two quarters.
That second-half difference was decisive. Washington’s offense did not score in either the third or fourth quarter, while Kansas City scored twice in the third and once in the fourth.
The figures establish the timing of the scoring difference, although they do not independently identify every coaching adjustment, coverage change, or individual play responsible for it.
Key Takeaways for NFL Fans and Fantasy Football Readers
The statistical record offers several practical lessons for readers evaluating individual performances.
- Quarterback output needs context. Mahomes’ three touchdown passes and 299 yards were central to the victory, but his two interceptions also matter when assessing decision-making.
- Receiving volume and receiving efficiency are different. Rice led Kansas City with nine catches, while Kelce led the listed receivers with 99 yards.
- Rushing production can support passing success. Kansas City’s 148 rushing yards provided a stronger ground contribution than Washington’s 60.
- A single productive receiver cannot guarantee a team victory. McLaurin scored Washington’s only touchdown, but the Commanders did not sustain their scoring after halftime.
- Defensive statistics must be interpreted together. Washington recorded more tackles and sacks, yet Kansas City allowed fewer points and generated two interceptions.
- Game script matters. A tied halftime score followed by a 21-point second-half advantage tells a different story from a game in which one team dominates from the opening quarter.
For fantasy football analysis, the listed receiving totals identify Kelce, Rice, and McNichols as notable contributors. However, fantasy points depend on the scoring system, bonuses, and any additional categories such as fumbles lost. The figures here should not be treated as a complete fantasy scoring calculation.
How to Read NFL Box Scores More Accurately
A box score is a useful starting point, but the best analysis combines individual statistics with team totals and scoring progression.
Start With the Final Score and Quarter Breakdown
The final score tells you who won. The quarter-by-quarter breakdown explains when the game changed. In this matchup, the tied halftime score and Kansas City’s 21-point second-half run are essential to understanding the result.
Compare Passing and Rushing Together
Looking at passing yards alone would miss Kansas City’s advantage on the ground. Likewise, rushing totals without passing figures would fail to show the scale of Mahomes’ contribution.
Combining passing and rushing yards provides a more complete view of offensive production, although it is not a substitute for official total-offense figures that may also account for sacks and other categories differently.
Separate Individual Statistics From Team Totals
A player’s row may show a contribution that does not reconcile perfectly with an extracted team total. This can happen when webpage tables are copied or formatted incorrectly.
For example, the supplied receiving rows for Washington do not fully reconcile with every displayed team figure. Analysts should verify questionable numbers against the official box score before publishing highly precise comparisons or using the data for betting and statistical modeling.
Avoid Treating Every Statistic as Equally Important
A high tackle count does not automatically mean a defense played better. A high completion percentage does not necessarily mean a quarterback created enough explosive plays. Similarly, a long punt does not prove that special teams controlled field position.
The strongest conclusions come from connecting several measures. In this game, the combination of offensive yardage, touchdown production, and second-half scoring provides a more persuasive explanation than any one isolated statistic.
Authoritative Source and Further Reading
For the original game record, consult the ESPN NFL box score for Chiefs vs Commanders. It is the relevant reference for checking the listed passing, rushing, receiving, defensive, and special-teams statistics.
Readers who want to go beyond a traditional box score should compare the official game summary with play-by-play data. That approach helps identify when a touchdown occurred, how a drive developed, and whether a player gained yards in a high-pressure situation or during a less decisive part of the game.
Frequently Asked Questions
1. What was the final score of the Kansas City Chiefs vs Washington Commanders game?
The supplied box-score data lists the Kansas City Chiefs as 28-7 winners over the Washington Commanders on October 28, 2025. Kansas City won by 21 points.
2. How many passing yards did Patrick Mahomes record?
Patrick Mahomes recorded 299 passing yards, completing 25 of 34 attempts with three touchdown passes and two interceptions, according to the supplied statistics.
3. How did Marcus Mariota perform against Kansas City?
Marcus Mariota completed 21 of 30 passes for 213 yards and one touchdown. He also threw two interceptions and recorded 28 rushing yards on eight carries.
4. Who led the Chiefs in receiving yards?
Travis Kelce led the listed Kansas City receivers with 99 receiving yards on six receptions and one touchdown. Rashee Rice followed with 93 yards on nine catches and one touchdown.
5. Which Washington player led the team in receiving yards?
Jeremy McNichols led Washington’s listed receivers with five receptions for 64 yards. Terry McLaurin recorded 54 receiving yards and Washington’s only listed receiving touchdown.
6. What was the biggest statistical difference between the teams?
Kansas City recorded 447 combined passing and rushing yards, compared with Washington’s 273, based on the supplied figures. The Chiefs also scored 21 unanswered points in the second half, which was decisive in the 28-7 result.
Conclusion
The Kansas City Chiefs’ 28-7 victory over the Washington Commanders was defined by stronger overall offensive production and a decisive second-half performance. Patrick Mahomes threw for 299 yards and three touchdowns, Travis Kelce and Rashee Rice both reached significant receiving totals, and Kareem Hunt added a rushing touchdown. Kansas City’s 148 rushing yards complemented its passing attack and helped the team build a 21-point advantage after halftime.
Washington produced some positive individual performances. Marcus Mariota passed for 213 yards, Jeremy McNichols led the team in receiving yards, and Terry McLaurin scored the Commanders’ only touchdown. The defense also recorded three sacks and two interceptions. Nevertheless, Washington’s 60 rushing yards and lack of second-half scoring limited its ability to remain competitive.
The central lesson from this matchup is that individual achievements must be considered alongside team production and game progression. Kansas City gained more yards, scored more touchdowns, and controlled the final two quarters. Those combined advantages provide the clearest statistical explanation for the result.
For anyone reviewing the kansas city chiefs vs washington commanders match player stats, the most informative approach is to examine quarterback efficiency, receiving contributions, rushing production, defensive turnovers, and quarter-by-quarter scoring together. Because the supplied dataset may contain extraction inconsistencies, readers should use the linked ESPN box score to verify any disputed individual or team total before relying on it for detailed statistical comparisons.
