If you have typed ops in baseball terms into a search box, you have probably seen a single three-letter statistic quoted next to batting average and home runs, with very little explanation of where the number comes from. OPS is a combined batting statistic. It adds two separate rates together: how often a batter reaches base, and how much power that batter produces when putting the ball in play. Once you understand those two parts, the final number stops looking mysterious and starts looking useful.
This guide works through the calculation in order. It explains each ingredient, shows the arithmetic with a worked example, and then covers the mistakes people most often make when they first read the statistic. It does not assume you already know advanced baseball analysis. If you can add, divide, and follow a simple fraction, you can calculate OPS yourself.
ops in baseball terms: the two parts of the statistic
OPS stands for on-base plus slugging. The name is the formula. You calculate on-base percentage, you calculate slugging percentage, and then you add them. That is the whole calculation. There are no hidden weights, no extra adjustments in the basic version, and no multiplication step. The simplicity is part of why the statistic spread so widely: any fan with a box score can reproduce it.
On-base percentage, usually shortened to OBP, answers a narrow question: out of the plate appearances in which a batter had a chance to reach base, how often did the batter actually reach base safely? Slugging percentage, usually shortened to SLG, answers a different question: how many bases, on average, did the batter earn per at-bat? One measures patience and contact in a broad sense, and the other measures power. Adding them gives a single snapshot that rewards both skills at once.
It helps to think of the two parts as complementary rather than interchangeable. A batter who walks often but rarely hits for extra bases can have a strong on-base percentage and a modest slugging percentage. A batter who hits many home runs but rarely walks can show the reverse pattern. OPS treats both contributions as valuable, and a high total usually means a batter is doing at least one of those jobs very well, and often both.
Why two rates are added instead of averaged
Adding the rates, rather than averaging them, is a deliberate choice. An average would pull the result back toward the middle and hide the difference between a batter who is good at one skill and a batter who is good at both. A sum preserves that difference. A batter with a .350 on-base percentage and a .450 slugging percentage reaches .800, while a batter with a .400 on-base percentage and a .500 slugging percentage reaches .900. The gap is easy to read, and it grows when both parts improve together.
That also explains why OPS numbers look larger than batting averages. Batting average is a single rate that usually sits between .200 and .300 for a regular player. OPS combines two rates, so a good total is often around .800 or higher. Do not compare an OPS figure directly with a batting average. They are on different scales, and the comparison will only cause confusion.
ops in baseball terms: on-base percentage explained step by step
On-base percentage is calculated by dividing the number of times a batter reaches base by the number of plate appearances that count toward the statistic. The numerator is hits plus walks plus hit by pitch. The denominator is at-bats plus walks plus hit by pitch plus sacrifice flies. Sacrifice bunts are not included in the denominator, which is one of the details that catches beginners out.
Put into a formula, it looks like this: OBP equals hits plus walks plus hit by pitch, divided by at-bats plus walks plus hit by pitch plus sacrifice flies. Every part of that formula has a reason. Hits are the most obvious way to reach base. Walks show plate discipline, because a batter who refuses to chase bad pitches earns first base without swinging. Hit by pitch counts because the batter reached base through no fault of their own, and the rules award first base. Sacrifice flies count in the denominator because the batter gave up an out to move a runner, and the statistic does not want to reward that as if it were a normal opportunity to reach base.
Consider a simple example. Suppose a batter has 100 at-bats, 30 hits, 12 walks, 2 hit-by-pitch events, and 1 sacrifice fly. The numerator is 30 plus 12 plus 2, which is 44. The denominator is 100 plus 12 plus 2 plus 1, which is 115. Dividing 44 by 115 gives about .383. That batter reached base in roughly 38 percent of the counted opportunities, which is a strong result.
One common misunderstanding is to leave walks out of the calculation. That produces batting average, not on-base percentage. Batting average divides hits by at-bats only, so it ignores walks completely. A patient batter who walks ten times in a stretch will look ordinary by batting average and much better by on-base percentage. That difference is exactly why analysts wanted a statistic that included walks in the first place.
What counts and what does not count
Reaching base on an error does not count as a hit, and it does not raise on-base percentage in the same way a hit does, because the batter is not credited with reaching base through their own hit. Catcher interference is a rarer route to first base, and it is treated in the same family of reaching-base events in official scoring, but for most fans the main cases to remember are hits, walks, and hit by pitch. Fielder choice situations, where a runner is put out while the batter reaches safely, are also handled by the official rules rather than by the simple fan formula, so small differences can appear between a quick hand calculation and an official total.
The practical lesson is to use official totals when you want a precise figure, and use the simple formula when you want to understand how the figure is built. The simple formula teaches the logic. The official record keeps the edge cases consistent across every player and every team.
Slugging percentage explained step by step
Slugging percentage measures power per at-bat. Each type of hit is worth the number of bases it earns: a single is worth one, a double is worth two, a triple is worth three, and a home run is worth four. Add those bases together to get total bases, then divide by at-bats. Walks, hit by pitch, and sacrifice flies do not appear in slugging percentage at all, because the statistic is only interested in what happens when a batter puts the ball in play and is charged with an at-bat.
The formula is therefore: SLG equals total bases divided by at-bats, where total bases equals singles plus two times doubles plus three times triples plus four times home runs. Notice that the number of hits alone is not enough. Ten singles and ten extra-base hits can produce the same hit total with very different slugging percentages, because the extra-base hits carry more bases.
Take another example. Suppose a batter has 100 at-bats with 20 singles, 6 doubles, 1 triple, and 3 home runs. That is 30 hits in total. Total bases are 20 plus 12 plus 3 plus 12, which is 47. Dividing 47 by 100 gives .470. The batting average in this example is .300, and the slugging percentage is .470. The gap between those two numbers tells you that the batter is hitting for meaningful power, not just collecting singles.
Slugging percentage can rise above 1.000 in theory, although that would require averaging more than one base per at-bat over a stretch, which only happens in very short samples. In a full season, a slugging percentage above .600 is exceptional. Most regular players sit well below that, which is why a high slugging figure stands out immediately.
Why slugging ignores walks
Beginners sometimes ask why walks are left out of slugging percentage. The answer is that slugging is designed to measure damage done with the bat, not patience at the plate. Walks are already rewarded in on-base percentage, so including them again in slugging would double-count the same skill. By keeping the two parts separate, OPS rewards patience once and power once, and the sum reflects both without repeating either.
A full worked example: adding OBP and SLG
Now combine the two examples above into one player line, with a small adjustment so the numbers belong to the same imaginary season. Suppose a batter finishes with 100 at-bats, 30 hits, 12 walks, 2 hit-by-pitch events, and 1 sacrifice fly. The hits break down as 20 singles, 6 doubles, 1 triple, and 3 home runs. The on-base percentage, calculated earlier, is 44 divided by 115, or about .383. The slugging percentage is 47 divided by 100, or .470. Adding them gives .383 plus .470, which is .853.
That .853 is the OPS. It is usually written to three decimal places, without a leading zero in many scoreboards, so you will see it shown as .853. The same convention applies to the two parts: on-base percentage and slugging percentage are also shown to three decimal places. Keeping three places matters, because the difference between .850 and .870 can separate a good season from a very good one.
Try the same steps with a different profile to see how the total moves. A batter with many singles and few walks might have an on-base percentage of .320 and a slugging percentage of .380, giving an OPS of .700. A batter with fewer hits but many walks and several home runs might have an on-base percentage of .380 and a slugging percentage of .520, giving an OPS of .900. The second batter reaches base more often and hits for more power, and the OPS total reflects both advantages in a single number.
| Player profile | OBP | SLG | OPS |
|---|---|---|---|
| Balanced hitter in the worked example | .383 | .470 | .853 |
| Contact hitter, few walks, little power | .320 | .380 | .700 |
| Patient power hitter | .380 | .520 | .900 |
| Strong all-round season | .410 | .580 | .990 |
The table is illustrative rather than a record of real players. Its purpose is to show how the sum behaves: raise either part and the total rises by the same amount, and raise both parts and the total rises twice as fast. That simple behaviour makes OPS easy to use when comparing two batters at a glance.
How to read an OPS figure
As a rough guide, an OPS around .700 is serviceable for a regular player, an OPS around .800 is good, an OPS around .900 is excellent, and an OPS above 1.000 is outstanding. These are general guideposts, not official thresholds, and they shift with the run environment of a particular season. In a high-scoring season, averages rise across the league, and in a low-scoring season they fall. Always compare a batter with their contemporaries before drawing a firm conclusion.
Position matters as well. A shortstop or catcher who provides strong defence may be valuable with an OPS near .750, while a first baseman or designated hitter, whose main job is to hit, is usually expected to clear .800 to be considered a strong offensive contributor. Context does not change the arithmetic, but it changes what the arithmetic means.
Sample size matters even more. A batter who goes on a hot run for two weeks can post an OPS above 1.100, and a batter in a slump can fall below .500 over the same stretch. Neither figure, on its own, describes the batter’s true level. Analysts usually wait for hundreds of plate appearances before treating an OPS figure as a reliable description of a player, and even then they adjust for ballpark, opposition, and role.
Common mistakes when calculating OPS
The most frequent mistake is dividing by plate appearances instead of by the correct denominator for each part. On-base percentage uses a denominator that includes walks, hit by pitch, and sacrifice flies, while slugging percentage uses at-bats only. Mixing those denominators up produces a number that looks like OPS but is not. Keep the two calculations separate until the final addition, and the mistake disappears.
A second mistake is counting a sacrifice bunt as a sacrifice fly. Bunts laid down to move a runner are not charged as at-bats and do not enter the on-base denominator in the same way. A third mistake is forgetting that total bases weight each hit by its base value. Adding hits together and dividing by at-bats gives batting average, not slugging percentage. The weighting is the whole point of slugging, because a double is worth more than a single.
A fourth mistake is rounding too early. If you round on-base percentage and slugging percentage to two places before adding, you can be off by a full point or more in the third decimal place. Carry three places through the whole calculation and round only at the end. The difference is small, but when you are checking your work against a published figure, it is often the source of the mismatch.
Related guides on this site can help you practise reading baseball numbers in context, including a guide to baseball fantasy names and a guide to reading numbers in a different field, which shows how a single figure can mislead without its surrounding context.
Frequently asked questions
Is OPS the same as batting average?
No. Batting average divides hits by at-bats and ignores walks. OPS adds on-base percentage and slugging percentage, so it rewards walks and extra-base hits as well as ordinary hits. A batter can have a modest batting average and a strong OPS if they walk often and hit for power.
Can OPS be calculated from a box score?
Yes, provided the box score lists hits, doubles, triples, home runs, walks, hit by pitch, sacrifice flies, and at-bats. From those figures you can work out total bases, on-base percentage, and slugging percentage, and then add the last two together. If any ingredient is missing, the result will be an estimate rather than an exact figure.
Does OPS include fielding or baserunning?
No. OPS is purely a batting statistic. It says nothing about defence, speed on the bases, or arm strength. A complete evaluation of a player needs other measures alongside OPS, which is why teams use it as one tool among many rather than as a final verdict.
Why do some analysts prefer adjusted versions of OPS?
Because the basic version does not adjust for ballpark or league scoring levels. A batter in a hitter-friendly park will tend to post a higher raw OPS than the same batter in a pitcher-friendly park. Adjusted versions try to remove that effect so that players in different environments can be compared more fairly. The basic version remains popular because it is transparent and easy to reproduce.
Conclusion
Calculating OPS is a two-step job followed by one addition. First, work out how often the batter reaches base, counting hits, walks, and hit by pitch against the proper denominator. Second, work out how many bases the batter earns per at-bat, weighting each hit by its base value. Add the two results, keep three decimal places, and you have the statistic. Once you have done it once by hand, every OPS figure you see in a broadcast or a standings table will carry more meaning, because you will know exactly what went into it and what it leaves out.
