The red sox vs st. louis cardinals match player stats from April 11, 2026, reveal how pitching control, timely hits, and situational execution shaped a close 3-2 victory for the St. Louis Cardinals. At Busch Stadium in St. Louis, the Cardinals collected eight hits and drew six walks, while the Boston Red Sox finished with five hits and no walks. St. Louis converted its opportunities into three runs, while Boston struggled to generate enough offense to take the lead.

The final score tells only part of the story. Boston recorded nine strikeouts as a pitching staff and held the Cardinals without a home run, yet St. Louis still found ways to score. The Cardinals also left 12 runners on base, showing that their victory was far from comfortable. Boston, meanwhile, received two hits from Wilyer Abreu and used aggressive baserunning to create pressure.

This breakdown covers the final score, individual batting performances, pitching statistics, scoring plays, and the key numbers that explain the result. All game-specific figures below are based on the supplied ESPN box score data.

Game Overview: Red Sox vs. St. Louis Cardinals

The Cardinals won 3-2 in a tightly contested game that lasted two hours and 38 minutes. Playing at home, St. Louis scored first in the second inning and added two important runs in the fifth. Boston tied the game in the fourth before the Cardinals regained the advantage.

Boston Red Sox

Away team

2 – 3

Final

St. Louis Cardinals

Home team

Date

April 11, 2026

Venue

Busch Stadium

Attendance

27,125

Game duration

2h 38m

Team Comparison

Statistical category	Boston Red Sox	St. Louis Cardinals
Runs	2	3
Hits	5	8
Errors	0	1
At-bats	32	30
Runs batted in	1	3
Home runs	0	0
Walks	0	6
Strikeouts	7	9
Left on base	5	12
Team batting with runners in scoring position	1-for-6	2-for-13
Pitching innings	8.0	9.0
Pitching strikeouts	9	7
Earned runs allowed	3	1

The most important difference was the Cardinals’ ability to reach base without recording a hit. Six walks gave St. Louis additional baserunners and more chances to score. Boston did a better job avoiding strikeouts at the plate, but its offense could not produce enough hits or walks to overcome the deficit.

The Cardinals also benefited from a complete nine-inning pitching performance. Boston’s pitchers recorded nine strikeouts, but the team allowed three runs and six walks.

Red Sox vs. St. Louis Cardinals Match Player Stats: Boston Batting

Boston’s offense recorded five hits across 32 at-bats. Wilyer Abreu led the team with two hits, while Masataka Yoshida and Marcelo Mayer also reached base with singles. Trevor Story scored a run and recorded Boston’s only RBI.

The Red Sox did not hit a home run or draw a walk. That combination limited their ability to build sustained rallies. Although Boston used its speed to put pressure on the Cardinals, it needed more consistent contact with runners in scoring position.

Boston Red Sox Batting Box Score

Player	Pos.	AB	R	H	RBI	BB	K
J. Duran	LF	4	0	0	0	0	0
C. Durbin	3B	3	0	0	0	0	1
M. Yoshida	DH	3	1	1	0	0	1
W. Contreras	1B	4	0	0	0	0	2
W. Abreu	RF	4	0	2	0	0	0
T. Story	SS	4	1	0	1	0	1
M. Mayer	2B	4	0	1	0	0	1
C. Narvaez	C	3	0	0	0	0	1
C. Rafaela	CF	3	0	1	0	0	0
Team total		32	2	5	1	0	7

Source data: supplied ESPN box score.

Wilyer Abreu Provides Boston’s Best Hit Total

Abreu finished with two hits in four at-bats, accounting for two of Boston’s five hits. His batting average was listed at .392, with a .415 on-base percentage and a .686 slugging percentage.

Those figures provide context for his individual performance, although they should not be confused with his statistics from this game alone. His two hits were a positive contribution, but the surrounding lineup could not turn enough opportunities into runs.

Abreu did not record an RBI or score a run. This illustrates the difference between reaching base and directly affecting the scoreboard. A batter can produce a strong individual result while the team’s overall offense remains limited.

