NEW YORK – New York Mets star Juan Soto exited Friday’s 4-2 loss to the Los Angeles Dodgers with left calf soreness. He will undergo an MRI on Saturday. The team described the move as precautionary.
Soto pulled up after chasing a fly ball in the top of the fifth inning. He limped off the field at Citi Field and was replaced by Tyrone Taylor. Teammates gathered around him as trainers evaluated the leg.
The injury occurred on a routine play. Soto appeared to grab his lower left leg immediately after the catch. He did not return to the dugout.
The MRI will determine the severity of the issue. The Mets are calling it “left calf soreness.” The spectrum of outcomes ranges from simple cramping to a Grade 1 strain. A strain typically requires a 10-to-14-day recovery period.
“We’ll know more tomorrow,” manager Carlos Mendoza said postgame. “He felt something. We took him out.” Mendoza declined to speculate on a timeline.
Soto’s status is currently listed as day-to-day. That assessment is contingent on clean MRI results. If the MRI reveals a strain, the timeline could extend significantly.
Historical data on MLB calf injuries is instructive. A 2021 study showed that Grade 1 strains average 11 missed games. Grade 2 strains average 35. The Mets are unlikely to risk a longer absence by rushing him back.
The impact on the Mets’ lineup is immediate. Soto has a .295 batting average with 25 home runs and 78 RBIs this season. He is the team’s primary offensive threat.
If Soto misses time, the outfield configuration shifts. Starling Marte or Brandon Nimmo could move into a more central role. Tyrone Taylor and DJ Stewart are the primary bench options. The Mets’ playoff push in the National League wild card race tightens without him.
| Metric | Soto (2024 Season) | Marte (Comparable) |
|---|---|---|
| Batting Avg | .295 | .282 |
| Home Runs | 25 | 14 |
| RBIs | 78 | 52 |
| WAR | 4.3 | 1.9 |
The game itself was a sidebar. The Dodgers took a 3-0 lead in the first inning. Shohei Ohtani hit a two-run double. The Mets scored two runs in the eighth but could not complete the comeback. The loss dropped them to 64-53.
Fan reaction on social media was immediate and anxious. The Mets’ official account confirmed the MRI plan within 30 minutes of Soto’s exit. Beat reporters for The Athletic and SNY have been the primary sources for updates.
To follow Soto’s recovery, monitor the team’s official social media channels. The Mets typically provide a post-MRI update via press release. Beat reporters at Citi Field will offer real-time commentary. Expect the next substantive news cycle Saturday afternoon.
Key takeaways: the injury is being treated with extreme caution. The MRI results are the single variable that will dictate the next move. Mets fans should brace for a potential multi-week absence, but hope for a day-to-day outcome.
💡 Frequently Asked Questions (FAQ)
- Q: What happened to Juan Soto during the Mets vs. Dodgers game?
- A: Juan Soto exited Friday’s 4-2 loss to the Los Angeles Dodgers with left calf soreness after chasing a fly ball in the top of the fifth inning. He limped off the field at Citi Field and did not return to the dugout.
- Q: When will Juan Soto undergo an MRI for his calf injury?
- A: Soto will undergo an MRI on Saturday to determine the severity of the left calf soreness. The team described the move as precautionary.
- Q: What are the potential outcomes of Juan Soto’s calf injury?
- A: The spectrum of outcomes ranges from simple cramping to a Grade 1 strain. A Grade 1 strain typically requires a 10-to-14-day recovery period, while Grade 2 strains average 35 missed games based on historical data.
- Q: How will Juan Soto’s injury impact the New York Mets lineup?
- A: Soto is the team’s primary offensive threat with a .295 batting average, 25 home runs, and 78 RBIs this season. His absence would immediately affect the Mets’ offensive production.
Extended Reading
For further detail, the initial reports from Yahoo Sports and Bleacher Report provided the first confirmations of the injury and the MRI plan. The CBS Sports report was unavailable due to a server error.