Brewers survive Game 1, 3–2: record heat and the questions for Game 2

Milwaukee opened the World Series with a 3–2 win over Tampa Bay on Friday night, combining Jacob Misiorowski’s record-setting velocity with an early lead, a seventh-inning insurance run and a final strikeout that stranded the potential tying and winning runs. The Brewers lead the best-of-seven championship series 1–0. Saturday’s second game brings a different starting matchup and a clear question: can the Rays convert pressure into runs before Milwaukee’s late relievers take control again?

The result and inning-by-inning reconstruction below come from MLB’s official Game 1 record. The first pitch made the night memorable, but the complete scorebook explains why the game remained unsettled until its last batter.

Two first-inning runs changed the assignment

Milwaukee’s offense did its first damage before Tampa Bay starter Nick Martinez completed an inning. Christian Yelich tripled to bring home Jackson Chourio, then scored on William Contreras’s single. Those were connected hits that turned a runner into an immediate lead, rather than a home run producing all the scoring at once.

The two-run start mattered beyond the scoreboard. It gave Misiorowski room to work through Tampa Bay’s early contact without pitching from behind. It also meant Martinez had to prevent the game from expanding while waiting for his own lineup to answer. Neither assignment required a spectacular offensive night from that point; both demanded that isolated opportunities be handled cleanly.

Martinez recovered to complete five innings with two runs allowed, five hits, five strikeouts and no walks. His final line is an important qualification to the early damage. The Brewers did not keep scoring against him throughout the evening. After the opening inning, he gave Tampa Bay four scoreless innings and preserved a close contest.

A record fastball, followed by a workable start

Misiorowski’s first actual pitch was recorded at 103.5 mph in the official feed. MLB calls the opener a pitch-tracking-era Series record.

The pitch was a ball, not an out. Its speed described the starter’s unusual weapon; the next five innings showed the broader job he had to do. Misiorowski allowed four hits and one walk while striking out three. He threw 78 pitches, including 56 strikes, and left Milwaukee ahead 2–1.

Those numbers resist a simple “overpowering equals strikeouts” reading. Tampa Bay put balls in play, and Milwaukee still obtained the outs it needed. A pitcher can win important innings through a mixture of velocity, contact management and fielding support. Three strikeouts do not diminish a five-inning, one-run start, but they do show why evaluating the outing requires more than replaying its fastest moment.

For the next game, the practical lesson is not that another starter must reproduce 103.5 mph. It is that Milwaukee established an advantage and protected it through the middle of the order and the middle of the game. Tampa Bay’s response must address scoring opportunities, not merely the spectacle of the opening radar reading.

Tampa Bay answered, but never drew level

The Rays’ first run arrived in the fourth. Liam Hicks grounded out as Jonathan Aranda scored, cutting the deficit to 2–1. Turning an out into a run is useful when a team is behind, yet it also uses one of the inning’s limited chances to continue the attack. Tampa Bay narrowed the margin without producing the hit that would erase it.

The official totals show a close game in contact as well as scoring: Milwaukee finished with eight hits and Tampa Bay seven. Neither club was charged with an error. Those totals do not make every hit equally valuable. The ordering of baserunners, the number of outs and the location of runners determined whether contact produced a run or merely extended an inning.

That distinction is central to a one-run result. A team can collect nearly as many hits as its opponent and still spend much of the evening chasing. Here, Milwaukee’s early sequence and its later run created two separate problems for Tampa Bay: first close the initial gap, then find another answer after the margin grew again.

The seventh-inning run was more than decoration

In the seventh, Chourio singled to right and Cooper Pratt scored, moving Milwaukee ahead 3–1. The play did not end the competitive portion of the game. It changed the amount of damage Milwaukee could survive in the ninth.

Calling it an insurance run is particularly apt when the final margin is one. Tampa Bay later scored exactly once in its last inning. Without Milwaukee’s seventh-inning addition, that same run would have tied the score rather than merely brought the Rays within one. This is a comparison of the scoring sequence, not a claim that the rest of the game would necessarily have unfolded identically under a different score.

The Brewers also left eight runners on base overall, compared with four for the Rays. That figure identifies opportunities Milwaukee did not convert; it does not establish that its offense was inefficient in every important situation. The club produced three runs, and those runs were enough. Game 2 offers both teams a reason to examine which opportunities they created and which they allowed to disappear.

Milwaukee’s bridge to the ninth

Abner Uribe and Aaron Ashby supplied three scoreless innings between Misiorowski and Trevor Megill. Uribe recorded four outs on 15 pitches, allowing one hit and striking out two. Ashby recorded five outs on 20 pitches without allowing a hit or walk, striking out three.

Baseball’s innings notation needs a little care here. Uribe’s 1.1 innings means one inning plus one out, and Ashby’s 1.2 means one inning plus two outs. Together they provided nine outs, not a decimal calculation of 2.3 innings. Their work carried the original lead to the final inning while Milwaukee’s offense added its third run.

The recorded workloads are useful context for Saturday, but they are not a bullpen availability announcement. A pitch count alone cannot tell readers whether a reliever will be used on consecutive nights. Managers must weigh prior workload, recovery and the situation in front of them. The evidence from Friday establishes who pitched and how much, not an undisclosed plan for Game 2.

Why the finish remained dangerous

Megill allowed a run in the ninth and finished with two hits and a walk against him. The scoring play came on Hicks’s groundout, with Jorge Mateo crossing the plate. The official account records replay review during that sequence. By the time Jonny DeLuca came up for the final confrontation, Tampa Bay still had runners at second and third.

That positioning made the threat tangible. A hit could have changed the lead; a strikeout would end it. Megill struck DeLuca out swinging, preserving the 3–2 score. The closing line therefore contains both the pressure Milwaukee allowed and the decisive out it secured. It would be misleading to describe the ninth as comfortable, or to treat a completed save as proof that Tampa Bay never seriously threatened.

What to watch in Game 2

MLB’s Saturday schedule lists Rasmussen for Tampa Bay and Henderson for Milwaukee at American Family Field. First pitch is scheduled for 8 p.m. Eastern, which is 7 p.m. Central in Milwaukee. The official listing is a preview, not a final lineup or guarantee that the probable starters cannot change.

Three questions follow directly from the opener. Can Tampa Bay avoid another immediate deficit? Can Milwaukee produce an additional scoring sequence rather than rely on its first inning? And if the score is close again late, which team turns a baserunner into a run before the final out arrives?

One victory changes the series position without settling those questions. Milwaukee needs three more wins for the championship; Tampa Bay needs four. Game 1 showed that extraordinary velocity and ordinary execution can matter in the same evening. Game 2 will test the execution with a new pair of starters and no obligation to repeat Friday’s script.