Speed Distance Time Calculator

Solve for speed, distance, or time — any two inputs gives you the third

The speed distance time calculator solves all three variables of the fundamental physics relationship using just two inputs. Enter any two values — speed and distance, speed and time, or distance and time — and it calculates the third automatically. Select your units from the dropdowns: km, miles, metres, or feet for distance; seconds, minutes, or hours for time; km/h, mph, or m/s for speed. Everything runs in your browser — no upload, no server, no sign-up required.

This covers the three most common day-to-day questions: how fast were you going (speed from distance and time), how far will you travel (distance from speed and time), and how long will the journey take (time from speed and distance). The core formula is simple — Speed = Distance ÷ Time — but juggling units and converting hours to minutes is where mistakes sneak in. The calculator handles unit conversion automatically, so you just enter what you know and get what you need.

The physics behind the formula

Speed, distance, and time are related by the equation v = d / t, where v is velocity, d is distance, and t is time. The relationship is linear: double the speed and you halve the travel time for a fixed distance; double the distance at the same speed and you double the time. That linearity is why the formula applies so broadly, from a quick mental check of driving time to formal engineering calculations.

The speed-distance-time triangle is a memory aid that's been in secondary school physics for decades. Draw a triangle with Distance at the top, Speed at the bottom-left, and Time at the bottom-right. Cover the variable you want: cover Distance and you see Speed × Time; cover Speed and you see Distance ÷ Time; cover Time and you see Distance ÷ Speed. This calculator does exactly what the triangle represents — but with unit conversion built in, so you don't need to be in consistent units before entering the values.

Practical uses — driving, running, cycling, physics homework

For driving and road trips: enter your trip distance and expected average speed to get estimated travel time. Most navigation apps give you a route distance — pair that with a realistic average speed to cross-check an app's ETA or plan fuel stops. For running: enter race distance and finish time to get average speed plus the equivalent pace per km/mile — a 40-minute 5K is 7.5 km/h or an 8:00 min/km pace. For cycling: enter ride distance and time to track average speed, or enter a target speed to predict how long a given route will take.

Physics students use this tool to check motion problem answers without arithmetic errors affecting the concept being taught. Pilots and boaters use similar calculations for range and time-on-fuel estimates. The formula itself is exact; the accuracy of the result depends entirely on how precisely you measure the inputs.

How this compares to RapidTables, Omni Calculator, and Calculator.net

RapidTables has a speed calculator but requires selecting which variable to solve for before entering values, and handles fewer unit combinations. Omni Calculator's speed tool is thorough but shows many intermediate steps that make simple queries feel slow. Calculator.net has good unit coverage but splits the three solve modes into separate tabs, so you have to navigate between them. Google answers basic speed questions in search results but doesn't handle unit mixing or solve all three variable directions.

This calculator puts all three solve modes in one interface: fill in any two of the three fields and it detects which is blank and solves for it. Unit selects are per-field, so you can mix units freely — enter distance in miles, time in minutes, get speed in km/h. The result includes the equivalent running/cycling pace in min/km and min/mile for speed outputs, which most competing tools skip. And it runs entirely offline in your browser once loaded, so it works without an internet connection.

Getting accurate results — what 'average speed' really means

The formula uses average speed, not instantaneous speed. A 200 km drive 'at 100 km/h' assumes you maintained exactly 100 km/h the entire time — but in reality, stops, traffic, and acceleration mean your actual average is always lower. Build in 10–20% extra time for real driving estimates, especially in urban areas or on routes with frequent stops.

For running and cycling, heart rate-based pacing means your speed varies continuously throughout a session — the calculator gives your average, which is the most useful figure for race planning and performance tracking. For scientific or academic use, measure your distance and time carefully before calculating. The formula is exact; the only source of error is the precision of your inputs.

Average speed, instantaneous speed, and the kinematic equations

There is an important distinction between average speed and instantaneous speed. Average speed is what this calculator computes: total distance divided by total time. Instantaneous speed is what a speedometer measures — mathematically, it is the derivative of position with respect to time, the speed at a single infinitesimally small moment. A driver who goes 60 mph for 30 minutes and then 80 mph for 30 minutes has an average speed of 70 mph, but their instantaneous speed fluctuated between those values the whole time. The distinction matters in physics, engineering, and any context where peak loads or peak velocities govern safety margins rather than averages.

Speed and velocity are often used interchangeably in everyday language but are different physical quantities. Speed is a scalar — it has magnitude only. Velocity is a vector — it has both magnitude and direction. A car travelling around a circular track at a constant 60 km/h has constant speed but continuously changing velocity, because the direction of travel changes at every instant. This is why the car still requires a centripetal force (friction from the tyres) even though its speed is not changing.

When acceleration is involved, the full picture is captured by the kinematic equations derived from constant-acceleration motion. The three key equations are: v = u + at (final velocity equals initial velocity plus acceleration multiplied by time); s = ut + ½at² (displacement equals initial velocity times time plus half of acceleration times time squared); and v² = u² + 2as (the velocity-squared equation, useful when time is unknown). Here, u is initial velocity, v is final velocity, a is acceleration in m/s², and s is displacement in metres. The reference value for acceleration is Earth's gravitational acceleration, g ≈ 9.8 m/s² — an object in free fall gains roughly 9.8 metres per second of speed every second it falls. These equations are the foundation of classical mechanics and underpin everything from ballistics to spacecraft trajectory planning.

Speed records across domains — from sprinting to supersonic

