Solve for speed, distance, or time when you know the other two — supports km/h, mph, m/s, and knots, with hours/minutes/seconds time entry and live unit conversion.
| Example | Speed | Context |
|---|---|---|
| Highway driving | 110 km/h (68 mph) | Typical highway/motorway cruising speed. |
| City driving | 50 km/h (31 mph) | Typical urban speed limit. |
| Walking pace | 5 km/h (3.1 mph) | Average adult walking speed. |
| Running (jogging) | 10 km/h (6.2 mph) | A comfortable jogging pace. |
| Commercial airliner | 900 km/h (486 knots) | Typical cruising speed of a passenger jet. |
| Cargo ship | 37 km/h (20 knots) | Typical cruising speed of a container ship. |
| Usain Bolt's 100m sprint | 37.6 km/h (10.4 m/s) | Peak speed during the 2009 world record. |
| Sound (at sea level) | 1,235 km/h (343 m/s) | The speed of sound in dry air at 20°C. |
Speed = Distance ÷ Time is one of the most fundamental relationships in all of physics, tracing back to some of humanity's earliest attempts to formally measure motion — ancient astronomers used essentially this same relationship to calculate the speed of celestial bodies across the sky centuries before physics existed as a formal discipline. Every more advanced concept involving motion (velocity, acceleration, momentum) ultimately builds on this same core relationship. Its enduring usefulness comes from being both dead simple to state and universally applicable — the same three-variable relationship works identically whether you're calculating a car's road trip time, a satellite's orbital speed, or the time light takes to reach Earth from a distant star.
The mathematical relationship between speed, distance, and time is trivially simple — the entire practical difficulty in real-world calculations comes from unit consistency, not the arithmetic itself. A speed of '60' means something completely different depending on whether it's 60 km/h, 60 mph, 60 m/s, or 60 knots — and mixing them (say, dividing a distance in miles by a speed in km/h) without an explicit conversion step produces a confidently wrong answer rather than an obvious error. This tool sidesteps the problem entirely by converting every input to a single consistent base unit (meters and seconds) internally before doing any math, then converting the result back to your chosen display unit — the same technique used throughout scientific and engineering software to avoid unit-mismatch bugs.
Unlike most units of length, which are arbitrary human-defined standards, the nautical mile has a genuinely elegant geographic definition: it's the distance covered by one minute of arc along any great circle of the Earth (essentially, one sixtieth of one degree of latitude), which works out to exactly 1,852 meters by international agreement. This makes nautical miles unusually convenient for navigation specifically, since a ship or aircraft's position (given in latitude and longitude) and its distance traveled can be related directly through this same unit, without needing an extra conversion step — a genuinely practical reason knots have remained the standard unit in maritime and aviation navigation long after most of the world moved to purely metric units elsewhere.
While road trip and commute time estimation is the most common everyday use, the same speed-distance-time relationship shows up across a surprising range of practical contexts: runners and cyclists calculating race pace and finish times, pilots and sailors doing dead-reckoning navigation calculations, physics and engineering students working through kinematics problems, project managers estimating shipping or delivery times, and even everyday scenarios like estimating how long a video call or livestream will take to buffer at a given download speed (conceptually the same relationship, just with data instead of physical distance). The underlying math never changes — only the units and context do.
Speed Distance Time Calculator solves the most fundamental motion equation. These related calculators cover other common everyday and travel math.