- Thread starter
- #161
saddles
Bullpen Failure is back, lurking like Gollum
From Scott Lucas:
This is wrong. Jordan Montgomery's sinker was 90.1 tonight and also averaged the same 90.1 in 3 prior AAA outings (I don't have data from 2 earlier AA outings, but no reason to think they're hotter.) @Evan_P_Grant wrote this, but it's not his fault. It's Statcast's fault.
My guess is Evan got "down 1.7" from the Statcast gamefeed. There it is, clearly stating a decline of 1.7 MPH from his previous average. But if you download the data, you'll find an average sinker of 90.1 (and a max of 91.9) prior to tonight. So where does 91.8 comes from?
91.8 is Montgomery's average sinker velocity in the Majors in 2024, the time he appeared there. Why does Statcast use two-year-old data and dub it "Yr-Avg" in a 2026 game? I guess because he has a lengthy MLB history, but it's highly deceptive. How could you possibly know?
The reasons *I* know are 1) looking at AAA data nearly every day because I have no life, and 2) Josh Sborz. A gamefeed from one of Sborz's outings shows a "Yr-Avg" fastball of 95.1. But we all know Sborz's velocity hasn't returned. Where does 95.1 come from?
Sure enough, 95.1 is Sborz's average fastball from 2024, the last time he pitched in the Majors. This comparison to the past is quite helpful, but the problem is Statcast doesn't ID it as an old MLB average. You have no reason to think it's anything but a 2026 AAA average.
Anyway, as far as the Rangers hoping to see "closer to 93," well, sure, yes, hope is great. Hope sustains us.
Apparently in AAA games, Statcast shows MLB velo/movement averages if a pitcher has thrown at that level at all; e.g., Winston Santos. He's thrown 3 sweepers & 6 sinkers across 2 AAA games, but his avg velo is N/A because he didn't throw either in his 1 MLB outing.
This is wrong. Jordan Montgomery's sinker was 90.1 tonight and also averaged the same 90.1 in 3 prior AAA outings (I don't have data from 2 earlier AA outings, but no reason to think they're hotter.) @Evan_P_Grant wrote this, but it's not his fault. It's Statcast's fault.
My guess is Evan got "down 1.7" from the Statcast gamefeed. There it is, clearly stating a decline of 1.7 MPH from his previous average. But if you download the data, you'll find an average sinker of 90.1 (and a max of 91.9) prior to tonight. So where does 91.8 comes from?
91.8 is Montgomery's average sinker velocity in the Majors in 2024, the time he appeared there. Why does Statcast use two-year-old data and dub it "Yr-Avg" in a 2026 game? I guess because he has a lengthy MLB history, but it's highly deceptive. How could you possibly know?
The reasons *I* know are 1) looking at AAA data nearly every day because I have no life, and 2) Josh Sborz. A gamefeed from one of Sborz's outings shows a "Yr-Avg" fastball of 95.1. But we all know Sborz's velocity hasn't returned. Where does 95.1 come from?
Sure enough, 95.1 is Sborz's average fastball from 2024, the last time he pitched in the Majors. This comparison to the past is quite helpful, but the problem is Statcast doesn't ID it as an old MLB average. You have no reason to think it's anything but a 2026 AAA average.
Anyway, as far as the Rangers hoping to see "closer to 93," well, sure, yes, hope is great. Hope sustains us.
Apparently in AAA games, Statcast shows MLB velo/movement averages if a pitcher has thrown at that level at all; e.g., Winston Santos. He's thrown 3 sweepers & 6 sinkers across 2 AAA games, but his avg velo is N/A because he didn't throw either in his 1 MLB outing.