Masataka Yoshida Helps Boston Get on the Scoreboard

Yoshida went 1-for-3 and scored one run. He finished with a .263 batting average, a .500 on-base percentage, and a .368 slugging percentage in the supplied data.

His fourth-inning run was important because it helped Boston draw level at 1-1. The scoring play came when Yoshida scored on a Cardinals throwing error.

That distinction matters when evaluating offensive performance. Yoshida contributed by reaching base and scoring, but the run was not recorded as an RBI for him. The defensive error played a direct role in allowing Boston to score.

Trevor Story Contributes a Run and an RBI

Story finished with no hits in four at-bats, but his final line included one run and one RBI. He also stole home during Boston’s fourth-inning baserunning sequence.

His performance shows why a batting line should not be judged by hits alone. A player can contribute through baserunning, defensive pressure, and productive opportunities even without recording a hit.

Story’s RBI was particularly important in a game decided by one run. Boston scored only twice, making every scoring contribution significant. His individual line also shows a .140 batting average and a .136 on-base percentage in the supplied figures, so the game-specific contribution should be considered separately from his broader season numbers.

Marcelo Mayer and Ceddanne Rafaela Add Singles

Mayer went 1-for-4 and stole second base. His single gave Boston another baserunner, while his stolen base demonstrated the team’s willingness to create opportunities through speed.

Rafaela also finished 1-for-3. He recorded a double according to the team extra-base-hit summary, while the individual batting line lists one hit. The supplied information does not identify an RBI or run scored for him.

Boston’s two stolen bases, credited to Story and Mayer, were an important part of its offensive approach. However, steals do not automatically translate into runs. Teams still need productive plate appearances or defensive mistakes to bring runners home.

Where Boston’s Offense Fell Short

Three figures help explain Boston’s difficulty scoring:

• Five hits: Boston recorded three fewer hits than St. Louis.
• Zero walks: The Red Sox did not receive a base on balls, limiting free baserunners.
• One hit in six opportunities with runners in scoring position: Boston struggled to deliver hits when runners were in scoring position.

The last figure is especially important. A team can record several hits but still score very little if those hits arrive with the bases empty. Boston’s offense needed a timely hit in one of its limited scoring opportunities.

The Red Sox also struck out seven times. That was fewer than the Cardinals’ nine strikeouts, but avoiding strikeouts was not enough to win. Contact quality, baserunner placement, and the timing of hits all influenced the result.

St. Louis Cardinals Batting Player Stats

St. Louis finished with eight hits, three runs, and six walks. The lineup’s ability to reach base was central to its victory, even though the Cardinals left 12 runners on base.

Ramón Urías scored twice, Jordan Walker collected two hits, and Thomas Saggese recorded an RBI single. José Fermín added a sacrifice fly that helped St. Louis extend its lead in the fifth inning.

Cardinals Batting Box Score

Player	Pos.	AB	R	H	RBI	BB	K
J. Wetherholt	2B	3	0	0	0	2	1
I. Herrera	DH	4	0	1	0	1	3
A. Burleson	1B	5	0	0	0	0	1
J. Walker	RF	4	1	2	0	0	1
R. Urias	3B	3	2	1	0	1	0
M. Winn	SS	0	0	0	0	1	0
T. Saggese	SS	2	0	1	1	0	0
J. Fermin	LF	3	0	1	1	0	2
N. Church	LF	0	0	0	0	0	0
P. Pages	C	4	0	1	0	0	1
V. Scott II	CF	2	0	1	1	1	0
Team total		30	3	8	3	6	9

Source data: supplied ESPN box score. Listed totals reflect the supplied team summary.

Ramón Urías Scores Twice

Urías was one of the Cardinals’ most influential players. He went 1-for-3, drew one walk, and scored twice. His supplied season line showed a .261 batting average, .346 on-base percentage, and .652 slugging percentage.

