What Does OPS Mean in Baseball? Formula and Examples

OPS is baseball’s quick answer to a two-part question: how often does this hitter reach base, and how much damage do the hits do? It combines those skills in one familiar number, but it is easy to misread if you treat it like an ordinary percentage.

OPS formula at a glance

OPS = on-base percentage + slugging percentage

MLB’s official OPS definition describes the purpose plainly: unite reaching base with hitting for average and power. The result is written to three decimal places, normally without a leading zero. A line of .810 means an OPS of eight-ten, not 81 percent.

How to calculate OPS step by step

Consider a hitter with these season totals:

• 500 at-bats
• 140 hits: 90 singles, 30 doubles, 5 triples and 15 home runs
• 60 walks
• 5 hit-by-pitches
• 5 sacrifice flies

First calculate OBP:

(140 H + 60 BB + 5 HBP) / (500 AB + 60 BB + 5 HBP + 5 SF) = 205 / 570 = .360

Then calculate total bases and SLG:

(90 x 1) + (30 x 2) + (5 x 3) + (15 x 4) = 225 total bases

225 TB / 500 AB = .450 SLG

Finally, add the two rates:

.360 OBP + .450 SLG = .810 OPS

The official OBP explainer and slugging-percentage guide go deeper into the edge cases. For a quick OPS calculation, the example above contains everything most readers need.

What an .800 OPS actually means

An .800 OPS does not mean a player gets on base eight times in ten. OPS is not one success rate. It adds OBP, which uses plate-appearance inputs, to SLG, which uses at-bats and weights hits by total bases.

Two hitters can reach the same .800 OPS in very different ways:

This was the most persistent confusion in public discussions we reviewed. Fans repeatedly asked whether OPS was “out of 1.000” or whether .800 meant an 80 percent success rate. The safest habit is simple: read OBP when you want frequency, SLG when you want total-base power, and OPS when you want a fast blend of both.

What is a good OPS?

The completed 2025 MLB season produced a league-average .315 OBP and .404 SLG, which add to a .719 OPS. That gives a recent baseline, but there is no official MLB grading scale and offensive conditions change over time.

Treat those bands as orientation, not universal law. A .750 line can be strong for a catcher in a low-scoring year and disappointing for a first baseman in a high-offense season. Small samples can also make an OPS look extreme after one hot or cold week.

Do walks count in OPS?

Yes. A walk improves OBP, so it improves OPS. It does not improve SLG because slugging counts total bases from hits and divides them by at-bats. A walk is a plate appearance but not an at-bat.

Hits have a different effect: they count in OBP and also add one to four total bases in SLG. That means a home run affects both halves of OPS, while a walk affects only one. Reaching on an error does not count as reaching base in the standard OBP numerator, another reason the everyday phrase “gets on base” is slightly broader than the statistic.

OPS vs batting average, OBP and SLG

OPS is usually more informative than batting average alone, but each number answers a different question.

Batting average still has descriptive value, but it treats a single and home run equally and ignores walks. OPS catches both gaps quickly. It also works well beside BABIP when you are trying to decide whether a batting line is being lifted by an unusual rate of balls falling for hits.

What OPS+ changes

OPS+ puts raw OPS into league and ballpark context. The scale centers on 100:

• 100 is league average.
• 120 is 20 percent above league average.
• 80 is 20 percent below league average.

That makes OPS+ much better for comparing a Colorado hitter with a San Francisco hitter, or a star from 1968 with one from 2026. Raw OPS remains easier to calculate and read during a season, but it cannot tell you how friendly the park or run environment was.

OPS+ still does not measure defense or baserunning. For a broader player-value question, WAR tries to combine more parts of the game. For a more carefully weighted offensive rate, wRC+ estimates runs created relative to league average.

Where OPS falls short

OPS is useful partly because it is simple. That simplicity also creates its flaws:

1. It adds unlike scales. OBP and SLG have different denominators and ranges.
2. It weights the halves equally. Reaching base and slugging do not contribute to run scoring in exactly equal proportions.
3. It needs context. Park, league, season, position and sample size all affect how impressive a raw number is.
4. It covers hitting only. It says nothing about fielding and does not fully value baserunning.
5. Different profiles can look identical. A patient hitter and a power-first hitter can post the same OPS.

That does not make OPS bad. It makes it a first read rather than a final scouting report. Public baseball discussions often arrive at the same balanced conclusion: good hitters generally have good OPS figures, but the two components explain how they got there.

Career and single-season OPS records

MLB’s glossary lists Babe Ruth first in AL/NL history with a 1.164 career OPS. Barry Bonds holds the qualified single-season record at 1.422 in 2004. Those figures show why 1.000 is not the top of the scale, even though it is exceptional over a full season.

Records also need a qualification standard. A player can post a huge OPS in a handful of plate appearances, but league leaderboards require enough playing time to qualify. When comparing players, confirm the season, league, minimum plate appearances and whether the number is raw OPS or adjusted OPS+.

How to read OPS on a stat page

Use this three-step check:

1. Compare the OPS with that season’s league average.
2. Look at OBP and SLG separately to see whether patience, contact or power drives it.
3. Use OPS+ or wRC+ when park and era comparisons matter.

For pitchers, the same combined calculation may appear as OPS against. Lower is better because it describes what opposing hitters produced. Pair it with pitching measures such as ERA and WHIP instead of treating one rate as a complete evaluation.