What Is OPS in Baseball?

Key takeaways

• OPS adds on-base percentage and slugging percentage. It is not a percentage of plate appearances that end successfully.
• OBP includes hits, walks and hit-by-pitches. SLG counts total bases from hits per at-bat.
• The same OPS can come from different combinations of reaching base and hitting for power.
• A good OPS depends on the league, season, ballpark and amount of playing time being compared.
• OPS+ adjusts for league and ballpark context, with 100 representing league average.
• OPS adds OBP and SLG equally even though equal changes in those components do not have equal value for run scoring.

What does on-base percentage measure?

On-base percentage measures how often a hitter reaches base through hits, walks or hit-by-pitches, using the opportunities included in its calculation. [2]

A walk is not a hit, but it still puts a batter on base. That is one reason OBP tells you something batting average cannot.

The standard formula is:

Here is what the abbreviations mean:

• H: hits.
• BB: walks, also called bases on balls.
• HBP: times hit by a pitch.
• AB: official at-bats.
• SF: sacrifice flies.

Sacrifice flies count in the denominator without adding a time on base to the numerator. Sacrifice bunts are excluded from this calculation. Reaching on an error, a fielder's choice or a dropped third strike does not count as reaching base for OBP. [2]

This is why saying OBP is simply “times on base divided by all plate appearances” is a useful first impression, but not a precise formula. Its numerator and denominator follow specific scoring rules.

In baseball notation, an OBP of .400 corresponds to 40 percent of the opportunities in its denominator. This is an illustrative value, not a current league benchmark.

What does slugging percentage measure?

Slugging percentage measures total bases from hits per official at-bat. A single contributes one base, a double two, a triple three and a home run four. [3]

The abbreviations 1B, 2B and 3B mean singles, doubles and triples. HR means home runs.

Despite the name, slugging percentage is not the percentage of at-bats that produce a hit. It is a rate of bases earned through hits. Its theoretical maximum is 4.000, because an at-bat producing a home run contributes four total bases.

Walks and hit-by-pitches do not enter the SLG calculation. Stolen bases do not count as total bases here either. SLG concerns the bases credited to the hit itself, not every base a player reaches during a game. [3]

Batting average treats every hit equally. Slugging percentage distinguishes a single from an extra-base hit, which makes it useful when describing a hitter's power production.

How is OPS calculated?

Once you have OBP and SLG, calculating OPS takes one addition:

The two components use different denominators. OBP includes walks, hit-by-pitches and sacrifice flies in addition to at-bats; SLG uses at-bats alone. OPS deliberately combines those two rates. [1][2][3]

OPS is not one combined success percentage. You should not read an OPS of .860 as an 86 percent chance of reaching base. It is the sum of two different measures.

For accuracy, calculate the underlying rates before rounding the final result. Adding already-rounded OBP and SLG values can occasionally produce a small difference from a provider's displayed OPS.

A fully worked hypothetical OPS example

Every value in this example is hypothetical and supplied for illustration. These are not real MLB player statistics or a league average.

Imagine a hitter with the following record:

Step 1: Calculate OBP

The hitter has 30 hits, 15 walks and 3 hit-by-pitches, giving 48 times on base that count toward OBP.

The denominator is 100 at-bats + 15 walks + 3 hit-by-pitches + 2 sacrifice flies = 120.

Step 2: Calculate SLG

Total bases from hits are:

• 20 singles × 1 = 20 bases.
• 6 doubles × 2 = 12 bases.
• 2 triples × 3 = 6 bases.
• 2 home runs × 4 = 8 bases.

That is 46 total bases in 100 at-bats.

Step 3: Add the components

The hypothetical hitter's batting average is 30 ÷ 100 = .300. That number describes hits per at-bat, while the .860 OPS also reflects walks, hit-by-pitches and extra-base production.

Two hypothetical players with the same OPS