His importance came from his ability to get on base and cross home plate. Urías scored in the second inning and again during the fifth-inning scoring sequence. Those runs helped St. Louis establish the lead and then strengthen it after Boston had tied the game.

Urías did not receive an RBI in the supplied batting line. That is consistent with the distinction between scoring a run and driving in a teammate. His contribution was based on reaching base and advancing around the diamond.

Jordan Walker Produces Two Hits

Walker finished 2-for-4 with one run scored and one strikeout. His season figures were listed as a .313 batting average, .377 on-base percentage, and .667 slugging percentage.

His two hits gave the Cardinals another reliable source of contact. Walker also scored in the fifth inning after reaching base, contributing to the home team’s ability to regain control.

Although Walker did not record an RBI in this game, his hits helped keep the lineup moving. A multi-hit performance can be valuable even when the batter does not directly drive in a run.

Thomas Saggese Delivers a Key RBI Single

Saggese went 1-for-2 and drove in one run. His fifth-inning single scored Walker, giving St. Louis an important offensive contribution after Boston had tied the game.

This was one of the clearest examples of timely hitting in the game. Saggese did not need a home run or an extra-base hit. A single was enough because a runner was already in position to score.

His supplied season line showed a .258 batting average, .343 on-base percentage, and .323 slugging percentage. The game-specific RBI illustrates how situational value can differ from a player’s overall power numbers.

José Fermín Adds a Sacrifice Fly

Fermín finished 1-for-3 with one RBI and two strikeouts. His sacrifice fly scored Urías in the fifth inning.

A sacrifice fly is a useful measure of situational execution. The batter puts the ball in the air deep enough for a runner to tag up and score, even though the plate appearance does not produce a hit.

Fermín’s contribution helped St. Louis reach three runs without hitting a home run. In a low-scoring contest, that type of play can be decisive.

Victor Scott II Contributes to the First Run

Scott finished 1-for-2 and drew one walk. His sacrifice fly in the second inning allowed Urías to score the game’s first run.

The play gave St. Louis an early advantage and established the pattern that continued throughout the game: the Cardinals used baserunners and productive contact rather than relying on power hitting.

Scott’s supplied season batting average was .278. While his game line was modest, his sacrifice fly directly contributed to the final result.

Ivan Herrera and JJ Wetherholt Work the Count

Herrera recorded one hit and one walk in four at-bats, while Wetherholt drew two walks and did not record a hit. Both players struck out, and Herrera finished with three strikeouts.

Their walks helped St. Louis reach the six-walk team total. Walks can increase pitch counts, put pressure on pitchers, and create scoring chances without requiring a ball to land safely.

Wetherholt’s two walks were particularly useful in a game where the Cardinals generated only eight hits. They gave the lineup additional opportunities to advance runners and forced Boston’s pitchers to work through more plate appearances.

Why the Cardinals’ Hit Total Mattered

St. Louis collected eight hits compared with Boston’s five. It also had six walks, compared with none for the Red Sox.

That combination created a meaningful advantage in baserunners. The Cardinals left 12 runners on base, which shows they did not convert every chance. However, they produced enough runs from the opportunities they did convert.

The team went 2-for-13 with runners in scoring position. That figure is not particularly efficient, but it includes two successful hits in high-value situations. The Cardinals also scored through sacrifice flies, demonstrating that a hit is not the only way to bring a runner home.

Pitching Analysis: How the Cardinals Protected Their Lead

Pitching was a major factor in the outcome. St. Louis used four pitchers across nine innings, allowing five hits and two runs while recording seven strikeouts. Boston used five pitchers across eight innings, allowing eight hits and three runs while striking out nine.

The Cardinals’ pitching staff also issued no walks. Boston’s pitchers allowed six, which gave the home team additional chances to build rallies.

St. Louis Cardinals Pitching Stats

