What Jimmie Foxx's 1932 Season Would Look Like in 2000
This page projects Jimmie Foxx's production from the 1932 run environment into the 2000 one, so the two can be compared directly. His actual line was .364/.469/.749, 1.218 OPS. Translated to 2000 conditions, that becomes .358/.483/.836, 1.319 OPS. The translation rescales counting stats by the ratio of league run scoring between the two eras; it does not attempt to model park, travel or integration effects.
- AVG (Batting Average):
- Hits divided by at bats. .300 is the traditional mark of an excellent hitter.
- OBP (On-Base Percentage):
- How often a batter reaches base: (H + BB + HBP) divided by (AB + BB + HBP + SF).
- SLG (Slugging Percentage):
- Total bases divided by at bats — a measure of power rather than frequency.
- OPS (On-Base Plus Slugging):
- On-base percentage plus slugging percentage, the quickest single summary of offensive value. .900 or better is star-level.
Data updated
What would Jimmie Foxx's 1932 season look like if he hit in 2000 instead? Below, his real 1932 line sits beside a cross-era translation into 2000's run environment — and a live slider lets you drop that season into any year in MLB history.
Jimmie Foxx — 1932 (real)
Translated to 2000
Why the translated line looks better: 2000 was a higher-offense run environment than 1932 (league OPS .727 → .782), so every hitter's raw line scales up. It does not mean Jimmie Foxx would hit better against modern pitching — it is the same hitter re-based to a livelier league.
What this translation does not account for
This is a model, not a prediction. It re-expresses only Jimmie Foxx's rate stats against 2000's league run environment — and nothing else. It does not account for the depth of competition (integration, international talent, a vastly larger athlete pool), pitch velocity, modern pitch arsenals (sliders, splitters, sweepers), strength and conditioning, or in-game adjustments and advanced scouting.
So a higher translated line means 2000 was simply a higher-offense era — not a claim that Jimmie Foxx would actually perform better against today's pitching.
Rate Stats: Real vs. Translated
These rate stats are re-expressed by holding Jimmie Foxx's performance relative to his league constant and re-basing it on 2000's averages (the same idea behind OPS+/ERA+).
| Stat | 1932 (real) | 2000 (modeled) |
|---|---|---|
| AVG | .364 | .358 |
| OBP | .469 | .483 |
| SLG | .749 | .836 |
| OPS | 1.218 | 1.319 |
Counting Stats (1932, as played)
| Games | 154 |
| At-Bats | 585 |
| Hits | 213 |
| Home Runs | 58 |
| RBI | 169 |
| Runs | 151 |
| Walks | 116 |
| Stolen Bases | 3 |
Why counting totals aren't translated: scaling a counting stat by the league environment ratio massively over-inflates era outliers — e.g. a 1920s slugger's home runs would balloon to absurd modern totals. So home runs, RBI, wins, strikeouts and the like are shown exactly as Jimmie Foxx produced them.
Verdict
This is a model, not a prediction. In 2000, the highest-offense season of the steroid era — a run environment friendlier to hitters than 1932's (league OPS .727 → .782) — one reasoned way to express Jimmie Foxx's 1932 season is roughly .358/.483/.836 with a 1.319 OPS. That figure holds his performance relative to his league constant and re-bases it on 2000's averages; it is not a claim that Jimmie Foxx would actually post that line. His counting totals (58 HR, 169 RBI) are shown exactly as he played them, because scaling counting stats across eras wildly inflates outliers.
Try Any Era — Live
Pick a player and slide across MLB history to re-translate their peak season into any season's run environment. Same model, recomputed instantly.
Jimmie Foxx in Other Eras
View Jimmie Foxx's full profile → · Browse all era translations →
What Jimmie Foxx's 1932 Season Would Look Like in 2000: Frequently Asked Questions
- What would Jimmie Foxx hit in the 2000?
- Translated into the 2000 run environment, Jimmie Foxx's line becomes .358/.483/.836, 1.319 OPS.
- What did Jimmie Foxx actually do?
- His real line was .364/.469/.749, 1.218 OPS in 1932, compiled in the 1932 season.
- How does the era translator work?
- It rescales a player's counting statistics by the ratio of league-wide run scoring between the two eras, holding his playing time constant. It does not model park effects, travel, equipment or the integration of the leagues.