This comparison is illustrative. Player A uses the worked example above; Player B is a separate invented rate example, not a real player.

Player A reaches base more often according to OBP. Player B records more total bases per at-bat according to SLG. Their OPS is identical because one component offsets the other in the addition.

That does not establish that they contribute equally to run scoring or have equal overall value. Keep the components visible rather than treating the combined figure as the entire story.

Why does OPS tell you more than batting average?

Batting average answers one question: how often does the batter get a hit per at-bat?

OPS widens the picture in two ways. OBP recognizes walks and hit-by-pitches, while SLG gives extra-base hits more weight than singles. [1][2][3]

A hitter who draws walks contributes something that batting average does not record. A hitter whose hits include more doubles and home runs contributes something batting average does not distinguish.

This does not make batting average useless. It means batting average, OBP and SLG describe different aspects of hitting. OPS brings two of those aspects together in a familiar summary.

For a broader explanation of how statistics complement watching a game, read Sports Analytics: Understanding the Game Through Data.

What is a good OPS in baseball?

A good OPS is one that compares favorably with the relevant hitting environment over a meaningful sample. There is no single cutoff that works for every league, season and comparison.

A number that looks strong in a lower-scoring season might be less remarkable in a higher-scoring one. Different leagues and levels of competition also have different environments. A short hot streak and a full season are not equivalent evidence.

Before deciding whether an OPS is good, ask:

1. Which league and season does this figure describe?
2. What is the corresponding league OPS or an appropriate comparison group?
3. How much playing time is included?
4. Does the hitter play in an environment that helps or suppresses offense?
5. Are you comparing ordinary OPS or an adjusted statistic such as OPS+?

A useful description might be “above the league average for that season,” supported by a named, dated source. It is more informative than assigning an unexplained label to a fixed number.

This guide deliberately does not provide a current league average or a universal rating chart. Use the season and source attached to the figures you are reading.

Why do league, season, ballpark and sample size matter?

League and season

Hitting does not take place in a fixed environment. Comparisons across leagues or years need the relevant baseline. OPS+ is designed to help with league-relative interpretation. [4]

Ballpark

Ordinary OPS does not account for ballpark effects. MLB's glossary specifically notes that factors such as dimensions or altitude can affect interpretation, and that OPS+ attempts to adjust for those factors. [4]

An adjustment is not the same as simply removing every home game. It is part of the statistical method used to account for the environment. Check the provider's documentation when using adjusted figures.

Sample size

OPS changes as new results are added. A few walks or extra-base hits can move a short-sample figure substantially. That is a reason to look at playing time, not a reason to dismiss every short sample.

There is no magic number of games after which OPS becomes a complete judgment of ability. The opponents faced, player role and purpose of the comparison still matter.

If you want to judge a team, use the team's combined underlying totals rather than a simple average of each player's OPS. Players contribute different amounts of playing time, and the two components have different denominators.

What is OPS+, and how is it different from OPS?

OPS+ is a league- and park-adjusted offensive index with 100 representing league average. It puts performance into context rather than displaying the raw sum of OBP and SLG. [4][5]

On that adjusted index:

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

These values illustrate how to read the scale; they are not player statistics. An OPS+ of 120 does not mean the hitter's raw OPS is exactly 20 percent higher than raw league OPS, nor that the player generated 20 percent more total runs. It describes relative performance on the adjusted OPS+ scale.

The simplified formula, and its limits

MLB displays this formula in its OPS+ glossary:

Here, lgOBP and lgSLG mean the corresponding league on-base and slugging rates. Comparing each component with its league rate explains the league-relative structure. If both component ratios equal 1, the expression becomes 100 × (1 + 1 − 1) = 100. [4]

This displayed expression is not a complete, reproducible park-adjusted implementation. MLB describes OPS+ as accounting for ballparks, but its short glossary formula does not show how those adjustments are applied. Do not calculate this expression using raw league averages and assume you have recreated a published provider's OPS+.