Pitcher	IP	H	R	ER	BB	K	Pitches
D. May	6.0	4	2	1	0	4	75
R. Stanek	1.0	0	0	0	0	1	10
J. Romero	1.0	1	0	0	0	1	21
R. O’Brien	1.0	0	0	0	0	1	8
Team total	9.0	5	2	1	0	7	114

IP means innings pitched, H means hits allowed, ER means earned runs, BB means walks, and K means strikeouts.

D. May Delivers Six Important Innings

May earned the win after pitching six innings and allowing four hits, two runs, and one earned run. He struck out four batters and did not issue a walk. His pitch count was 75, including 54 strikes.

The absence of walks was a major strength. May made Boston earn its baserunners through contact rather than giving away free passes. That helped limit the number of opportunities the Red Sox could create.

His performance also demonstrated the value of limiting damage. Although Boston scored twice during his outing, only one run was earned. The distinction indicates that defensive circumstances contributed to the scoring sequence.

May’s listed game score was 62, the highest pitching game score identified in the supplied data. Game score is a summary measure of a starting pitcher’s performance, but it should be read alongside innings, runs, strikeouts, and other statistics.

His listed season ERA was 9.45. That number is separate from his performance in this particular game and should not be used to dismiss the quality of his six innings.

Ryan Stanek Maintains the Advantage

Stanek pitched a scoreless seventh inning. He allowed no hits, issued no walks, and struck out one batter on 10 pitches.

His inning was important because Boston had already demonstrated that it could score. By preventing additional baserunners, Stanek kept the game within the Cardinals’ control.

Relief pitchers often work with a different objective from starters. A starter may focus on working deep into a game, while a reliever is asked to secure a specific portion of the contest. Stanek completed that task efficiently.

JoJo Romero Keeps Boston Off the Scoreboard

Romero pitched one inning, allowing one hit without giving up a run. He recorded one strikeout and threw 21 pitches, including 12 strikes.

Although he allowed contact, he prevented Boston from turning that hit into a run. That was an important part of the Cardinals’ overall pitching effort.

The inning also highlights why hits allowed should not be interpreted in isolation. A pitcher can give up a single and still complete a successful inning by limiting further advancement and recording the necessary outs.

Ryan O’Brien Closes Out the Game

O’Brien recorded the save with a scoreless ninth inning. He allowed no hits, issued no walks, and struck out one batter on eight pitches.

A clean ninth inning is particularly valuable in a one-run game. Boston needed only one run to tie the contest, but O’Brien did not allow the Red Sox to put a runner on base.

His performance completed the Cardinals’ nine-inning defensive effort. The supplied data credited him with his fourth save.

Boston Red Sox Pitching Stats

Pitcher	IP	H	R	ER	BB	K	Pitches
C. Early	4.1	5	1	1	2	5	86
Z. Kelly	0.2	2	2	2	1	0	18
T. Samaniego	0.2	0	0	0	2	1	22
G. Weissert	1.1	0	0	0	0	1	18
J. Moran	1.0	1	0	0	1	2	17
Team total	8.0	8	3	3	6	9	161

Pitching figures are transcribed from the supplied box score. The individual innings are displayed in baseball notation.

C. Early Gives Boston a Competitive Start

Early pitched 4⅓ innings, allowing five hits and one earned run. He walked two batters and struck out five, using 86 pitches.

His five strikeouts helped Boston stay competitive. He also kept the Cardinals’ scoring relatively limited during his appearance.

However, Early’s pitch count was substantially higher than May’s. Early needed 86 pitches to record 13 outs, while May used 75 pitches to record 18 outs. This comparison shows how strike efficiency and the number of batters faced can affect a team’s bullpen workload.

Early’s performance was not enough to secure the win, but his ability to strike out five batters gave Boston a chance to remain in the game.

Z. Kelly’s Short Appearance Changes the Game

Kelly faced a difficult situation in the fifth inning. He pitched two-thirds of an inning, allowed two hits, gave up two earned runs, and walked one batter. He did not record a strikeout.

