Free Speed Distance Time Calculator Online

Speed, Distance & Time Calculator: Solve Any One From the Other Two

Speed, distance, and time are locked together by one of the oldest formulas in physics: speed equals distance divided by time. This calculator rearranges that relationship so it can solve for whichever of the three you don't already know — supply distance and time and it returns speed, supply speed and time and it returns distance, or supply speed and distance and it returns time. Enter numbers into the page and the missing value appears immediately, calculated as JavaScript running in your browser with no upload step and no server delay.

This kind of calculation surfaces constantly outside a physics classroom: estimating how long a drive will take at a given average speed, working out how fast you'd need to travel to make a deadline, or checking a reported average speed against a known distance and elapsed time to see if the numbers actually add up. Doing the algebra by hand each time is trivial once you remember which variable to isolate, but a calculator removes even that small friction.

How to Use This Calculator

1. Choose which value you want the page to solve for: Find speed, Find distance, or Find time.
2. Fill in the two fields that remain. Speed is entered in kilometers per hour, distance in kilometers, and time as separate hours and minutes fields that combine into a decimal number of hours behind the scenes.
3. Once both required fields hold a positive value, three result cards appear at once — the value you solved for, plus a couple of unit conversions of that same figure for convenience.
4. In "Find speed" mode, the cards show the speed in km/h, the same speed converted to mph, and the same speed converted to meters per second.
5. In "Find distance" mode, the cards show distance in kilometers, miles, and meters. In "Find time" mode, the cards show time as hours and minutes, total minutes, and total decimal hours.

Unit Coverage: What This Page Accepts

It's worth being precise about which units this particular page works with, since the underlying calculation supports more flexibility than the on-page form exposes. As built, the page only accepts speed in kilometers per hour, distance in kilometers, and time as hours plus minutes for input — there's no dropdown here to switch the input fields to miles or mph directly. What you do get is automatic conversion on the output side: whichever quantity you solve for is displayed in km/h, mph, and m/s (for speed), or km, miles, and meters (for distance), so you can read the answer in whichever unit you actually need even though you typed the other two values in metric.

If you need to enter distance in miles, time in seconds, or speed directly in mph or meters per second rather than converting by hand first, the same speed/distance/time solver is available through this site's metered API, which accepts distance in miles, kilometers, or meters, time in hours, minutes, or seconds, and speed in mph, km/h, or m/s, in any combination — every value is converted through a shared internal unit before the math runs, so mixing units across the three fields (say, distance in miles with time in minutes) works correctly rather than silently producing a wrong answer.

The Kinematics Formula Behind It

