Slugging Percentage Calculator

What slugging percentage measures

Slugging percentage answers one narrow question: how many bases did a hitter collect for each at-bat he used up? MLB's own glossary defines it as "the total number of bases a player records per at-bat" and prints the formula as (1B + 2B x 2 + 3B x 3 + HR x 4) / AB. The league keeps a separate glossary entry for total bases, and the two pages describe the same arithmetic from opposite ends.

The name oversells what the number is. Slugging is not a percentage the way a test score is a percentage. It is an average of bases per at-bat on a scale that runs from 0 to 4.000, and big league hitters almost never pass 1.000 across a season. A 4.000 would mean a home run in every at-bat.

That scale is what separates power from contact. Batting average counts a bloop single and a 440 foot drive as one hit each. Slugging pays the single one base and the home run four, so a hitter who trades average for damage shows up in this column long before his batting average moves.

The formula, step by step

Four steps cover every calculation, and the tool above runs them in this order.

1. Count singles. Box scores list hits and extra-base hits, so singles are hits minus doubles, triples and home runs. This is the step people skip.
2. Weight each hit type: single 1, double 2, triple 3, home run 4.
3. Add the weighted values. That sum is total bases.
4. Divide total bases by at-bats.

Walks, hit-by-pitches, sacrifice bunts, sacrifice flies and catcher's interference enter neither the numerator nor the denominator, because none of them is an at-bat. A walk lifts on-base percentage and leaves slugging untouched, which is the reason OPS adds the two stats rather than picking one.

The counts in that table describe a fictional 486 at-bat season used through this page: 80 singles, 27 doubles, 4 triples and 21 home runs. Add the last column and total bases come to 230.

A full season line, worked end to end

Start with 486 at-bats and 132 hits split as 80 singles, 27 doubles, 4 triples and 21 home runs. Total bases are 80 + 54 + 12 + 84 = 230. Slugging is 230 / 486 = 0.47325, written the way a scoreboard writes it: .473.

Three related numbers fall out of the same inputs. Batting average is 132 / 486 = 0.27160, written .272. Isolated power, which is slugging minus batting average, is 0.47325 - 0.27160 = 0.20165, written .202, and it strips the singles out of the power picture. Add an on-base percentage of .350 and OPS lands at .823. Each stat uses a different slice of one line score, and the table shows how they line up.

A .473 slugging line with a .272 average is a productive regular. The gap between slugging and average on this line is about 200 points, and that gap is the power premium: bases that came from doubles, triples and homers rather than singles.

What counts as an at-bat, and what does not

At-bats are the denominator, so the definition matters more than it looks. A plate appearance becomes an at-bat unless the batter walks, is hit by a pitch, reaches on catcher's interference, or puts down a sacrifice bunt. A sacrifice fly also stays out of the at-bat column.

Two consequences follow. A walk-heavy hitter can carry a strong on-base percentage with a modest slugging percentage, because 60 walks add nothing above the line and nothing below it. And a player who goes 0 for 3 with a walk has an SLG of .000 for the day, not .250: the walk does not dilute the zero.

Stolen bases, wild pitches and advancing on an error do not count either. Total bases move only when the bat makes contact and the ball falls for a hit. A runner who steals second, third and home on three straight pitches adds three bases on the paths and zero to his slugging percentage, even though the team just scored.

Scorekeepers decide some of these calls, not players. A ruling changed from error to hit after the game can move a season slugging percentage by a point or two, which is one reason published stats sometimes shift in the days that follow.

What a good slugging percentage looks like

Context decides, and the league supplies the context. In 2025 MLB hitters combined for 66,089 total bases over 163,664 at-bats, a .404 league slugging percentage according to Baseball-Reference's 2025 league page. MLB's own Statcast leaderboard lists the same .404 average for the season, so the two sources agree to the point.

Aaron Judge topped qualified hitters at .688 in 2025 on that same leaderboard. The .473 example above sits 69 points over the league average, which is a good everyday regular rather than a star.

Those bands are scouting shorthand, not an official MLB threshold, and they drift with the run environment. A .450 season in a low-scoring year can rank higher than a .450 season in a slugfest, which is why park and era adjustments exist.

Slugging against average, OBP and OPS

Batting average and slugging share a denominator, so the comparison is clean. Average counts hits, slugging counts bases. A hitter with 150 hits in 500 at-bats has a .300 average whether those hits were all singles or included 40 homers, while slugging splits those two seasons into .300 and .540, because 110 singles plus 40 homers is 270 total bases over 500 at-bats.

On-base percentage answers a different question: how often did the plate appearance end with the batter standing on first base or further? It counts walks and hit-by-pitches, which slugging ignores, and it ignores the difference between a single and a homer, which slugging captures. OPS adds the two on the theory that reaching base and hitting for power are both worth runs, and the sum tracks team scoring better than either part alone.

Isolated power is the quiet one. Subtract batting average from slugging and what remains is extra bases per at-bat. A hitter at .330 slugging and .300 average has an ISO of .030 and almost no gap power, while a .240 hitter at .480 slugging carries a .240 ISO and a completely different skill set.

Where slugging misleads, and how to use it well

Park effects are the first trap. A hitter who plays half his games in a friendly park will out-slug his road numbers, and a season split between two parks can look better than the underlying contact quality. Park adjusted stats such as OPS+ exist to pull that distortion out, and they set 100 as league average.

Era is the second. League slugging has swung by more than 60 points across recent decades as the baseball, the strike zone and pitching usage changed, so a .430 season means something different in 1968 than in 2019. Compare a player with his own league and season, not with a number from a highlight reel.

Sample size is the third. Slugging needs a few hundred at-bats before it settles, so a short tear with four homers in 40 at-bats, a .400 pace, tells you little about the next 400. The math is unforgiving: small samples swing the number hard in both directions.

Used with those caveats, the stat earns its place. It prices power in one number, it is easy to recompute from a box score, and it explains why a team with a .450 slugging percentage scores more than a team with a .380 mark even when their batting averages match.