Your result
Click Calculate
Enter your values, then click Calculate result.How this calculator helps
This speed calculator merges the matching speed distance time calculator and converter queries into one worksheet with three real modes. Find speed from distance and elapsed time, distance from a supplied average speed and time, or time from distance and supplied average speed. The working inputs use kilometres, hours and kilometres per hour, while outputs include mph, metres per second and feet per second. It does not find a route or predict traffic. Average speed over an interval is different from an instantaneous speed reading, and the result is only meaningful when distance and time describe the same interval.
How to use it
- 1
Select the unknown quantity: speed, distance or elapsed time. Check which two numerical fields are active for that mode.
- 2
Enter the values in the displayed units and verify the source record or measurement basis.
- 3
Click Calculate result to submit the current inputs.
- 4
Read the labeled outputs with the methodology and checks. Input edits retain the previous result until Calculate is clicked again.
Formula and methodology
Speed km/h = distance km / time h. Distance km = speed km/h × time h. Time h = distance km / speed km/h. mph = km/h ÷ 1.609344; m/s = km/h ÷ 3.6; ft/s = km/h ÷ 1.09728.
The calculator applies the displayed arithmetic to the values entered on this device. It does not silently load a local tax rate, currency conversion or commercial assumption.
Worked calculation example
For 150 km over 2 hours, average speed is 75 km/h, approximately 46.602839 mph, 20.833333 m/s and 68.350831 ft/s. The inverse time mode at 150 km and 75 km/h returns 2 hours.
How to interpret your result
For 150 km over 2 hours, average speed is 75 km/h, approximately 46.602839 mph, 20.833333 m/s and 68.350831 ft/s. The inverse time mode at 150 km and 75 km/h returns 2 hours. Supplied average-speed arithmetic only. No navigation, route length, traffic, peak speed, stopping distance or guaranteed arrival time. Inactive fields are ignored according to selected mode. Compare the main quantity with the separately labeled intermediate values before using it in another worksheet. Retain units, input basis and any selected convention with the result so it can be reproduced.
For different inputs or formulas, use Decimal Time Converter; Running Pace Calculator; Zero To Sixty Calculator.
Related questions this calculator covers
- speed calculator and speed distance time calculator
- how to calculate speed from matching distance and time
- distance calculator from speed and time
- time calculator from speed and distance
- mph calculator and feet per second calculator
- speed distance time converter with explicit units
Scenario comparison
| Scenario | What it shows |
|---|---|
| 150 km in 2 h | average speed 75 km/h. |
| 75 km/h for 2 h | modeled distance 150 km. |
| 150 km at 75 km/h | modeled time 2 h. |
Common mistakes to avoid
- Entering 1:30 or 1.30 as one and a half hours.
- Mixing moving time with total elapsed time.
- Treating average-speed arithmetic as a route ETA.
Multiply the solved speed by elapsed hours and check the original distance. Use the inverse mode with the same quantities to reconcile the result. Confirm the minute output matches your intended decimal hours, and retain the exact units when sharing a conversion.
Authoritative reference. Methodology reference reviewed on 4 October 2026. SolvePilot applies the explicitly displayed arithmetic and its own bounded input handling; the linked documentation does not certify an individual result. Review by Mohammad Qasim is editorial and technical, not a specialist assessment of the entered situation.What can affect the result?
Choose the unknown before entering the active measurements
Find speed uses distance and elapsed hours. Find distance uses elapsed hours and supplied speed. Find time uses distance and supplied speed. The inactive value is not used to overwrite the relationship, even if it remains visible in its field. Changing modes does not automatically submit a new answer: press Calculate after reviewing the active inputs. The primary result label identifies which quantity has actually been solved, avoiding a hidden switch between an observed average and a modeled trip.
Elapsed time and moving time are different denominators
A journey can include stops. Dividing its total distance by total elapsed time gives overall average speed, while dividing by moving time gives another measurement. Both can be valid when labeled, but comparing them directly creates a false discrepancy. This worksheet applies the time you supply and does not remove breaks, traffic or stationary intervals. Record which denominator you used. For a planning scenario, account for additional delays separately rather than presenting pure distance-over-speed time as a guaranteed arrival duration.
Convert clock notation to decimal hours
The hours field accepts a number, not an HH:MM timestamp. One hour and thirty minutes is 1.5 hours, and one hour and fifteen minutes is 1.25 hours. Entering 1.30 means one and three-tenths hours, or seventy-eight minutes. The elapsed-minutes output provides a check. The related decimal-time converter handles clock-to-decimal intent; this page keeps its inputs on a consistent hour basis so all three modes use the same identity.
mph and feet per second are unit conversions
The mph calculator output and feet per second calculator output express the same speed using different units. They do not infer another physical measurement or a different journey. Kilometres per hour divided by 3.6 gives metres per second, while the stated length factors produce the imperial outputs. For a value entered from miles, convert the distance to kilometres before using the working fields. Keep units with copied numbers to prevent a speed from being mistaken for a distance or time.
Average speed does not determine every motion detail
Two journeys can have the same distance and elapsed time while having very different speed traces. The quotient cannot identify peak speed, acceleration, route geometry, fuel use or stopping distance. The time calculator from speed and distance is a constant-average scenario, not navigation. Zero distance is supported when the denominator is valid, while zero time for speed and zero speed for time are rejected. Those mathematical boundaries prevent an impossible quotient from looking like a real travel result.
Privacy and browser processing
Values entered on this page are processed in the current browser session. SolvePilot does not require an account and does not receive the values entered into the calculator. Refreshing or closing the page clears the working values unless the browser itself restores a previous session. Avoid entering identifying or account information because the calculation needs summary values only.
Accuracy and verification
Accuracy depends first on input quality. Confirm definitions, scales, dates and source information before entering a value. Keep an independent record of any result used for planning because this page does not create an official statement or retain a calculation history.
Limits of this estimate
Supplied average-speed arithmetic only. No navigation, route length, traffic, peak speed, stopping distance or guaranteed arrival time. Inactive fields are ignored according to selected mode. Results use the entered assumptions and do not verify their real-world applicability. Calculator inputs are processed locally by the browser interface. Avoid entering identifying records; save only the quantities and context necessary for your own review.
Sources and review information
Frequently asked questions
How to calculate speed?＋
Divide matching distance by elapsed time in consistent units. This page uses kilometres and hours for the working calculation.
Can it calculate distance from speed and time?＋
Yes. Select Find distance and supply km/h plus hours; distance is their product.
Is time calculator distance speed the same page?＋
Yes. Find time solves that matching intent from distance and positive supplied average speed.
Are mph and feet per second supported?＋
Yes, as clearly labeled output conversions from the solved or supplied km/h value.
Does modeled time include traffic?＋
No. Stops, route choice, traffic and arrival timestamps are not inferred from the simple average-speed identity.