Swimming time calculator
1500 m at 1:30 per 100 m takes 22:30: enter the distance and the pace you can hold, and the calculator multiplies the hundreds by that pace to give your finish time. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Distance
- 1,500
- Pace
- 1.5
- Hundreds
- 15
- Time minutes
- 22.5
- Time seconds
- 1,350
- Time hours
- 0.375
A swimming time calculator answers the planning question every pool session raises: if you hold this pace per 100 metres, how long will a given distance take? Competitive swimmers, masters athletes, triathlon coaches, and meet officials already store interval pace as minutes per hundred metres, because split sheets, critical-swim-speed tests, and race entries are all expressed that way. Enter distance in metres and pace in minutes per 100 metres; the tool multiplies the number of hundreds in the distance by that pace and returns total time in minutes, plus seconds, hours, and a clock-style string.
What swimming time from pace per 100 metres actually means
Swimming time from a known pace is the linear projection of a split onto a race or set distance. If you swim one hundred metres in one and a half minutes, fifteen of those hundreds make a 1500 metre swim of twenty-two and a half minutes, provided the average rate holds. That assumption is the same one coaches write on a whiteboard: hold 1:30 per hundred through the set, and the clock for 400, 800, or 1500 follows by multiplication.
Pace here is minutes per 100 metres, not kilometres per hour and not minutes per kilometre, because pool programming, CSS tests, and FINA event boards all speak in hundred-metre splits. A decimal 1.5 is a 1:30 split; 1.25 is 1:15; 2 is a round two minutes per hundred. The capability does not model turns, current, or fading in the last 200 metres; it reports the exact product of hundreds times pace so you can compare a target against a stopwatch.
Use this landing when you already know the split you can hold and need the finish time; if you already have a finish time and want the split, that is the inverse problem of a swimming pace calculator, a different search with different fields.
Who plans with a swim time estimate
Squad coaches convert a CSS or threshold split into predicted 200, 400, 800, and 1500 times before they write the main set, so athletes see the clock they are chasing rather than a pace they have to multiply in their heads. Triathlon planners scale an open-water target from a pool hundred, then compare the projected minutes against the swim-start wave and the bike rack time.
Meet directors and timing volunteers fill heat sheets when an entry has a seed pace but not a recorded finish, using the same identity the swimmer used in training. Classroom exercise-science labs ask students to project time from pace so the arithmetic of rate times quantity is checked against a deterministic oracle instead of a spreadsheet that someone rounded twice. Convert yards to metres before you call if you train short-course yards; this contract is metres and minutes per hundred metres only, not a yards-to-metres pace converter.
Stay inside the published limits: distance up to 100 kilometres of open water, pace no slower than one hour per hundred metres.
What you can do with it
Interval sets and CSS projections
Coaches enter a threshold split in minutes per 100 m and a set distance to publish the clock athletes should see at 200, 400, 800, or 1500 metres.
Triathlon and open-water planning
Athletes scale a pool hundred into a predicted swim leg in minutes, then compare that duration against wave starts and bike-rack targets.
Heat sheets and training-log columns
Meet entries and workout diaries store distance and pace, then call this tool once to fill a consistent finish-time column without spreadsheet drift.
FAQ
How is swimming time calculated from pace per 100 metres?
Time in minutes equals (distance in metres divided by 100) multiplied by pace in minutes per 100 metres. A 1500 m swim at 1.5 min/100 m is 15 × 1.5 = 22.5 minutes (clock 22:30).
What units should I use for distance and pace?
Distance is metres. Pace is minutes per 100 metres (1.5 means a 1:30 / 100 m split). Convert yards to metres before you call; this contract does not accept a yards unit.
Does this invert a finish time into pace?
No. This landing projects time from a known pace and distance. If you already have a finish time and want pace per 100 m and per 100 yards, use a swimming pace calculator instead.
How long does a 1500 m swim take at 1:30 per 100 m?
22 minutes 30 seconds. 1500 metres is 15 hundreds, and 15 times 1.5 minutes is 22.5 minutes, shown as 22:30 on the clock.
How do I enter a pace like 1:15 per 100 m?
Type it as decimal minutes: 1:30 is 1.5, 1:15 is 1.25 and two minutes is 2. A 400 m swim at 1.25 minutes per hundred takes exactly five minutes.
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/swimming-time \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"distance":1500,"pace":1.5}'const res = await fetch("https://api.kit.forhosting.com/sports/swimming-time", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"distance": 1500,
"pace": 1.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/sports/swimming-time",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"distance": 1500,
"pace": 1.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/sports/swimming-time", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"distance":1500,"pace":1.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"distance":1500,"pace":1.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/sports/swimming-time", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"distance": 1500,
"pace": 1.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "sports.swimming_time",
"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_distance | 100000 |
max_pace | 60 |
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
Distance or pace that is zero or negative is rejected as invalid_input so a missing split never becomes an infinite or negative swim. The same pure arithmetic runs free in the browser and as a prepaid API call, so a 1500 metre estimate you check on this page is the same number a training log will persist.
What swimming time from pace per 100 metres actually means
Zero and negative inputs are not a slow swim: they are undefined as a rate or a length, so the task fails with invalid_input instead of returning zero minutes or a negative clock.
Input contract, formula, response shape, and errors
Zero or negative distance or pace is rejected with a message that zero or negative values are not allowed, and those failures are not billed. Example: 1500 metres at 1.5 minutes per 100 metres yields 15 hundreds, 22.5 minutes, 1350 seconds, 0.375 hours, and the clock 22:30. A 400 metre swim at 1.25 minutes per hundred is exactly five minutes. POST a JSON body with two required finite positive numbers. The field distance is the swim length in metres, greater than zero and at most one hundred thousand, with aliases dist, d, length, meters, metres, and distance_m. The field pace is minutes per 100 metres, greater than zero and at most sixty, with aliases pace_per_100, pace_100m, min_per_100, minutes_per_100, and pace_min. Each field may arrive as a JSON number or as a numeric string; empty strings, non-finite values, and missing keys fail with invalid_input naming the field. On success the body echoes cleaned distance and pace, publishes hundreds as distance divided by one hundred, and returns time_minutes as the primary result together with time_seconds, time_hours, and time_formatted as M:SS or H:MM:SS rounded to the nearest second. A formula string restates time_minutes equals (distance_m / 100) times pace_min_per_100m, and an ordered steps array shows the substitution. Successful API calls cost the published $0.002 per item; validation failures do not consume prepaid balance.
Where a swimming time API earns its keep
Failed tasks that return invalid_input do not consume prepaid balance. API pricing remains $0.002 per successful request with unit item.
Technical questions
What happens if distance or pace is zero or negative?
The task fails with invalid_input and is not billed. A zero or negative length or split is not a valid swim, so the API does not return a zero or negative clock.
What does the swimming time calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.