Top1 • Tampa Bay Rays
Called Strike
Medium Pressure • ELI 55
Count Shift
Strikeout
Base / Score
Bases Empty • Tie 0-0
Count Edge
No baseline delta
Decision Read
Hold • +0.10% EV
Review happened at the at-bat level without a tracked pitch event.
Game 823082
Busch Stadium
Mar 28, 6:15 PM UTC
A chart-first postgame recap of which club handled the challenge game better, where the biggest swings landed, and what the umpire looked like by final out.
Debrief generated Mar 29, 8:50 PM
Team vs Team Outcome Recap
Total Reviews
Raw challenge volume from the completed game.
Overturn Rate
Which club actually won more of its review bets.
Late / Close Share
How much of each team’s review activity came in the game’s tightest windows.
Tonight's Review Pattern
3 reviewed pitches so far • 0 overturned
Highest Risk Split
RHP vs RHB
RHP vs RHB
0%
2 reviews
ELI 59.0
RHP vs LHB
0%
1 review
ELI 55.0
Most Targeted Pitch
Four-Seam Fastball
1 reviews • 0% overturned
Most Active Lane
Bot-M
1 reviews • 0% overturned
Scenario Timeline
Top1 • Tampa Bay Rays
Medium Pressure • ELI 55
Count Shift
Strikeout
Base / Score
Bases Empty • Tie 0-0
Count Edge
No baseline delta
Decision Read
Hold • +0.10% EV
Review happened at the at-bat level without a tracked pitch event.
Bot8 • Tampa Bay Rays
Medium Pressure • ELI 47
Count Shift
1-0
Base / Score
Bases Empty • 0-4
Count Edge
+0.0 pts
Decision Read
Hold • -3.28% EV
Call was confirmed after review.
Top9 • St. Louis Cardinals
High Pressure • ELI 71
Count Shift
1-0
Base / Score
Runner on 1st • 3-4
Count Edge
+0.0 pts
Decision Read
Hold • -3.52% EV
Call was confirmed after review.
Narrative readout of how the review battle unfolded after the charts have established which club actually captured the value.
The St. Louis Cardinals edged the Tampa Bay Rays 6-5 in a tight contest at Busch Stadium, with Absence-Based System (AiBS) challenges playing a subtle yet telling role in the flow of the game. Despite three total challenges—one from the Cardinals and two from Tampa Bay—none were overturned, underscoring a consistent umpiring zone that withstood scrutiny late into a closely fought battle. All calls were confirmed, affirming the plate umpire’s control and providing no shifts in momentum from reversed decisions.
The challenges punctuated key innings, notably in the bottom of the 9th with Cardinals’ Pedro Pagés’ ball call confirmed, maintaining his team’s narrow lead at 4-3 and underscoring the game’s tight closing stretch. Earlier, the Rays had two challenges in the bottom of the 1st and 8th innings involving ball and strike calls at counts 2-3 and 1-0, both upheld, which kept Tampa Bay from pressing a scoring surge before falling behind. These moments highlight the game’s measured sequencing, reinforcing that while the Rays managed productive innings, the umpire’s zone held firm under pressure.
Pitch Timeline
Mapping Decisions
Challenge Brief
Focus this rail on the call, the game-state consequence, and the decision read. Deeper model and historical context stay tucked into org view only.
Focus
Carson Williams vs Ryne Stanek
Count Transition
1-0
Result
Call Confirmed
Recorded Challenge
Game State
Runner on 1st
Top 9 • 3-4 • 2 outs
Away offense batting
Estimated Leverage
71
Pitch
Four-Seam Fastball
Velocity
97.1 MPH
Location
-0.02 x, 1.54 z
Count Before
1-0
Baseball Consequence
Review held the count at 1-0.
Comparable game states move run expectancy by +0.000 from this review state.
Decision Read
Model favored holding
45% overturn probability and -3.52% expected value at challenge time.
Most active innings at the plate—bottom 1, 8, and 9—coincided with these pivotal challenge opportunities, illustrating how subtle strike zone calls anchored the game’s rhythm without provocation of overturned judgments. The early and late involvement in reviews demonstrates how AiBS can delineate tight strike-zone boundaries that influence scoring chances and preserve the game’s competitive structure. However, one review relied on inferred pitch coordinates, indicating that conclusions on umpire zones should be framed cautiously despite the tracked data supporting the majority of challenges.
Ultimately, the clean uphold of all three challenges reflected the umpire’s consistent strike zone throughout, contributing to a game defined by narrow margins and competitive balance rather than officiating disruptions. This suggests that in this matchup, AiBS served more as a confirmation tool than a game-altering influence, reinforcing an already well-officiated contest.