The two runs charged to Kelly were decisive because they helped St. Louis move ahead after Boston had tied the score. In a 3-2 final, a two-run sequence represents a large share of the winning team’s total offense.

This is a reminder that relief pitching can shape the outcome quickly. A pitcher may enter for a short appearance but still face several high-pressure plate appearances with runners on base.

Kelly’s line does not mean every run was caused by one mistake. It shows that the Cardinals took advantage of the opportunities available during his time on the mound.

Boston’s Other Relievers Limit Further Damage

Samaniego, Weissert, and Moran combined to prevent further Cardinals scoring after Kelly’s appearance.

Samaniego allowed no hits and no runs in two-thirds of an inning, although he issued two walks. Weissert also allowed no hits or runs over 1⅓ innings. Moran pitched one inning, allowing one hit while striking out two.

These performances helped Boston remain close. The relief group recorded four strikeouts combined after Early’s outing, but the runs already allowed proved difficult to overcome.

Boston’s bullpen did enough to prevent the deficit from growing further. The bigger challenge was that the offense could not produce the additional run needed to tie the game.

Key Scoring Plays and Inning-by-Inning Breakdown

The scoring sequence explains how a game with no home runs still produced a decisive result. St. Louis scored through sacrifice flies and a run-scoring single, while Boston benefited from a throwing error and an aggressive baserunning play.

Second Inning: St. Louis Scores First

Victor Scott II hit a sacrifice fly that allowed Urías to score. The Cardinals took a 1-0 lead.

A sacrifice fly can be one of the most practical ways to score when a runner is already in position to advance after a fly ball. It does not count as a hit, but it can be just as important as a single in a close contest.

The early run also gave May a lead to work with. Pitchers do not need a large advantage to benefit from run support, especially when they are limiting walks and controlling the pace of the game.

Fourth Inning: Boston Ties the Game

Yoshida scored on a throwing error, making it 1-1. During the same inning, Story stole home and Mayer stole second, according to the supplied game summary.

Boston’s aggressive baserunning put pressure on the Cardinals’ defense. Stealing home is an especially high-risk play because the runner must reach the plate before the catcher completes the tag, and the timing must be right.

The scoring error is also an important detail. A run that scores on an error is not automatically an earned run charged to the pitcher. This helps explain why May’s line shows two runs allowed but only one earned run.

Fifth Inning: The Cardinals Regain Control

St. Louis scored twice in the fifth. Saggese singled to bring Walker home, and Fermín hit a sacrifice fly that scored Urías.

The two plays gave the Cardinals a 3-1 lead. They also demonstrated two different approaches to run production: a base hit with a runner in scoring position and a fly ball that allowed a runner to tag up.

Boston’s fourth-inning equalizer had made the game competitive, but St. Louis responded quickly. That response became the defining offensive sequence of the contest.

Final Innings: Pitching Takes Over

After the fifth inning, neither team added another run. The Cardinals’ bullpen prevented Boston from mounting a late comeback, while Boston’s relievers kept the home team’s lead at one run.

O’Brien’s clean ninth inning completed the victory. The final score remained 3-2, despite the Cardinals leaving 12 runners on base throughout the game.

Scoring Summary

Inning	Boston	St. Louis	Key event
Second	0	1	Scott II sacrifice fly scores Urías
Fourth	1	0	Yoshida scores on a throwing error
Fifth	0	2	Saggese single and Fermín sacrifice fly
Other innings	1	0	Boston’s other run is reflected in the supplied fourth-inning summary
Final	2	3	St. Louis wins by one run

The inning-by-inning description above follows the supplied scoring notes. Those notes identify the fourth inning as the tying sequence and the fifth as the Cardinals’ two-run response. For a complete official play-by-play, consult the ESPN box score for the game.

Advanced Statistical Insights From the Game

The final score is straightforward, but several underlying statistics explain why St. Louis won despite leaving many runners on base.

1. Walks Created an Important Advantage

St. Louis drew six walks, while Boston drew none. This was one of the clearest differences between the offenses.