League adjustment asks how the hitter compares with the relevant league baseline. Park adjustment addresses the influence of the ballpark environment. They serve different purposes, even though both contribute to the reported adjusted index. Use the provider's finished statistic and methodology for comparisons that require those adjustments. [4][5]

What are the limitations of OPS?

OBP and SLG are not equally valuable for run scoring

OPS gives a .010 change in OBP the same numerical effect as a .010 change in SLG. Each adds .010 to the total.

That arithmetic does not mean the changes have equal value for scoring runs. FanGraphs' explanatory material describes OBP as roughly twice as valuable as SLG in this comparison, citing an approximate ratio of 1.8. [5][6]

Treat that ratio as an explanatory approximation, not a universal law, a new OPS formula or a rule for comparing any two players. The important point is that simple addition does not weight the components according to their run-scoring contributions.

The same total can hide different profiles

The hypothetical .860 comparison above shows why checking OBP and SLG separately matters. One hitter can reach base more often while another produces more bases per at-bat, even when OPS is identical.

OPS does not describe the whole player

OPS does not include fielding, stolen bases or every other baserunning contribution. It does not tell you when hits occurred, guarantee future performance or establish why a hitter's results changed.

Ordinary OPS also leaves league and park context to the reader. OPS+ helps address that issue, but an adjusted offensive index is still not a complete player evaluation.

How does OPS relate to wOBA and wRC+?

You do not need to master every advanced statistic to understand OPS. Two related measures are useful when you want to go further.

wOBA, or weighted on-base average, weights offensive events according to their run value rather than simply adding OBP and SLG. A walk, single and home run receive different weights. FanGraphs explains that those weights change by season. Ordinary wOBA is not itself the park- and league-adjusted index described below. [6][7]

wRC+, or weighted runs created plus, builds on weighted offensive production and accounts for league and park context. Its scale also uses 100 for league average. It is not another name for OPS+, and the two methods should not be treated as interchangeable. [7]

A sensible progression is to start with OBP and SLG, use OPS as a summary, then consult adjusted and weighted measures when the question calls for them.

The same habit helps in other sports: identify what a statistic measures before treating it as a verdict. Our guides to NBA offensive rating and expected goals in soccer explore that idea in different settings. Neither is a direct baseball equivalent of OPS.

Sources and further reading

Definitions and methodological explanations were checked on October 17, 2026. This is a research verification date, not an article publication date. Numerical examples in this guide are hypothetical unless they describe a statistic's defined scale.

1. MLB, On-base Plus Slugging (OPS). Definition of OPS and the relationship between reaching base and hitting production. Read the glossary.
2. MLB, On-base Percentage (OBP). Included ways of reaching base and exclusions, including sacrifice bunts. Read the glossary.
3. MLB, Slugging Percentage (SLG). Total bases per at-bat, the hit-weighting formula and exclusion of walks and hit-by-pitches. Read the glossary.
4. MLB, On-base Plus Slugging Plus (OPS+). League-average scale, park and league context, and the displayed simplified formula. Read the glossary.
5. FanGraphs Library, OPS and OPS+. Component-weighting limitations and adjusted-statistic interpretation. Read the explanation.
6. FanGraphs Library, wOBA. Run-value weights, season-specific coefficients and the limitations of simpler hitting statistics. Read the explanation.
7. FanGraphs Library, wRC and wRC+. Weighted offensive production, league and park adjustments, and index interpretation. Read the explanation.

Optional related reading: Baseball-Reference OPS glossary. Automated access to this glossary was blocked during verification. No factual claims in this article depend on that page.

Understand sports through data

SportQuantix is a sports intelligence platform in development. This guide is educational; it does not claim that SportQuantix currently provides live MLB statistics or proprietary baseball analytics.

Pre-register for a free account to hear when the platform goes live. Your account stays pending until launch.

Pre-register free