Race pace band calculator
A 10 km goal of 50 minutes becomes ten marks at 5:00 each, and a 3:30:00 marathon becomes an even 4:58.613 per kilometre that lands exactly on 42.195 km. Enter your goal time and race distance to print the band. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Hours
- 0 km
- Minutes
- 50
- Seconds
- 0
- Distance
- 10
- Finish seconds
- 3,000 km
- Finish clock
- 50:00
- Pace seconds
- 300
- Pace clock
- 5:00
A ten-kilometre goal of fifty minutes becomes ten five-minute marks. A three-hour-thirty marathon becomes a 4:58.613-per-kilometre band that lands exactly on 3:30:00 at 42.195 km.
How even pace-band splits are computed from a finishing time
A race pace band starts from the number on the finish-line banner, not from a spoken pace. Divide those finish seconds by the race distance expressed in the chosen unit. The quotient is the even pace in seconds per kilometre or per statute mile — one constant that every mark will share.
Marks are then laid at 1, 2, 3, and so on until a mark would pass the race distance; the finish is appended as the last mark so a 42.195 kilometre marathon always ends on 42.195, never on a fictional 43, and a 13.1 mile half marathon always ends on 13.1. The elapsed clock at a mark is the mark times that even pace, because even splits mean time grows linearly with distance.
The segment time for a row is the elapsed clock minus the previous elapsed clock, which equals one unit times the pace for every full kilometre or mile and equals the leftover distance times the pace for a short closer. A ten kilometre race in fifty minutes therefore prints 5:00, 10:00, through 50:00. A marathon in three hours thirty minutes prints a 4:58.613-per-kilometre band and a 3:30:00 finish.
Negative distances, a zero finish, or a unit other than km or mi are rejected as invalid input rather than silently wrapped, because a printed band that invents a lap is worse than no band at all.
What to enter, how the clocks read, and limits
Each time part defaults to zero; at least one part must be strictly positive so a blank form never prints a zero-pace fantasy. Hours may be as large as 2400; minutes and seconds may carry overflow — 90 seconds is one and a half minutes, and 210 minutes is a valid 3:30 finish without using the hours field. Optional unit is km or mi and defaults to kilometres; it sets both the distance unit and the split interval, which is always one of that unit.
Each numeric field also accepts a decimal string. Clocks use M:SS or H:MM:SS, with milliseconds only when the arithmetic is not a whole second, so a five-minute kilometre prints 5:00 and a 298.613 second kilometre prints 4:58.613. A copyable table field joins the same rows as tab-separated mark, segment, and elapsed columns.
At most five thousand rows are emitted. Failed validation is not billed.
Where a race pace band from a goal finish earns its keep
Marathon and half-marathon planners pick a clock first — Boston, a club standard, or a personal-best attempt — and only then want the kilometre or mile checks that keep that clock honest. Printing the band from the finish time avoids a two-step conversion through pace that drops a second and then refuses to add back up at 42.195.
Club coaches hand a beginner a 10K or half-marathon band so the first-hour surge does not bankrupt the last 5K: the athlete hits the printed elapsed clock at each kilometre instead of chasing a pack. Ultra and long-training days use the same numbers at mile marks on a 50-kilometre or 30-mile outing, because remembering 3:29:02 at 42 kilometres is easier than multiplying a messy pace by 42 on the run.
Treadmill and track sessions that target a constant goal time use the band as lap goals — twelve four-hundred-metre laps that must sum to a 20-minute 5K are four minutes of work each, and the calculator makes the cumulative column so the watch lap and the plan agree. Keep requests inside the published limits, pin the rounded clocks in tests, and you get reproducible race pace band splits for homework of the running kind, club newsletters, and edge workers without standing up a sports-science stack of your own.
What you can do with it
Marathon and half-marathon wristbands
Type a 3:30:00 or 1:45:00 goal and print even clocks at every kilometre or mile, including the 42.195 km or 13.1 mi closer, so the watch and the band agree at the finish.
Club 5K and 10K goal bands
Turn a fifty-minute 10K or a twenty-five-minute 5K into ten or five identical split clocks a beginner can check without converting minutes per kilometre mid-race.
FAQ
How do I build a race pace band from a goal finish time?
Send distance plus hours, minutes, and/or seconds. Elapsed time at a mark is mark × that pace.
What is a pace band, and how is it different from entering a target pace?
A pace band starts from the clock you want on the finish banner and derives the even split at each kilometre or mile. You do not type minutes-per-kilometre; you type 3:30:00 or 50:00 and receive the band that lands on that finish.
How are leftover kilometres or miles such as 42.195 or 13.1 handled?
The last row is a shorter leftover that ends exactly at the race distance. A 42.195 km marathon therefore ends with a 0.195 km closer, not a fictional 43 km mark. The finish clock equals the time you sent.
Can I print mile splits for a kilometre-measured race?
Yes, if you first express the race in miles and set unit to mi. Distance, each mark, and the derived even pace then all use statute miles, so a 26.21875 mile marathon uses the same even-pace arithmetic.
Can I enter my goal as 210 minutes instead of 3 hours 30?
Yes. Minutes and seconds may run over, so 210 minutes with the hours left at zero is the same 3:30 finish, and 90 seconds counts as one and a half minutes. At least one part must be above zero.
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/health/pace-band-splits \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"distance":10,"minutes":50}'const res = await fetch("https://api.kit.forhosting.com/health/pace-band-splits", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"distance": 10,
"minutes": 50
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/pace-band-splits",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"distance": 10,
"minutes": 50
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/pace-band-splits", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"distance":10,"minutes":50}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"distance":10,"minutes":50}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/pace-band-splits", 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": 10,
"minutes": 50
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.pace_band_splits",
"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 | 1000 |
max_time_seconds | 8640000 |
max_splits | 5000 |
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
Invalid or non-positive inputs fail with invalid_input and are not billed.
How even pace-band splits are computed from a finishing time
Convert the goal into seconds: hours times 3600 plus minutes times 60 plus the seconds remainder. That total is the only time the calculator needs; 210 minutes with hours left at zero is the same three-hour-thirty finish as hours 3 and minutes 30.
Inputs, clocks, limits, and what the response contains
POST a JSON body with distance, a positive finite race length at most one thousand units, and a finishing time built from optional hours, minutes, and seconds. The response echoes the resolved inputs, reports finish_seconds and a finish_clock such as 3:30:00, then lists pace_seconds, a pace_clock such as 4:58.613, and split_count. Successful API calls use the published $0.002 base price. Pair the JSON with your own watch face or sheet if you need colours or negative splits — this endpoint models even pace from a goal finish only and never consults a GPS file or the wall clock.
Integration use cases
Preview pages and training-plan APIs
Generate thousands of deterministic pace-band tables from finish time, distance, and unit so a race-preview site or coaching API never disagrees with the free browser widget.
Technical questions
What does the race pace band splits calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.