Speed equals distance divided by time. That's the whole core of it: if you ran 1,500 meters in 300 seconds, your average speed was 5 meters per second. The catch is that this simple division fails in three predictable places — mismatched units, confusing average speed with instantaneous speed, and forgetting that "per hour" answers need a second conversion. Get those right and every word problem, fitness log, and driving estimate from here on behaves.

The formula works in any measurement system and any time unit, provided the two units match before you divide. What changes between contexts is what "speed" means — a car's cruise-control reading, a sprinter's top velocity, and a marathoner's overall pace are three different measurements that happen to share a formula. This guide walks through the arithmetic first, then the conversions and the failure cases that trip people up in practice.

Why Distance Divided by Time Gives You Speed

Speed is a rate: how much position change happens per unit of time. Dividing distance by time is the arithmetic version of that definition. Nothing more mystical is happening, and no equation needs memorizing beyond s = d/t.

Take a concrete case. A cyclist covers 36 kilometers in 90 minutes. Convert 90 minutes to 1.5 hours, then divide: 36 km ÷ 1.5 h = 24 km/h. If you skip the conversion and divide 36 by 90, you get 0.4 — numerically correct as kilometers per minute, but useless if the question asked for km/h.

The formula's three arrangements cover most real questions. Speed is d ÷ t. Distance is s × t. Time is d ÷ s. When someone asks "how long will it take to drive 40 kilometers at 80 km/h," you're using the third arrangement: 40 ÷ 80 = 0.5 hours, or 30 minutes.

One boundary worth stating up front: this formula gives average speed over the whole interval. If a hill slowed the cyclist and a descent sped her up, 24 km/h is the single number that would have produced the same trip time on flat ground. The word "average" is doing real work there.

Setting Up the Calculation Without Mixing Units

The single most common error in speed problems is dividing a distance in one unit by a time in another and reporting an answer that means nothing. Fix the units before you touch a calculator.

Quantity Metric example Imperial example Convert to before dividing
Distance 5,000 meters 3.1 miles One distance unit throughout
Time 25 minutes 1,500 seconds Hours for "per hour" answers
Speed result 200 m/min 7.44 mph Label the result with both units

Run the imperial example through: 3.1 miles in 1,500 seconds. Convert 1,500 seconds to 1,500 ÷ 3,600 = 0.4167 hours. Divide 3.1 by 0.4167 to get 7.44 mph. Rounding the time conversion to 0.42 hours would shift the answer to 7.38 mph, so carry at least four decimal places in intermediate steps.

Memorize the conversion anchors rather than looking them up each time: 1 hour = 60 minutes = 3,600 seconds; 1 kilometer = 1,000 meters = 0.621371 miles; 1 mile = 1,609.344 meters. Those three facts cover almost every school problem and most adult estimates.

If a problem hands you mixed units deliberately — "a train travels 45 kilometers in 35 minutes, what is its speed in km/h?" — the conversion is the test. 35 minutes is 35 ÷ 60 = 0.5833 hours, and 45 ÷ 0.5833 = 77.14 km/h. The arithmetic is trivial; the unit discipline is the actual skill.

Worked Example: Converting Meters per Second to Kilometers per Hour

Metric speed problems frequently ask for km/h after giving you meters and seconds. The conversion factor is exactly 3.6, and it's worth understanding where it comes from so you never need to recall it blindly.

Suppose a runner covers 400 meters in 50 seconds. Divide: 400 ÷ 50 = 8 m/s. To convert m/s to km/h, multiply by 3.6: 8 × 3.6 = 28.8 km/h. The factor arises because one hour holds 3,600 seconds and one kilometer holds 1,000 meters, so 3,600 ÷ 1,000 = 3.6.

The reverse direction divides by 3.6. A car cruising at 72 km/h is moving at 72 ÷ 3.6 = 20 m/s. That mental shortcut — divide km/h by 3.6 for m/s — is genuinely useful for physics estimates and safe-driving intuition.

Watch the rounding trap. An athlete at 8.333 m/s converts to exactly 30 km/h only if you keep the fraction; rounding to 8.3 first gives 29.88 km/h. When a problem's answer looks like it should be a clean number but isn't, the culprit is usually premature rounding.

Track-and-field contexts add one more wrinkle: race distances are metric while broadcast speeds are often shown in km/h or mph. A 100-meter dash in 10.5 seconds is 9.52 m/s, which converts to 34.3 km/h — the kind of figure a commentator quotes. Same formula, one extra multiplication.

Finding Time and Distance Instead

The formula's other two forms answer questions that come up more often than speed itself once you're out of the classroom. Both are one-step rearrangements and both obey the same unit rule.

Time is distance divided by speed. Driving 240 kilometers at an average of 80 km/h takes 240 ÷ 80 = 3 hours. If the speed is given in mph and the distance in miles, no conversion is needed; if they're mixed, convert first. A 150-mile trip at 60 mph takes 2.5 hours, which is 2 hours 30 minutes — decimal hours convert to clock time by multiplying the fraction by 60.

