What Paul Waner's 1928 Season Would Look Like in 1968
This page projects Paul Waner's production from the 1928 run environment into the 1968 one, so the two can be compared directly. His actual line was .370/.446/.547, .992 OPS. Translated to 1968 conditions, that becomes .312/.389/.470, .859 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 Paul Waner's 1928 season look like if he hit in 1968 instead? Below, his real 1928 line sits beside a cross-era translation into 1968's run environment — and a live slider lets you drop that season into any year in MLB history.
Paul Waner — 1928 (real)
Translated to 1968
Why the translated line is lower: 1968 was a tougher, lower-offense run environment than 1928 (league OPS .738 → .639).
What this translation does not account for
This is a model, not a prediction. It re-expresses only Paul Waner's rate stats against 1968'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 1968 was simply a higher-offense era — not a claim that Paul Waner would actually perform better against today's pitching.
Rate Stats: Real vs. Translated
These rate stats are re-expressed by holding Paul Waner's performance relative to his league constant and re-basing it on 1968's averages (the same idea behind OPS+/ERA+).
| Stat | 1928 (real) | 1968 (modeled) |
|---|---|---|
| AVG | .370 | .312 |
| OBP | .446 | .389 |
| SLG | .547 | .470 |
| OPS | .992 | .859 |
Counting Stats (1928, as played)
| Games | 152 |
| At-Bats | 602 |
| Hits | 223 |
| Home Runs | 6 |
| RBI | 86 |
| Runs | 142 |
| Walks | 77 |
| Stolen Bases | 6 |
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 Paul Waner produced them.
Verdict
This is a model, not a prediction. In 1968, the Year of the Pitcher and the lowest-scoring modern season — a run environment tougher for hitters than 1928's (league OPS .738 → .639) — one reasoned way to express Paul Waner's 1928 season is roughly .312/.389/.470 with a .859 OPS. That figure holds his performance relative to his league constant and re-bases it on 1968's averages; it is not a claim that Paul Waner would actually post that line. His counting totals (6 HR, 86 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.
Paul Waner in Other Eras
View Paul Waner's full profile → · Browse all era translations →
What Paul Waner's 1928 Season Would Look Like in 1968: Frequently Asked Questions
- What would Paul Waner hit in the 1968?
- Translated into the 1968 run environment, Paul Waner's line becomes .312/.389/.470, .859 OPS.
- What did Paul Waner actually do?
- His real line was .370/.446/.547, .992 OPS in 1928, compiled in the 1928 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.