Travel Time Calculator

Distance, speed and the one number every plan hinges on

Every travel time question starts with one division: distance divided by average speed. The word that matters is average. A 560 mile highway leg posted at 70 mph is not a 560 ÷ 70 trip, because ramps, towns, traffic and weather pull the average down from the limit. Pick an average speed you have seen on that route, not the number on the sign, and the rest of the plan holds together.

The same formula runs backward. If a leg took 8 hours 2 minutes over 442 miles, the average speed was 55 mph, and that measured number is a far better input for the next trip than any guess. Keep one figure per route type: interstate, two lane, and city, because a blended average hides exactly the variation that ruins arrival estimates.

Adding stops without losing count of the clock

Stops are where door to door time drifts away from driving time. Fuel, food, restroom breaks and the walk from the parking spot all count, and each one adds its full length to the elapsed total even though the odometer does not move. The honest way to plan is to name the stops, give each a length, and add them to the driving figure.

Two habits keep this table honest. First, count the stop from the moment the wheels stop turning, not from the moment you decide to stop. Second, on any drive past about three hours, assume at least one stop you did not plan, because bathroom and fuel needs do not consult the itinerary. A plan with zero slack is a plan that arrives late.

Multi-leg trips: add the times, never the speeds

A trip with distinct legs must be summed leg by leg, because averaging the speeds of the legs produces a wrong answer whenever the legs differ. The workable rule is to convert each leg to hours first and add hours, not to average the mph figures.

When the legs differ in speed the trap shows itself. Drive 300 miles at 60 mph and then 300 miles at 30 mph and the total is 600 miles in 15 hours, which is 40 mph for the trip, not the 45 mph a naive average of the two speeds suggests. The weighted mean, total distance over total time, is the only average that survives contact with arithmetic, and it is what the calculator computes.

Crossing time zones: which clock does the arrival belong to

Time zones do not change how long a trip takes, but they change what the arrival clock says, and that is the number people write down. The clean method is to carry the whole plan on the origin clock, then shift the arrival once, by the offset between destination and origin. Moving east adds hours, moving west subtracts them, and daylight saving boundaries can add or remove one more hour on particular dates.

The example trip from Portland to Twin Falls crosses from Pacific into Mountain time, so a 07:00 departure that lands 10 hours 20 minutes later arrives at 17:20 on the Pacific clock and 18:20 on the local one. Quoting 17:20 to someone standing in Twin Falls is a promise that is an hour late, which is why the tool reports the arrival on both clocks.

Working backward from a fixed arrival time

Half of real trip planning starts from the other end: a meeting at 18:00, a hotel check in, a ferry that leaves once a day. The arithmetic reverses cleanly. Take the required arrival, shift it onto the origin clock, subtract the full door to door elapsed time, and the result is the latest departure. Anything that lengthens the trip, traffic, a longer meal, a second fuel stop, moves that departure earlier by exactly the same amount.

The last row is the one worth staring at. An early morning deadline on a long trip pushes the departure into the previous evening, and the correct response is to plan an overnight stop, not a night of driving. For commercial drivers that decision is not a preference at all, because the hour rules in the next section cap how the night can be used.

Commercial driving: 11 hours, the 14 hour window and the 30 minute break

Driving a commercial motor vehicle in interstate commerce adds federal hour limits on top of the arithmetic. Under the FMCSA summary of hours of service regulations, which consolidates 49 CFR 395.3 as amended by the final rule published June 1, 2020 and effective September 29, 2020, a property carrying driver may drive at most 11 hours after 10 consecutive hours off duty, may not drive beyond the 14th consecutive hour after coming on duty, and must take a 30 minute break when 8 cumulative hours of driving pass without one. The agency's driver guide, updated in April 2022, walks the same rules through worked examples.

The 750 mile row from the first table shows why distance alone is not a plan: 11 hours 32 minutes at 65 mph exceeds the 11 hour driving limit by 32 minutes, so a solo driver cannot complete it in one shift no matter how early the day starts. The trip needs a second duty period after 10 hours off, a team split, or a shorter route, and the 14 hour window caps the whole shift even before the driving cap bites.

What real travel looks like: commute and safety data

Public data puts useful bounds on the inputs. The Census Bureau's American Community Survey commuting summary reports a mean one way travel time to work of 27.2 minutes in 2024, up from 26.8 minutes in 2023, and that figure blends every mode and every kind of traffic. The Bureau of Labor Statistics' American Time Use Survey 2024 results, released in June 2025, put full time workers at an average of 8.4 hours of work on weekdays they worked, which caps how much driving most people can stack around a job.

The divisions behind the first table are simple enough to check in your head: 560 / 60 = 9.33 hours of driving, and 500 / 55 = 9.09 hours, which is the 9 hours 5 minutes quoted above. The mixed speed case is the one that needs care, since 600 / 15 = 40 mph is the true trip average for the 60 mph and 30 mph legs.

The NHTSA figures, from the agency's speeding countermeasures material, are the reason the average speed input deserves respect rather than optimism: 11,775 deaths in speeding related crashes in 2023, 29 percent of all traffic fatalities that year. An arrival time saved by driving faster is borrowed against exactly that statistic.

Building a plan you can drive

A travel plan is a small chain of arithmetic and every link should be written down. Start with distances per leg, choose an average speed per leg from experience, add named stops with lengths, shift the arrival onto the destination clock, and only then compare against any deadline and read off the departure time. When the departure lands at an hour you would not choose to drive, add the margin at the departure end, not by inflating the average speed.

• Convert each leg to hours before adding, and quote the total in hours and minutes.
• Budget one unplanned stop on any drive past three hours.
• Shift the arrival once, destination clock, and say which clock you mean.
• For commercial trips, check driving hours, the 14 hour window and the 30 minute break before trusting the arrival time.

Run the numbers twice with two different average speeds, one normal and one slow. If the slow case still makes the deadline, the plan is sturdy; if it does not, the gap you just found is the conversation to have before the wheels roll.