OPS Calculator
Enter a hitter's counting stats to get OBP, SLG, and OPS (on-base plus slugging) all at once — plus total bases — and see how the combined number compares to the current MLB league average.
OBP vs. SLG contribution to OPS
How you compare
Your OPS vs. the current MLB league average
How OPS works
OPS combines two different offensive skills into one number: on-base percentage (how often a hitter avoids making an out) and slugging percentage (how many bases they average per at-bat, which captures power). Adding them together is a deliberately simple shortcut — not a perfectly weighted formula — but it correlates strongly with how many runs a lineup scores, which is why OPS became a mainstream stat even outside sabermetric circles.
How it’s calculated
Total bases (TB) = Singles + 2×Doubles + 3×Triples + 4×Home runs, where Singles = Hits − Doubles − Triples − Home runs. Slugging (SLG) = TB ÷ At-bats. On-base percentage (OBP) = (Hits + Walks + HBP) ÷ (At-bats + Walks + HBP + Sacrifice flies). OPS = OBP + SLG.
Educational estimate for any stat line you enter — not an official MLB or league statistics feed.
Worked example
A season line of 165 hits (30 doubles, 3 triples, 22 home runs) in 550 at-bats, with 60 walks, 5 HBP, and 6 sacrifice flies: total bases = 110 singles + 60 (doubles×2) + 9 (triples×3) + 88 (HR×4) = 267 TB. Slugging = 267 ÷ 550 = .485. OBP = (165+60+5) ÷ (550+60+5+6) = 230 ÷ 621 = .370. OPS = .370 + .485 = .856 — solidly in the “good” range, well above the 2025 MLB league average of .719.
Common mistakes
- Forgetting that total bases counts a single as 1 base, not 0 — the singles component (Hits minus 2B, 3B, HR) still contributes to TB.
- Mixing up SLG (uses at-bats) and OBP (uses a wider denominator including walks and sac flies) when computing each piece by hand.
- Treating OPS as perfectly weighted — OBP and SLG are simply added, even though a point of OBP is generally worth slightly more than a point of SLG.
- Comparing OPS across very different offensive eras without adjusting — a .750 OPS meant something different in 1968 than in 2000.
Where it is used
- A fast, single-number gauge of overall hitting value in box scores, broadcasts, and articles.
- Setting realistic performance tiers for fantasy baseball and scouting reports.
- The foundation for era-and-park-adjusted stats like OPS+ and wRC+.
Frequently asked questions
What is a good OPS in baseball?
Roughly: below .700 is below-average, .700-.799 is solid/average, .800-.899 is good, .900-.999 is very good to great, and 1.000+ is elite, MVP-caliber production. These bands move a little year to year with league offense levels — MLB's league-average OPS was .719 in the 2025 season (Baseball-Reference), so today .800+ is meaningfully above average.
Why is OPS just OBP plus SLG added together?
OPS is intentionally simple: it adds on-base percentage (how often a batter reaches base) to slugging percentage (how many bases they average per at-bat) into one number, on the theory that both getting on base and hitting for power matter and roughly offset each other in value. It's not a perfectly weighted stat — OBP is generally considered slightly more valuable per point than SLG — but OPS is popular because it's easy to calculate and correlates well with run scoring.
How is slugging percentage different from batting average?
Batting average treats every hit the same (a single counts the same as a home run); slugging percentage (SLG) weights hits by total bases — 1 for a single, 2 for a double, 3 for a triple, 4 for a home run — divided by at-bats. A hitter who mostly hits home runs can have a much higher SLG than BA, which is why SLG is used to capture power separately from pure contact rate.
What counts as an at-bat for these formulas?
At-bats exclude walks, hit-by-pitches, and sacrifice bunts/flies under MLB's official scoring rules — only balls put in play or strikeouts (and hits, of course) count as at-bats. Both slugging percentage and batting average use at-bats as their denominator, while on-base percentage uses a wider denominator that adds walks, HBP, and sacrifice flies back in.
Is OPS or OPS+ better for comparing players across eras?
Raw OPS is fine for comparing players within the same season, since they faced the same run-scoring environment — but league-wide OPS has moved around over baseball history (it was .782 in 2000 and .639 in the pitching-dominated 1968 season, for example), so the same raw OPS meant very different things in different years. OPS+ (or wRC+) adjusts for the era and ballpark, which is why analysts prefer it for cross-era comparisons; see our OPS+ calculator for that adjustment.