Distance is speed times time. A cyclist averaging 18 km/h for 2.25 hours covers 18 × 2.25 = 40.5 kilometers. For runs and rides tracked in minutes, convert first: 18 km/h for 45 minutes is 18 × 0.75 = 13.5 kilometers.

Aviation and marine contexts use knots, which is one nautical mile per hour and equals roughly 1.852 km/h. A vessel at 12 knots for 90 minutes travels 12 × 1.5 = 18 nautical miles. Mixing nautical miles with statute miles in the same calculation is a classic navigation error, and it's the exact mistake route-planning software is built to prevent.

Each arrangement deserves a sanity check before you trust it. If a division gives you a time longer than the distance in kilometers with a fast speed, you inverted the formula. Re-check which quantity you're solving for.

Average Speed vs Instantaneous Speed: When the Formula Breaks

Here's the failure case almost no beginner guide covers. Average speed over a whole trip is not the same as the average of two speeds, and the difference is large enough to matter in every real journey.

A driver goes 60 km/h for 30 minutes, then 120 km/h for another 30 minutes. The naive average is (60 + 120) ÷ 2 = 90 km/h. The true average speed is total distance over total time: 30 km + 60 km = 90 km in 1 hour, so 90 km/h. That case happens to match, because the two legs took equal time.

Now change the setup: the driver goes 60 km/h for the first 60 km, then 120 km/h for the next 60 km. Total distance 120 km, total time 1 hour plus 30 minutes = 1.5 hours. Average speed is 120 ÷ 1.5 = 80 km/h — ten below the naive 90. Whenever the legs take equal distance instead of equal time, the simple average overstates the true figure. The slower leg always dominates because you spend more time in it.

Instantaneous speed is different again. A speedometer reading at one moment comes from dividing a very small distance by a very small time interval. Mathematically it's the limit as that interval shrinks toward zero, called a derivative in calculus. For a car with cruise control set at 100 km/h, the instantaneous speed is roughly constant; for a sprinter exploding out of the blocks, it climbs from zero to a peak and back down.

Practical upshot: use d/t when you want the overall trip figure, and trust a speedometer or GPS for the moment-to-moment reading. The formula alone can't distinguish them without being told which interval you're measuring.

Doing It in a Spreadsheet: Cells, Formulas, and One Formatting Trap

If you're analyzing a log of runs, drives, or shipments, a spreadsheet does the arithmetic reliably — as long as you respect how it stores time.

Column Header Example entry Notes
A Distance (km) 5.00 Plain decimal number
B Time (h:mm:ss) 0:25:00 Entered as a time value, not text
C Speed (km/h) =A2/(B2*24) The ×24 converts Excel time to decimal hours

The multiplication by 24 is the whole trick. Google Sheets and Microsoft Excel both store 0:25:00 as the fraction 0.017361 of a day, so dividing distance by the raw cell gives an answer 24 times too small. Multiply the time cell by 24 to get 0.4167 hours, and 5 ÷ 0.4167 returns 12 km/h.

Confirm your time cells are real time values before trusting results. If you type "25 min" as text, the formula throws a #VALUE! error. Re-enter it as 0:25:00 using the colon format, which both major platforms parse automatically.

For minutes-and-seconds pace work — common in running — convert the result once more: 12 km/h equals 5 minutes per kilometer. Divide 60 by the km/h figure for pace in minutes per kilometer, or 1,600 by the m/s figure for pace per mile in the original units.

Two Real Numbers From the Field, and What They Reveal

Published records give the formula something to bite on, and they show how the same arithmetic scales from a school problem to elite performance.

According to World Athletics, the men's 100-meter world record stands at 9.58 seconds, set by Usain Bolt in Berlin in 2009. Divide 100 by 9.58 and you get 10.44 m/s, which converts to 37.58 km/h. Bolt's actual top speed inside that race was higher — measured at roughly 12.2 m/s, or about 44 km/h, over a short segment — because the 10.44 figure is the average across a race that includes a standing start. The record time isn't the speed; the formula with the full race interval gives you an average, and the gap between 37.58 and 44 km/h is the cost of acceleration.

The marathon provides the second number. The men's marathon world record is 2:00:35, set by Kelvin Kiptum in Chicago in 2023, which works out to 42.195 km ÷ 2.00972 hours = 20.99 km/h. That's roughly 2 minutes 51 seconds per kilometer, sustained for two hours. The 100-meter average of 37.58 km/h and the marathon average of 20.99 km/h aren't contradicting each other — they're two averages over intervals of very different lengths, and the drop reflects what an athlete can hold as duration grows.

This is the practical lesson the plain formula can't teach: the interval you choose defines the number. A stopwatch, a GPS watch, and a race official's timing mat may all produce slightly different intervals because they start and stop at different moments, which shifts the computed speed by small amounts. For most purposes that's fine; for records, the interval is specified in the rules.

Common Mistakes That Produce Wrong Answers

Five errors account for nearly all incorrect speed calculations. Recognizing them by symptom speeds up fixing them.

Mismatched units top the list — the 36 km in 90 minutes divided raw into 0.4 problem above. The symptom is an answer absurdly small or large for the context, and the fix is converting the time to hours first.