The land speed record is held by Thrust SSC, driven by Andy Green in the Black Rock Desert, Nevada, on October 15, 1997 — 1,228 km/h (763 mph), making it the first land vehicle to break the sound barrier. For production cars, the Bugatti Chiron Super Sport 300+ achieved 304.7 mph (490.5 km/h) in 2019, the first production car to exceed 300 mph; the Koenigsegg Jesko Absolut has a calculated theoretical top speed of 330 mph (531 km/h), though that figure has not been officially verified on a closed course. These numbers illustrate just how dramatic the gap is between road-legal vehicles and purpose-built record cars.

In human-powered sport, Usain Bolt's 100m world record of 9.58 seconds (set in Berlin in 2009) works out to an average speed of 10.44 m/s (37.6 km/h) — but that's the average across the full run. Analysis of his split times shows he reached a peak instantaneous speed of approximately 12.4 m/s (44.7 km/h) at the 65–70 metre mark, after the acceleration phase. In the water, Michael Phelps reached peak speeds of approximately 2.3 m/s — which feels slow against a sprinter until you account for water's resistance being roughly 800 times greater than air's at the same speed. The cycling speed record belongs to Denise Mueller-Korenek, who reached 280.44 km/h in 2018 on the Bonneville Salt Flats, paced by a dragster — a speed achievable only because of aerodynamic drafting, not raw human power output.

These records are useful reference points when using any speed calculator: they set the physical plausible range for a given context. A result of 500 km/h for a car trip should trigger a sanity check; a marathon running pace of 12 km/h for an elite runner is entirely reasonable. Knowing what's physically possible in each domain makes it easy to spot a misplaced decimal or a unit mismatch before acting on a calculation.

Speed units and conversions — mph, km/h, knots, Mach, and beyond

The world uses several competing speed units depending on context. Miles per hour (mph) is standard in the United States and the United Kingdom for road speeds. Kilometres per hour (km/h) is used in most other countries, and in the SI-adjacent world of science and engineering. The conversion is exact: 1 mph = 1.60934 km/h, so a 60 mph motorway limit is 96.6 km/h, and a 130 km/h autobahn limit is 80.8 mph. Knots — nautical miles per hour — are used in maritime navigation and aviation because 1 nautical mile equals exactly 1 arcminute of latitude, making position and distance calculations on a globe far simpler. One knot equals 1.852 km/h or 1.151 mph. A commercial jet cruising at 480 knots is travelling at 889 km/h.

The Mach number measures speed as a ratio to the local speed of sound. Mach 1 ≈ 343 m/s at 20°C at sea level — but the speed of sound decreases with altitude and temperature. At 35,000 feet (the cruise altitude of most airliners), Mach 1 is approximately 295 m/s (1,062 km/h), which is why a jet at Mach 0.85 is actually slower in absolute terms at altitude than Mach 0.85 at sea level. Supersonic aircraft are defined as exceeding Mach 1; hypersonic begins at Mach 5. In ballistics, feet per second (fps) remains the dominant unit — a .308 rifle bullet leaves the muzzle at roughly 2,780 fps (850 m/s), comfortably supersonic.

At the extreme end, the speed of light in a vacuum is c = 299,792,458 m/s exactly — this is not a measured value but a defined constant, fixed by international agreement since 1983, which then defines the metre in terms of the second. Nothing with mass can reach or exceed this speed. It takes light approximately 1.3 seconds to travel from the Earth to the Moon, and about 8 minutes 20 seconds to travel from the Sun to Earth. When astronomers say a galaxy is 13 billion light-years away, they mean light has been travelling for 13 billion years to reach us — a distance of roughly 1.23 × 10²⁶ metres.

Relative speed, the meeting problem, and GPS accuracy

Relative speed describes how fast two objects approach or separate from each other's frame of reference. When two objects move toward each other, their relative speed is the sum of their individual speeds: two cars approaching head-on at 60 mph each are closing the gap at 120 mph. When they move in the same direction, the relative speed is the difference: a car at 70 mph overtaking one at 50 mph closes the gap at only 20 mph. This is why overtaking on a motorway takes far longer than it feels — at a 20 mph closing rate, passing a 15-metre truck takes over 2.5 seconds of maintained speed difference just to clear its length, before accounting for the safe gap you need at the end. The classic "two trains approaching each other" problem is solved by adding their speeds to find the closing rate, then dividing the separation distance by that rate.

GPS speed measurement works quite differently from an odometer. GPS receivers calculate speed by measuring the Doppler shift of signals from multiple satellites — as you move toward a satellite, its signal frequency appears slightly higher; as you move away, lower. Differencing the phase shift across satellite signals gives a velocity vector accurate to within approximately 0.1 km/h under good sky conditions. Car odometer-based speedometers, by contrast, count wheel rotations and multiply by circumference — but tyre wear, inflation, and load change the effective rolling radius, causing typical speedometer readings to run 3–5% high (deliberately, in most jurisdictions, so manufacturers can guarantee no speed is understated). The GPS speed you see on a cycling or running app is therefore often more accurate than your car's dashboard.

At speeds approaching a significant fraction of the speed of light, time dilation from special relativity becomes measurable. A clock moving at velocity v runs slow by a factor of √(1 − v²/c²) relative to a stationary observer. At 10% of c, this factor is about 0.5% — tiny, but not zero. GPS satellites orbit at roughly 14,000 km/h and also sit higher in Earth's gravitational well than ground-based receivers. Together, special-relativistic time dilation (satellites' clocks run slow due to speed) and general-relativistic time dilation (clocks run fast farther from a gravitational mass) produce a net effect of approximately 38 microseconds per day of clock drift. Without correction, this would translate to a positional error of roughly 10 kilometres per day. Every GPS receiver applies a relativistic correction continuously — a practical, everyday application of Einstein's theories that most users never think about.