A walk gives a batter first base without requiring a hit. It can also force a pitcher to throw more pitches, create a scoring opportunity, and increase the pressure on the defense.

The Cardinals did not turn every walk into a run. Their 12 runners left on base show that many opportunities went unused. Still, those free baserunners helped the lineup generate enough chances to score three times.

Boston’s lack of walks meant that nearly every offensive opportunity depended on recording a hit or advancing a runner through another play. That made the Red Sox more dependent on timely contact.

2. Hits With Runners in Scoring Position Tell Only Part of the Story

Boston went 1-for-6 with runners in scoring position, while St. Louis went 2-for-13.

Runners in scoring position are generally on second or third base, where a single is more likely to bring them home. The statistic is useful because it measures how often a team records a hit in these situations.

However, batting with runners in scoring position does not capture every way a team can score. A sacrifice fly, a defensive error, or a productive ground ball can also bring a runner home.

That distinction is important here. The Cardinals recorded two hits in 13 opportunities, but their sacrifice flies also contributed to the scoring total. Boston’s tying run came on a throwing error rather than an RBI hit.

The numbers therefore describe offensive execution, but they do not tell the entire story of run production.

3. Boston Had More Strikeouts From Its Pitching Staff

Boston’s pitchers recorded nine strikeouts compared with seven for St. Louis. This suggests that the Red Sox pitching staff generated more strikeouts overall.

Yet strikeouts alone do not determine the winner. Boston also allowed eight hits and six walks, while the Cardinals allowed five hits and no walks.

A pitching staff can strike out several batters and still struggle if too many opponents reach base through other means. In this game, the Cardinals’ control helped compensate for their lower strikeout total.

4. Neither Team Hit a Home Run

Both teams finished without a home run. St. Louis produced its three runs through smaller offensive contributions rather than one major power display.

This is an important distinction for baseball analysis. Home runs can create immediate scoring opportunities, but teams can also win by combining singles, walks, sacrifice flies, and aggressive baserunning.

The Cardinals demonstrated that approach throughout the game. Boston also used baserunning to create pressure, but it could not match St. Louis’s overall number of hits and walks.

5. The Cardinals Left More Runners on Base

St. Louis left 12 runners on base, compared with five for Boston.

At first glance, that may seem like a sign of poor offensive execution. In part, it reflects missed opportunities. The Cardinals could have increased their lead by bringing more of those runners home.

However, a high left-on-base total can also indicate that a team created many baserunners. St. Louis reached base frequently enough to leave 12 runners stranded while still scoring three runs.

Boston’s lower total does not automatically mean it was more efficient. The Red Sox had fewer opportunities because they recorded fewer hits and no walks.

6. Pitch Efficiency Helped St. Louis Control the Game

May needed 75 pitches to complete six innings. Early used 86 pitches to record 13 outs.

This comparison highlights how pitch efficiency can influence bullpen management. A starter who works efficiently can stay in the game longer, preserve relief pitchers, and reduce the number of difficult transitions a team must manage.

May’s outing allowed St. Louis to use three relievers for the final three innings. The Cardinals then secured the final nine outs without allowing another run.

Boston’s starter left earlier, and the Red Sox needed four relief appearances after Early. The difference did not automatically determine the result, but it shaped how both managers used their pitching staffs.

What These Player Statistics Mean for Baseball Fans

A box score is more useful when its numbers are interpreted together. Looking at a single statistic can lead to an incomplete conclusion about a player’s performance or a team’s strategy.

Understanding Batting Average, OBP, and Slugging Percentage

The supplied player lines include three common offensive statistics.

• Batting average (AVG): The number of hits divided by official at-bats. It measures how frequently a batter gets a hit in an at-bat.
• On-base percentage (OBP): The rate at which a batter reaches base, accounting for hits, walks, hit-by-pitches, and certain other outcomes.
• Slugging percentage (SLG): Total bases divided by at-bats. It gives more weight to extra-base hits than batting average does.

