What Is a Park Factor?
A park factor is a multiplier that quantifies how much a ballpark inflates or suppresses run scoring compared to league average. A park factor of 1.10 means the venue produces 10% more runs than a neutral park. A factor of 0.92 means 8% fewer runs. Over many seasons, these differences accumulate and matter significantly.
Park factors are calculated by comparing the average number of runs scored (for both home and visiting teams) in a given park to the league-wide average. The math accounts for the era (deadball vs. steroid era) and controls for the strength of teams playing there. A park's factor remains relatively stable year-to-year because the physical dimensions, elevation, and climate do not change.
Coors Field: The Extreme Example
Coors Field in Denver sits at 5,280 feet above sea level. The thin air means less air density, which allows balls to travel farther and faster. A ball hit 430 feet in Denver might travel only 420 feet at sea level. Compounding this, Denver's low humidity and warm summers further amplify the ball's carry distance. The result: Coors Field has a run-scoring park factor of approximately 1.15, meaning games there produce roughly 15% more runs than league average.
This inflation affects everything. A hitter at Coors Field will post inflated batting average, home runs, and slugging percentage compared to his true talent. Pitchers give up more hits and more long balls. A team's home ERA at Coors (with visiting pitchers on the road benefiting from the thin air) will appear worse than their true pitching ability. This is why adjusted stats (wRC+, ERA+) are essential for fair player comparison.
Hitter-Friendly Parks
Beyond Coors, several parks favor offense. Globe Life Field in Arlington (factor ~1.08) plays hot due to warm Texas temperatures. Fenway Park (factor ~1.06) has a short left field wall (the 'Green Monster') that turns potential long flyouts into home runs. Great American Ball Park in Cincinnati (factor ~1.05) also tends to inflate batting lines. When a star hitter plays most games in one of these parks, their raw stats overstate their true talent level.
Pitcher-Friendly Parks
On the flip side, some parks suppress offense. Oracle Park in San Francisco (factor ~0.92) combines dense marine air with deep outfield dimensions, making home runs rare. Petco Park in San Diego (factor ~0.94) has similar properties: chilly coastal air and spacious gaps. Kauffman Stadium in Kansas City (factor ~0.95) is another pitcher's refuge. Pitchers thriving in these environments appear better than their true talent; those relocated elsewhere see ERA rise.
Why This Matters for Your Analysis
Park factors directly impact totals (over/under) and moneylines. If two teams play a game at Coors, expect higher scoring and higher totals lines. If the same matchup occurs at Petco, scoring drops. A lineup posting a .320 wOBA at home in Coors Field might project to only .310 wOBA at Petco due to park factor differences. This creates an edge for bettors and analysts who account for it.
StatScope's model includes park factor adjustment in its win-probability calculation. When a high-offensive-power team plays at Coors, we expect more runs and higher scoring. When a dominant pitching staff works in a pitcher-friendly park, we suppress expected offense. Failing to account for park factors is a systematic error that impacts every statistical conclusion.
Adjusted Stats: The Solution
This is why adjusted stats (wRC+, OPS+, ERA+) exist. They remove park factor bias by normalizing to 100 as league average. A player with a .320 wOBA at Coors might post a wRC+ of 130 (30% above league average after park adjustment). The same player at Petco might have wRC+ of 135 despite a lower raw wOBA, because the park factor makes hits harder to come by. When comparing players across teams, always prefer adjusted stats. When analyzing totals, always factor in the venue.