New York Yankees at Kansas City Royals: Final Score & Recap
Line Score
| Team | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | R | H | E |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| NYY | 4 | 1 | 4 | 0 | 1 | 0 | 1 | 2 | 2 | 15 | 24 | 0 |
| KC | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 6 | 0 |
The Story
The New York Yankees battered the Kansas City Royals 15-1 at Kauffman Stadium on May 26, 2026, producing a 24-hit performance that left little doubt from the opening frame. The DiamondIQ model entered the game giving Kansas City a 34% chance of winning at home, but that number collapsed almost immediately and finished at 0%, reflecting how thoroughly New York controlled the contest from wire to wire. The Yankees struck for four runs in the first inning and added four more in the third, building a lead the Royals never threatened.
The most consequential swing in win probability came from the Kansas City side of the ledger, where the Royals' failure to generate any offense in the early innings effectively ended the game's competitive window. Nick Loftin's strikeout to end the bottom of the second against Cam Schlittler carried a win-probability swing of negative 7.7%, the single largest play of the game, and Salvador Perez's groundout to conclude the bottom of the first had already cost Kansas City 5.0% in win probability against Schlittler. New York's offense contributed its own decisive moments, with Paul Goldschmidt posting the top batting WPA at plus 4.8% and Anthony Volpe adding a home run off Bailey Falter in the second inning worth plus 2.7% in win probability. Jazz Chisholm Jr. also registered plus 3.6% WPA on a lineout that, in context, reflected how thoroughly New York was suppressing Kansas City's chances with every plate appearance.
Cam Schlittler was the standout performer of the night by a wide margin, accumulating plus 14.5% WPA to lead all pitchers and serving as the primary engine behind New York's dominance on the mound. The Royals managed only six hits across nine innings against a Yankees pitching staff that allowed nothing to escalate, finishing with no errors on either side. The final run differential of 14 matched the lopsided nature of a game that the DiamondIQ model's estimate had already priced as nearly certain by the middle innings.