Slugging percentage calculator
Two singles, a double and a home run in 10 at-bats make 8 total bases and a slugging percentage of .800: enter the five counts from the scorebook and get the power number. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Singles
- 2
- Doubles
- 1
- Triples
- 0
- Home runs
- 1
- At bats
- 10
- Hits
- 4
- Total bases
- 8
- Slugging percentage
- 0.8
- Slugging percentage text
- 0.800
A baseball slugging percentage is total bases divided by official at-bats, reported to three decimal places in every box score, leaderboard, and baseball card. Unlike batting average, which treats every hit as one, slugging weights singles as one base, doubles as two, triples as three, and home runs as four. Coaches, scorekeepers, fantasy managers, and students need that extra-base power number from five counting stats: singles, doubles, triples, home runs, and at-bats. This slugging percentage calculator forms total bases as one times singles plus two times doubles plus three times triples plus four times home runs, then divides by at-bats and rounds the quotient to three decimals, matching the published convention that writes eight total bases in ten at-bats as .800. An at-bat total of zero is rejected because the percentage would divide by zero. Any negative hit count is rejected because official scoring cannot produce a negative single, double, triple, or home run.
What slugging percentage measures and why total bases are the numerator
Slugging percentage answers a power-hitting question that batting average cannot: of the official at-bats a batter took, how many bases did those at-bats produce? Official baseball scoring packs that idea into one identity: slugging percentage equals total bases divided by at-bats. Total bases count a single as one, a double as two, a triple as three, and a home run as four, so a batter who goes two-for-four with a double outslugs a batter who goes two-for-four with two singles.
The result is not written as a percent. Scoreboards, newspapers, and baseball-reference tables print it to three decimal places, dropping a leading zero so that eight total bases in ten at-bats appear as .800 and a four-homer game in four at-bats appears as 4.000. An at-bat is a plate appearance that ended in a hit, an out, or a fielder's choice; walks, hit-by-pitch, sacrifice bunts, sacrifice flies, and catcher's interference are not at-bats, so they do not enter this ratio.
That is why a patient hitter can post a modest slugging percentage and still reach base often: this calculator does not compute on-base percentage, batting average, OPS, or wOBA. It applies only the published total-bases-over-at-bats identity to the five numbers you already have. Zero extra-base hits with a positive at-bat count is a legal line; a batter who went hitless is a legal .000.
A season or a career with tens of thousands of at-bats uses the same identity as a single game.
Where a slugging percentage calculator earns its keep
Youth coaches and high-school scorekeepers need a reproducible slugging percentage so a lineup card, a tournament recap, and a parent spreadsheet never disagree on whether two singles and a double in five at-bats is .800. A publisher ranking for slugging percentage calculator is targeting people who already have the four hit types and an at-bat count and want the three-decimal extra-base ratio, not a projection system, not a Statcast spray chart, and not an on-base-plus-slugging explainer.
Fantasy managers who sit in a weekly waiver review need the same number the official box printed, so they can compare two hitters whose batting averages look similar but whose extra-base power is not. Classroom and coaching-certification courses that teach counting stats need an oracle that rejects zero at-bats, rejects a negative double, and still returns .000 when a batter went hitless, because those cases are how students confuse no slugging yet with a slugging of zero.
Engineers writing scorebook and recap tests pin known-good pairs—two singles, a double, and a homer over ten at-bats as .800, three total bases over seven at-bats rounded to .429, and a zero-at-bat rejection—so a reporting library cannot silently treat slugging as hits over at-bats. Failed validation does not consume balance.
What you can do with it
Box scores and recap pages
Enter official singles, doubles, triples, home runs, and at-bats to publish a three-decimal slugging percentage that matches the box score, whether the line is a single game, a series, or a season.
Fantasy and waiver comparisons
Convert two batting lines that look similar in average into slugging percentages so extra-base power and at-bat volume are visible in the same three-decimal figure.
FAQ
How do I calculate baseball slugging percentage?
Example: two singles, one double, and one home run in ten at-bats is 0.800, shown as .800 on a scoreboard.
What happens if at-bats is zero?
Slugging percentage divides by at-bats, so a zero denominator is rejected and is not billed.
What if a hit count is negative?
Official scoring cannot produce a negative single, double, triple, or home run, so that value is rejected rather than returning a nonsense slugging percentage.
How is slugging percentage different from batting average?
Batting average counts every hit as one over at-bats. Slugging weights extra-base hits: a double is two total bases, a triple is three, and a home run is four. A .300 batting average can sit next to a .500 slugging percentage when the hits are extra-base hits. This calculator does not return batting average.
Do walks and sacrifice flies count as at-bats?
No. Walks, hit-by-pitch, sacrifice bunts, sacrifice flies and catcher's interference are not at-bats, so they stay out of the ratio. Only plate appearances that end in a hit, an out or a fielder's choice count.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/sports/slugging-percentage \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"singles":2,"doubles":1,"triples":0,"home_runs":1,"at_bats":10}'const res = await fetch("https://api.kit.forhosting.com/sports/slugging-percentage", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"singles": 2,
"doubles": 1,
"triples": 0,
"home_runs": 1,
"at_bats": 10
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/sports/slugging-percentage",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"singles": 2,
"doubles": 1,
"triples": 0,
"home_runs": 1,
"at_bats": 10
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/sports/slugging-percentage", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"singles":2,"doubles":1,"triples":0,"home_runs":1,"at_bats":10}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"singles":2,"doubles":1,"triples":0,"home_runs":1,"at_bats":10}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/sports/slugging-percentage", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"singles": 2,
"doubles": 1,
"triples": 0,
"home_runs": 1,
"at_bats": 10
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "sports.slugging_percentage",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_abs | 1000000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Successful calls are billed at $0.002; invalid input is not charged.
What slugging percentage measures and why total bases are the numerator
This endpoint does not decide which events your scorebook counted as at-bats, does not park-adjust the result, and does not annualize a small sample.
Input contract, response shape, and validation
Values must stay within one million so a simulated season or a full career still fits, while pathological billions are rejected. Example: two singles, one double, zero triples, one home run, and ten at-bats yield eight total bases and 0.800. Prefer bare integers over formatted strings; percent signs, thousands separators, and the leading-dot box-score form are not parsed as input. POST a JSON body with five required integers. singles is the count of official one-base hits and must be a non-negative integer; aliases 1B, 1b, and single are accepted so a scorebook export does not need a rename step. doubles is the count of official two-base hits; aliases 2B, 2b, and double are accepted. triples is the count of official three-base hits; aliases 3B, 3b, and triple are accepted. home_runs is the count of official home runs; aliases HR, hr, homers, home_run, and homeruns are accepted. at_bats is the count of official at-bats over the same window and must be a strictly positive integer, because slugging percentage divides by at-bats; aliases at-bats, atbats, AB, ab, and at_bat are accepted. Each field may arrive as a JSON integer or as a numeric string that parses to an integer. Missing fields, empty strings, non-integers, negative counts, an at-bat total of zero, a hit total that exceeds at-bats, or a value outside those limits fail with invalid_input naming the field and are not billed. On success the body echoes singles, doubles, triples, home_runs, and at_bats, returns hits as the sum of the four hit types, total_bases as the weighted sum that feeds the ratio, slugging_percentage as the quotient rounded to three decimal places, slugging_percentage_text as that same value always written with three digits after the decimal so .800 does not collapse to 0.8 in a display, slugging_percentage_display in box-score form, and a formula string you can print next to the numbers. Pricing for a successful item is a flat $0.002.
Where a slugging percentage calculator earns its keep
Keep requests small, pin the three-decimal slugging_percentage_text in tests, and you get stable baseball arithmetic for widgets, recap pages, and edge workers without standing up a full stats service of your own.
Integration use cases
Coaching classes and scorebook tests
Students and QA pin two singles, a double, and a homer over ten at-bats as .800, three total bases over seven as .429, and zero at-bats as invalid_input.
Technical questions
What does the slugging percentage calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.