🏎️ Speed Calculator

How to Use the Speed Calculator

Enter a distance and a time to get average speed in mph and km/h, plus the equivalent running pace. The defaults are set to a marathon in 4 hours so you can see the classic example immediately; change them to your own drive, ride, or race. Remember this is average speed, which includes every stoplight and water stop.

How Speed Math Works

Speed is distance divided by time, in matching units. Pace flips the fraction: time divided by distance, which is why runners say 9:09 per mile instead of 6.55 mph. The two describe the same motion; the choice is cultural. Drivers get tickets in speed, runners set goals in pace.

Worked example, verified: marathon, 26.2 miles, 4 hours. Speed: 26.2 ÷ 4 = 6.55 mph, which is 10.54 km/h. Pace: 60 ÷ 6.55 = 9.16 minutes per mile, or 9 minutes 9.6 seconds, shown as 9:10/mi. Per kilometer: 240 minutes ÷ 42.195 km = 5.69 min/km, or 5:41/km. Every split of a 4-hour marathon must average that pace, hills and crowds included.

Speed vs Pace: Which to Use

Use speed for machines and pace for bodies. Cars, bikes on a computer, and treadmill displays speak mph or km/h because the machine holds it steady. Runners speak pace because races are fixed distances and the question is always how long each mile takes. Converting between them is one division either way, but training plans, race predictors, and running watches all live in pace, so runners should think in pace natively. One caution: pace from a GPS watch on a hilly or twisty course wobbles, since the watch measures a noisy path. Trust the average over the whole run, not the live number on a hill.

Why Averages Disappoint

Average speed is always lower than the speed you remember traveling, because memory keeps the cruising and forgets the slowing. Every red light, toll booth, water stop, and hill must be repaid with faster-than-average stretches to hold the number. On a road trip, cruising at 72 mph with normal stops typically averages in the low 60s. In a marathon, even pacing means every mile near 9:10; banking time early by running 8:30s usually detonates after mile 20. Plan with the average, train or drive to the average, and let the fast stretches be a bonus rather than the plan.

Tips for Runners Using Pace

Set goal paces from a recent race, not from ambition; a 5K time predicts marathon pace far better than hope does. Do most training slower than goal pace: the conversational easy pace builds the aerobic base that makes the fast pace possible. Learn what your paces feel like without staring at the watch, because race-day adrenaline corrupts the first two miles. And when the calculator gives you 9:09.6, round with mercy. Nobody ever PR\'d because of the decimal.

A Second Worked Example: The Bike Commute

Twelve miles in 45 minutes. Time in hours: 45 divided by 60 is 0.75. Speed: 12 divided by 0.75 is 16 mph. In km/h: 16 times 1.609 is 25.7. Pace per mile: 45 divided by 12 is 3.75 minutes per mile, or 3:45/mi. That is a brisk but ordinary commute pace, and it tells you the e-bike question directly: at 20 mph the same trip takes 36 minutes, saving 9 minutes each way, 18 a day, 90 a week.

Notice what the average hides: stoplights, hills, the slow first mile warming up. The 16 mph average might mean 20 on the flats and 8 on the hill. Averages describe the trip; they do not describe any moment of it. Plan arrival times on the average, but do not judge your fitness by it.

Speed Limits and Stopping Distance

Speed math turns serious in a car because stopping distance grows with the square of speed, not linearly. Double the speed and you need roughly four times the distance to stop. The difference between 30 and 40 mph is not a third more stopping distance; it is nearly double. This is pure physics, kinetic energy is proportional to velocity squared, and it is why small speed increases in neighborhoods have outsized safety consequences.

Reaction distance adds its own linear chunk: at 60 mph you travel 88 feet per second, so a one-second glance at the screen eats nearly 90 feet before braking even starts. Total stopping distance is reaction plus braking, and both punish speed. The speed limit signs are not suggestions about flow; they are statements about physics.

Common Speed-Math Mistakes

First: confusing average speed with cruising speed. A 60 mph average on a road trip means hours at 75 plus stops, not a steady 60. Second: mixing units mid-calculation. Miles with km/h, or minutes with hours, silently corrupt the answer. Convert everything to one system first. Third: pace-speed confusion. A 9:00/mile pace is 6.67 mph, but runners who "run 9-minute miles" sometimes hear "9 mph," which would be a 6:40 pace and a very different runner.

Fourth: forgetting that average speed includes stops. A drive with a 30-minute lunch stop has a lower average than the highway speed suggests, which is why trip estimates based on the speedometer always run optimistic. Fifth: rounding the time. Forty-five minutes is 0.75 hours, not 0.45. Decimal hours strike again; the minutes-to-decimal conversion is the most error-prone step in the whole calculation.

Worked Example: The Marathon Finish Time

A runner holds 9:09 per mile for a marathon (26.2 miles). Total time: 26.2 × 9.15 minutes = 239.7 minutes, or 3:59:42. In speed terms, 9:09 pace is 6.55 mph (60 / 9.15). The calculator runs it either direction: enter pace, get speed and finish time; enter a goal time, get the required pace per mile.

The even-split assumption is where predictions break. Almost no one runs 26 identical miles; the second half is usually 2 to 5 percent slower. A realistic plan: target 9:00 pace through mile 18 (2:42:00), then allow 9:20s home (8.2 × 9.33 = 76.5 min), totaling 3:58:30. Banking time early works only if the early pace feels easy; banking at effort always backfires.

Average Speed Lies: The Wind and Hills Problem

Average speed hides the distribution that produced it. A cyclist averaging 18 mph might have ridden 22 with a tailwind and 14 into a headwind; the average says nothing about the effort. Hills distort more: climbing at 8 mph and descending at 30 does not average to 19. Time spent slow weighs more than time spent fast, so the true average sits below the midpoint.

This is why "average pace" frustrates runners on hilly courses. A 9:00 average on a flat course and a 9:00 average on a hilly course are different fitness achievements, and comparing them directly misleads. For training, track normalized effort (heart rate or power) alongside speed; for racing, compare times only on similar courses. The single number is a summary, not the story.

MPH vs. Pace vs. Knots: Unit Comparison

Miles per hour suits vehicles and cycling: 20 mph means 3 minutes per mile, intuitive at speed. Minutes per mile suits runners: pace maps directly to effort and race planning, where nobody thinks "I run at 6.5 mph." Knots (nautical miles per hour) suit boats and aircraft because a nautical mile equals one minute of latitude, making chart math trivial.

Conversions: 60 / mph = minutes per mile (20 mph = 3:00/mi); mph × 0.869 = knots; knots × 1.151 = mph. Runners switching to cycling often struggle because 15 mph on a bike feels easy while 15 mph running is world-class; the units are the same but the sports scale differently. Use each sport's native unit and convert only when comparing across them.

Pro Tips for Pacing Race Day

Start 10 to 15 seconds per mile slower than goal pace for the first 2 miles. The adrenaline start is the top destroyer of race plans, and the time "lost" going out controlled is recovered twice over in a strong finish. Your watch is more trustworthy than the crowd's energy.

Learn your effort gears in training, not on race day. Know what goal pace feels like in your breathing and legs, because GPS watches lag on tree-covered courses and in downtown canyons. The runners who pace best are the ones who could do it by feel if the watch died.