These statistics answer different questions. A player with a high batting average may get hits frequently, while a player with a high on-base percentage may create value through walks as well. Slugging percentage helps identify a batter’s extra-base power.

For example, Abreu’s supplied .686 slugging percentage was higher than his .392 batting average. That difference suggests that his overall season production included substantial extra-base value. His two hits in this particular game, however, should be evaluated separately from those season figures.

Understanding Pitching Statistics

Pitching lines also contain several measures that are easy to misinterpret.

• Innings pitched (IP): The number of outs a pitcher records, displayed in baseball notation.
• Earned runs (ER): Runs charged to a pitcher that are not considered unearned under the official scoring rules.
• Walks (BB): Batters awarded first base after four balls.
• Strikeouts (K): Batters retired by strike three.
• Earned run average (ERA): Earned runs allowed per nine innings, based on a pitcher’s statistical record.

A pitching line of 4.1 innings means four complete innings plus one additional out. It does not mean four and one-tenth innings in ordinary decimal arithmetic. Similarly, 0.2 means two outs, or two-thirds of an inning.

This matters when comparing workloads. Treating 4.1 as a decimal would produce an incorrect calculation of innings pitched.

May’s six innings, zero walks, and one earned run provide a useful picture of his outing. O’Brien’s one hitless inning with one strikeout describes a different job: finishing the game without allowing Boston to score.

Why RBI Totals Need Context

Runs batted in measure how many runs a batter is credited with driving home, subject to official scoring rules. They do not measure every contribution a player makes to scoring.

Yoshida scored on a throwing error, but that run did not give him an RBI. Urías scored twice, yet he was not credited with an RBI in the supplied batting line. Meanwhile, Saggese and Fermín each recorded an RBI through different types of plays.

When evaluating players, it is helpful to combine RBI totals with runs scored, hits, walks, and the actual scoring sequence. That provides a more complete understanding of who contributed and how.

Frequently Asked Questions

Who won the Red Sox vs. St. Louis Cardinals game on April 11, 2026?

The St. Louis Cardinals defeated the Boston Red Sox 3-2 at Busch Stadium, according to the supplied game data.

Who was the winning pitcher?

1. May earned the win after pitching six innings, allowing four hits, two runs, and one earned run. He struck out four batters and issued no walks.

Which Cardinals player scored the most runs?

Ramón Urías scored twice, making him the Cardinals player with the most runs in the supplied box score.

How many hits did Boston and St. Louis record?

Boston recorded five hits, while St. Louis collected eight. The Cardinals also drew six walks, compared with none for the Red Sox.

Did either team hit a home run?

No. Both teams finished without a home run. The Cardinals scored through a sacrifice fly, an RBI single, and another sacrifice fly, while Boston benefited from a run scored on a throwing error.

Who recorded the save for St. Louis?

1. O’Brien earned the save by pitching a scoreless ninth inning. He allowed no hits, issued no walks, and recorded one strikeout.

Red sox vs st. louis cardinals match player stats: Final Analysis

The Cardinals’ 3-2 victory demonstrated how pitching control and timely offensive execution can decide a close baseball game. St. Louis recorded eight hits, drew six walks, and received a strong six-inning start from May. Its bullpen then protected the one-run advantage through the final three innings.

Boston had its own strengths. The Red Sox pitching staff recorded nine strikeouts, Abreu collected two hits, and the team used aggressive baserunning to create pressure. However, five hits and zero walks limited its ability to build consistent scoring opportunities.

The decisive difference was not a home run or a dominant offensive explosion. Instead, St. Louis scored through a combination of sacrifice flies, a run-scoring single, and patient plate appearances. Boston remained competitive but could not produce enough offense to complete the comeback.

For readers analyzing individual performances, the most useful approach is to consider batting totals, baserunning, pitching efficiency, and scoring situations together. These statistics provide a clearer picture of how the game unfolded than the final score alone.