10
Loading video...
By Cameron Kiszla
0
Share
Newsweek is a Trust Project member
See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.
Utility infielder Joshua Kuroda-Grauer of the Athletics took a foul ball to a sensitive place Monday night, and the horrific injury he suffered is going to keep him sidelined.
Kuroda-Grauer took a foul ball to what announcers called his "inner leg" in the game against Arizona Diamondbacks.
The pain sent him to the ground for several minutes, though after receiving attention from the medical staff, he was able to rise and hit a single.
Read More on MLB
After the game, though, JKG was placed on the 10-day injured list. The injury? A ruptured testicle.
After Monday night's game, A's manager Mark Kotsay noted that it was an "unfortunate event for JKG."
“He tried to stay in and battle. Right now, the big concern is [to make sure] there’s no significant injury to him. We’ll have further notice later on tonight, but, hopefully, things are OK.”
...
MLB.com reports that Monday night, JKG "underwent emergency surgery to repair a ruptured testicle last night at St. Joseph’s Hospital in Phoenix and is resting comfortably."
On Tuesday, Kotsay told Martín Gallegos of MLB.com that he'd visited JKG in the hospital.
"He’s in great spirits. He was joking. His personality is amazing. … I think he might be the only player in history to [rupture] a testicle, stay in the game, get a hit and play another half inning of defense," Kotsay said.
JKG’s Injury Comes After High Point of Young Career
Kuroda-Grauer only made his MLB debut a few weeks ago.
Since being called up to the big leagues on June 29, he's played in 16 games and is hitting .417.
He also has multiple hits in eight of those games, an astounding rate for any player, not to mention a rookie.
Monday was one of those multi-hit games, as he'd earlier blasted a home run, his first in the big leagues.
Hopefully, he'll heal quickly and be back to wowing baseball fans soon.
View 0 Comments
Submit Correction
View Editorial & AI Guidelines