Average speed calculator
Covering 120,000 metres in 7,200 seconds, every stop included, is an average of 60 km/h. Enter the path distance and the total elapsed time to get the overall average speed in metres per second and kilometres per hour for trip logs or homework. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Distance
- 120,000
- Time
- 7,200
- Average speed mps
- 16.6666666667
- Average speed kmh
- 60
Overall average speed for a trip is the total path distance travelled divided by the total elapsed wall-clock time, including every stop for lights, fuel, rest, or traffic. The defining relation is simply average speed equals distance over time. When distance is measured in metres and time in seconds, the result is metres per second; multiplying by three point six converts to kilometres per hour for road and logistics contexts. Unlike average velocity, which uses signed straight-line displacement and can be zero on a round trip, average speed always uses path length and stays non-negative. Drivers, fleet planners, cycling coaches, and students use this one-line formula constantly for trip logs, homework checks, and first-pass ETA estimates. This calculator accepts total distance and total elapsed time, returns average speed in both m/s and km/h, flags that stops are included in the duration, and rejects zero elapsed time with a clear validation error instead of producing infinity.
How overall average speed is defined and computed
Begin with the total length of the path actually travelled, the quantity an odometer or GPS track reports as distance, not the straight-line displacement between start and finish. Elapsed time is the full wall-clock duration from departure to arrival, including every pause: traffic lights, fuel stops, rest breaks, and congestion all count. Overall average speed is defined as that path distance divided by that elapsed time.
The single quotient is the constant speed you would need to cover the same path in the same total time if motion never paused. Because the denominator includes idle time, trip average speed is usually lower than the speeds you held while moving. When distance is zero, average speed is zero for any nonzero duration.
Distance cannot be negative for path length; signed net progress belongs to average velocity, a different quantity and a different search intent. Converting metres per second to kilometres per hour multiplies by three point six because one kilometre is one thousand metres and one hour is three thousand six hundred seconds. Both fields must be finite; NaN and Infinity are rejected.
The special case of zero or vanishingly small elapsed time is rejected with invalid input because division by zero is undefined and would not represent a physical average over a trip interval.
What you send and what you get back
Send two required finite numbers under the fields distance and time. Distance is total path length in metres or any consistent length unit; zero is allowed, negatives are not. Time is total elapsed duration including stops, in seconds or any consistent time unit, and must be nonzero.
Classic checks include one hundred twenty kilometres in two hours for sixty kilometres per hour when you pass metres and seconds consistently, a short urban hop with long idle time that pulls the mean well below cruise, and zero distance for a stationary wait. Wire the free browser form for homework and quick trip logs, then call the identical contract from scripts when you need bulk answer keys or fleet tables.
Where average speed calculators show up in real work
Secondary-school physics and road-safety lessons compare average speed with average velocity, assign distance-over-time drills, and require students to include stop time honestly; a single trusted oracle speeds grading and demo setup. Fleet and logistics teams convert odometer kilometres and scheduled gate-to-gate durations into mean trip speeds as a first filter before full traffic models. Cycling and running coaches turn stage distances and elapsed split times into mean speeds for pacing tables without re-deriving unit conversions each session.
Tourism and commute planners estimate realistic door-to-door averages including known parking or border waits. If you later need signed average velocity from displacement, multi-leg harmonic means from segment speeds only, fuel economy conversions, or instantaneous speed from derivatives, treat those as separate search intents and landings rather than overloading this average speed calculator page.
What you can do with it
Homework and lab answer keys
Compute overall average speed from total path distance and elapsed time so students and auto-graders share one closed-form ground truth in m/s and km/h.
Trip logs and fleet mean-speed tables
Turn odometer distance and gate-to-gate duration including stops into trip average speed before full traffic or routing models.
Sports pacing with rest included
Convert stage distances and full elapsed times into mean speeds for training plans that count aid-station stops in the clock.
FAQ
What is overall average speed?
Total path distance divided by total elapsed wall-clock time. Stops count in the duration, so the result is trip mean speed, not cruise-only speed.
How is this different from average velocity?
Average speed uses non-negative path length. Average velocity uses signed displacement and can be zero on a round trip even when the odometer is large.
What happens if elapsed time is zero?
Average speed is distance divided by time; zero elapsed time is undefined (division by zero).
What does it cost?
The browser tool is free and runs locally.
Why is my average speed lower than the speed I was driving?
Because the elapsed time includes every stop, from traffic lights to fuel and rest breaks. The result is the constant speed that would cover the same path in the same total time, so idle minutes pull it below your moving speed.
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/travel/average-speed \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"distance":120,"time":7200}'const res = await fetch("https://api.kit.forhosting.com/travel/average-speed", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"distance": 120,
"time": 7200
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel/average-speed",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"distance": 120,
"time": 7200
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel/average-speed", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"distance":120,"time":7200}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"distance":120,"time":7200}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel/average-speed", 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": 120,
"time": 7200
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel.average_speed",
"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.
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
How overall average speed is defined and computed
The entire pipeline is deterministic floating-point arithmetic: no random seeds, no wall-clock timestamps, no network calls, and no model drift, so identical inputs always produce identical JSON.
What you send and what you get back
Missing fields, non-numeric strings, NaN, Infinity, and negative distance fail with invalid_input and are not charged. When time is zero or extremely close to zero the request fails with a message that average speed is distance divided by elapsed time and zero elapsed time is undefined, so clients can fix clocks or intervals rather than guessing. On success the response echoes cleaned inputs, average_speed_mps as the primary SI result, average_speed_kmh as the road-unit conversion, includes_stops set to true so callers remember the duration is wall-clock, a units hint object, method set to average_speed_distance_over_elapsed_time, and a short formula string for display. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where average speed calculators show up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Technical questions
What units should I use?
Use consistent length and time units. When distance is metres and time is seconds, the API returns m/s and also km/h via the factor 3.6.