Inverting the formula comes second. Dividing speed by distance to find time, or time by speed to find distance, produces a number that passes a careless glance. Ask whether the answer's unit matches what was requested; a "time" answer with a distance unit is your flag.

Premature rounding causes errors in the third decimal that occasionally fail grade thresholds. Keep four decimal places until the final step. A student rounding 50 ÷ 3 to 16.67 m/s instead of 16.666… loses accuracy worth two-tenths of a km/h.

Averaging speeds instead of totals is the fourth trap, covered in the failure case above. If a problem gives speeds and asks for the trip average, compute total distance over total time rather than averaging the given figures.

Treating decimal hours as clock time is the fifth. A result of 1.75 hours is 1 hour 45 minutes, not 1 hour 75 minutes. Multiply the fractional part by 60 to get minutes, then the fractional part of that by 60 for seconds. The 1:45 conversion is a one-second fix that still costs people marks.

How the Formula Appears in Real Instruments and Jobs

Speed calculation isn't just pencil work; it's embedded in devices and professions where the same division runs continuously in hardware.

A car's speedometer doesn't measure speed at all. It counts wheel rotations over a known circumference to derive distance, divides by elapsed time, and displays the result. That's why changing tire size can make a speedometer read a few percent off — the wheel circumference assumption in the firmware no longer matches the physical wheel. A GPS unit bypasses this by computing position fixes and dividing the change in position by the time between fixes, which is why GPS speed can lag a speedometer by a fraction of a second during hard braking.

Pilots use the identical relationship with aviation-specific units. A nautical mile is one minute of latitude, and speed in knots is nautical miles per hour. Flying 90 nautical miles at 150 knots takes 90 ÷ 150 = 0.6 hours, or 36 minutes. Weather and air-traffic communication use knots almost universally, so pilots convert to and from statute mph at the boundaries.

Sports timing and logistics use it visibly. Race splits, delivery ETAs, and cycling power meters all lean on distance ÷ time, sometimes with corrections for elevation or wind. A delivery route planner estimating 55 minutes for 48 kilometers assumes an average of 52.4 km/h, and if traffic drops the real average to 40 km/h, the same formula returns 1.2 hours — the ETA is only as good as the assumed speed.

FAQ

How do I calculate speed from distance and time in mph?

Divide the distance in miles by the time in hours. A 26.2-mile marathon in 3 hours gives 26.2 ÷ 3 = 8.73 mph. If your time is in minutes, divide by 60 first — a 5-mile run in 45 minutes is 45 ÷ 60 = 0.75 hours, then 5 ÷ 0.75 = 6.67 mph. Keep the units stated in the answer to prevent the numbers mixing silently.

What is the difference between speed and velocity?

Velocity carries direction as well as magnitude. A car returning to its starting point after 100 kilometers has an average speed of 100 km divided by elapsed time but a velocity of zero, because displacement is zero. Speed is a scalar — a plain number with a unit — while velocity is a vector. The d/t formula gives speed unless you're tracking displacement in a specific direction.

Why does my average speed formula not match my speedometer?

Because the two are measuring different intervals. Your speedometer reads instantaneous speed; averaging readings across a trip can't reproduce total distance divided by total time if you accelerated, braked, or spent unequal time at different speeds. The correct trip figure is total distance over total time, which the speedometer's samples only approximate. GPS trip computers compute the same way the formula does.

Can speed ever be negative?

Only when the quantity is velocity, not speed. Velocity on a chosen axis is negative when motion goes opposite to the positive direction — a car heading west while east is positive has negative velocity. Speed as defined by distance ÷ time is always zero or positive, because distance traveled is never negative even when you reverse direction.

How do I convert m/s to km/h without remembering 3.6?

Multiply by 3,600 and divide by 1,000, which is the same as multiplying by 3.6. The origin is the unit chain: one hour is 3,600 seconds and one kilometer is 1,000 meters, so the ratio fixes the factor. To convert km/h to m/s, reverse it — divide by 3.6. A quick mental check: 10 m/s should land near 36 km/h, since that's roughly sprinting speed.

What's the fastest way to estimate travel time without a calculator?

Use the ratio shortcut: time in hours ≈ distance in miles ÷ average mph, rounded. A 200-mile drive at 50 mph takes about 4 hours. For metric, a 300-kilometer trip at 100 km/h takes 3 hours. Add roughly 20 percent for real-road conditions including stops, which is close to how navigation apps weight their estimates. The rounding gets you within minutes, not the exact elapsed-vehicle time.

Does the formula work for a round trip?

It does, but use total distance and total time, not one-way figures. A 60-kilometer round trip completed in 45 minutes gives 60 ÷ 0.75 = 80 km/h average, which is correct even though it passed the same point twice. If a problem asks only about the outbound leg, calculate that leg separately and don't combine it with the return. That distinction matters in delivery logs and commuting studies alike.

How accurate should my final answer be rounded?

Match the number of significant figures in the least precise input. If the distance is "5 miles" (one significant figure), reporting 6.6667 mph implies false precision; 7 mph is honest. Exam answers usually specify rounding to one or two decimals, so follow the instruction. In spreadsheets, format to two decimals for display and keep full precision in the underlying cell to prevent compounding error.