What is Park Factor? Definition, Formula, and Example
Park factor is a ratio that captures how much a specific ballpark inflates or depresses offensive events (runs, home runs, hits) relative to a neutral environment. It is the correction that lets analysts fairly compare a Coors Field hitter to a Petco Park hitter — and the reason Legends Deck card ratings already adjust for ballpark effects.
What Is Park Factor?
A park factor is a number that expresses how friendly or hostile a ballpark is for a specific offensive event, compared to the MLB average. It's usually expressed on a scale where 100 = neutral, numbers above 100 mean the park increases that event, and numbers below 100 mean it suppresses that event.
Examples from recent seasons:
| Ballpark | Runs | Home runs | Hits |
|---|---|---|---|
| Coors Field (COL) | 112 | 107 | 106 |
| Great American Ball Park (CIN) | 105 | 120 | 101 |
| Fenway Park (BOS) | 104 | 94 | 106 |
| Oracle Park (SF) | 93 | 82 | 96 |
| T-Mobile Park (SEA) | 92 | 89 | 94 |
A home run factor of 120 at Cincinnati means GABP inflates HRs by 20% over neutral. A HR factor of 82 at Oracle Park means San Francisco suppresses them by 18%.
Park Factor Formula (One-Year, Simple)
One-year park factor for event E =
((home team E at home + opponent E at home) / home team games at home) /
((home team E on road + opponent E on road) / games on road)
This is computed over multi-year windows (usually 3–5 years) to reduce noise, and typically centered around 100.
FanGraphs and Statcast publish regressed, event-specific park factors that account for handedness of the batter (LHH vs RHH see different outfield dimensions at many parks) and batted-ball direction.
Why Park Factors Matter
For hitter evaluation. Kyle Farmer hitting .290/.350/.500 in Coors is not the same hitter as someone posting identical stats in Oakland. Park-adjusted wRC+ and OPS+ already bake in park factor — they're why front offices use them instead of raw OPS for contract comps.
For pitcher evaluation. A 3.40 ERA in Yankee Stadium is more impressive than a 3.40 ERA at Oracle Park. Park-adjusted ERA+ captures this.
For projections. Projection systems (Steamer, ZiPS) apply destination park factors when forecasting. A hitter traded from Detroit to Colorado gets a projection bump.
The Handedness Wrinkle
Park factors are not symmetric across handedness. Fenway's Green Monster is a left-field wall 310 feet from home — a massive boost for right-handed pull hitters, a mild suppressor for lefty pull power. The run-environment-neutral park factor of 104 hides a 115 for RHH and 95 for LHH.
Legends Deck uses handedness-split park factors internally when rating players — meaning a lefty pull hitter on the Red Sox is correctly rated as park-neutral, not park-boosted. This matches how MLB front offices actually evaluate.
Worked Example
A hitter posts .310/.380/.540 (.920 OPS) across 600 PA at Coors Field (park factor 112). A second hitter posts .275/.350/.480 (.830 OPS) across 600 PA at Oracle Park (park factor 93).
Raw OPS gap: 90 points favoring the Coors hitter.
Park-adjusted: divide each OPS by the park factor / 100.
- Hitter A: .920 / 1.12 = .821
- Hitter B: .830 / 0.93 = .892
Park-adjusted gap: 71 points favoring the Oracle Park hitter. The raw numbers were lying.
Park Factors in Legends Deck
Every card rating in Legends Deck is park-adjusted. If a player put up big counting stats at Coors, his card rates at his true talent level — not his Coors-inflated level. Conversely, a Petco Park or Oracle Park hitter is upgraded to reflect what he'd produce in a neutral environment.
This is why card ratings in Legends Deck often diverge from what fans expect based on headline stats. The math is running on the same park-adjusted inputs that MLB front offices use. And when you run a Franchise season, each of the 30 real parks applies its real park factor to simulated games — so Coors still inflates offense, Oracle still suppresses it, and your stadium choice matters.