The core relationship is speed = distance ÷ time. The other two forms follow directly by rearranging: distance = speed × time, and time = distance ÷ speed. This is the same formula taught in an introductory physics or driver's-education context, just applied to whichever variable happens to be missing from what you already know. The math assumes a constant, or average, speed across the entire distance and time — it doesn't (and can't) account for a trip that included stops, acceleration, or varying speed along the way, since only the overall average is recoverable from total distance and total time.

Worked Example on the Page: 150 Kilometers in 2.5 Hours

Set the mode to "Find speed," enter a distance of 150 kilometers, and enter 2 hours plus 30 minutes for the time (which combines to 2.5 hours). Dividing distance by time: 150 ÷ 2.5 = 60 km/h. The result cards then show that same speed converted to roughly 37.28 mph and roughly 16.67 m/s, so you can read the answer in whichever unit matches how you're used to thinking about speed, without needing to do that conversion separately.

A Second Worked Example in Miles and Hours

For a case that matches the units the API accepts directly rather than the km/h-only page form: 100 miles covered in 2 hours gives a speed of 100 ÷ 2 = 50 mph. Rearranged the other two ways, the same relationship confirms itself — 50 mph held for 2 hours covers 50 × 2 = 100 miles, and covering 100 miles at 50 mph takes 100 ÷ 50 = 2 hours. Whichever two of the three numbers you start with, the third one is fully determined; there's no additional information needed to pin it down.

Familiar Speeds as a Reference Point

Because the result cards show a computed speed in three different units at once, it helps to have a few familiar reference points in mind for judging whether a number looks reasonable. A brisk walking pace is roughly 5 km/h (about 3 mph). Casual cycling often falls somewhere around 15 to 20 km/h. Highway driving speeds in many places cluster around 100 to 120 km/h, which converts to roughly 60 to 75 mph. A commercial jet's typical cruising speed is in the neighborhood of 900 km/h. None of these figures come from the calculator itself — they're just everyday anchors — but they're useful for a quick gut check: if you solve for speed and the result comes back at, say, 400 km/h for what was supposed to be a car trip, that's a strong signal one of the input numbers (probably the time) was entered incorrectly rather than a sign of an unusually fast car.

The same kind of sanity check works in reverse for distance and time results. If solving for distance returns a number far larger than the route you had in mind, or solving for time returns a duration that would mean traveling implausibly fast for the mode of transport involved, that's a cue to recheck whether the speed or time value was entered in the unit you intended — a common slip is typing a time in minutes into a field that's being treated as hours, which inflates or shrinks the resulting speed by a factor of 60.

Everyday Situations That Need Speed, Distance, or Time

• Estimating a drive's duration. Knowing a route's distance and a realistic average speed (accounting for highway versus city driving) gives a reasonable travel-time estimate before setting out.
• Working backward from a deadline. If you know the distance to cover and how much time you have left, solving for the required speed tells you whether the trip is realistic at a safe, legal pace or not.
• Checking a reported average speed. News reports, vehicle telemetry, or race results sometimes state an average speed alongside distance and elapsed time — plugging two of those into the calculator is a quick way to confirm the third figure is consistent.
• Shipping and logistics time estimates. Estimating when a delivery or freight shipment will arrive often starts with exactly this formula, applied to a known route distance and an assumed average transport speed.
• Comparing this to running or cycling pace. This tool computes overall average speed for any kind of travel, distinct from a running- or cycling-specific pace figure (typically expressed as minutes per mile or per kilometer) — for that narrower use case, this site's dedicated pace calculator is built specifically around training and race-pace conventions.

Limits of an Average-Speed Calculation

Because the formula only works with totals — total distance and total time — it can't tell you anything about what happened in between. A road trip that included a long rest stop, a flight with a layover, or a run that started fast and finished slow will all report a single average speed that may not resemble the pace at any single moment during the trip. If you need a moment-by-moment speed profile rather than an overall average, this calculator isn't the right tool; it's built for exactly the "distance covered over a span of time" question, not for analyzing variable motion within that span.

Why does the page only accept km/h, km, and hours/minutes for input?

The on-page tool was built around metric units for its input fields, with the common alternative units (mph, miles, meters, seconds) surfaced as read-only conversions in the results rather than as additional input options. If you specifically need to type a value directly in miles or mph rather than converting it to metric first, use the API instead, which accepts all of those units natively as inputs.

Can I enter a time like "1 hour 45 minutes" directly?

Yes — when solving for speed or distance, enter 1 in the hours field and 45 in the minutes field; the page combines them into 1.75 decimal hours automatically before running the calculation, so there's no need to convert the minutes portion to a decimal yourself.

What happens if I try to solve for time but the speed is zero?

A speed of zero means no distance is ever covered, so time can't be meaningfully solved for — the calculator requires a positive speed value before it will compute a result, the same way it requires a positive time value before computing a speed.

Does this calculator account for acceleration or changing speed?

No. It works entirely with average speed over a total distance and total time, which is the correct tool for "how long will this whole trip take" style questions but not for modeling instantaneous speed, acceleration, or a speed that changes partway through the trip.

Why do my mph and m/s figures look like they have a lot of decimal places?

Converting between km/h, mph, and m/s involves multiplying or dividing by conversion factors that aren't round numbers — a kilometer isn't an even fraction of a mile, for instance — so a clean speed like 60 km/h translates to a less tidy 37.28 mph rather than another whole number. This is normal and doesn't indicate any rounding error in the underlying calculation.

Can I use this calculator for a trip with multiple legs at different speeds?

Only if you're working with the trip's overall totals. Add up the full distance covered across every leg and the full time elapsed across every leg, then enter those two combined figures to solve for the overall average speed. The calculator has no way to account for each leg individually — it treats whatever distance and time you provide as a single, uniform trip.

Related Tools

For running or cycling training paces specifically, expressed as minutes per mile or per kilometer rather than an overall average speed, the pace calculator is built around that exact convention. If a distance or speed figure needs converting into a unit this page doesn't directly expose as an input, the length converter handles distance units on their own. And once you know how long a trip will take, the energy converter is useful if you're working out fuel or energy figures for the same journey.