What David Ortiz's 2007 Season Would Look Like in 1998
This page projects David Ortiz's production from the 2007 run environment into the 1998 one, so the two can be compared directly. His actual line was .332/.445/.621, 1.066 OPS. Translated to 1998 conditions, that becomes .329/.444/.617, 1.062 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 David Ortiz's 2007 season look like if he hit in 1998 instead? Below, his real 2007 line sits beside a cross-era translation into 1998's run environment — and a live slider lets you drop that season into any year in MLB history.
David Ortiz — 2007 (real)
Translated to 1998
Why the translated line is lower: 1998 was a tougher, lower-offense run environment than 2007 (league OPS .758 → .755).
What this translation does not account for
This is a model, not a prediction. It re-expresses only David Ortiz's rate stats against 1998'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 1998 was simply a higher-offense era — not a claim that David Ortiz would actually perform better against today's pitching.
Rate Stats: Real vs. Translated
These rate stats are re-expressed by holding David Ortiz's performance relative to his league constant and re-basing it on 1998's averages (the same idea behind OPS+/ERA+).
| Stat | 2007 (real) | 1998 (modeled) |
|---|---|---|
| AVG | .332 | .329 |
| OBP | .445 | .444 |
| SLG | .621 | .617 |
| OPS | 1.066 | 1.062 |
Counting Stats (2007, as played)
| Games | 149 |
| At-Bats | 549 |
| Hits | 182 |
| Home Runs | 35 |
| RBI | 117 |
| Runs | 116 |
| Walks | 111 |
| 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 David Ortiz produced them.
Verdict
This is a model, not a prediction. In 1998, the peak of the steroid-era home-run chase — a run environment tougher for hitters than 2007's (league OPS .758 → .755) — one reasoned way to express David Ortiz's 2007 season is roughly .329/.444/.617 with a 1.062 OPS. That figure holds his performance relative to his league constant and re-bases it on 1998's averages; it is not a claim that David Ortiz would actually post that line. His counting totals (35 HR, 117 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.
David Ortiz in Other Eras
View David Ortiz's full profile → · Browse all era translations →
What David Ortiz's 2007 Season Would Look Like in 1998: Frequently Asked Questions
- What would David Ortiz hit in the 1998?
- Translated into the 1998 run environment, David Ortiz's line becomes .329/.444/.617, 1.062 OPS.
- What did David Ortiz actually do?
- His real line was .332/.445/.621, 1.066 OPS in 2007, compiled in the 2007 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.