Adding travel time to Google maps

I use Google Maps a lot, they're very convenient.
I allot my travel time based on a speed of 50 MPH. I believe Google uses an average speed of 65 MPH, which I find to be unrealistic when traveling by RV.

I also add a lot of time to Googles time. I agree with gbopp, 50 mph average, so I just count on 2 hours per hundred miles. Not much thinking involved.

I wish mapping software would have an option for towing. The ridiculous towing speed limits in CA can really alter the estimated time.

We disregard the times given and go by the standard of 50 miles made good in an hour for the run. This usually works out very close as dog walks, bathroom breaks and a lunch stop will make the google times meaningless. We are also in no hurry so speed limits are not what we go by. Cruise is usually set for about 59 to 64 depending on terrain and traffic.

I've found the Google maps estimates to be not too far off for me in my motorhome, for just driving time (not including fuel stops, lunch stops, detours when trying to get back on the route after a fuel or lunch stop, and such like)--at least close enough for rough planning purposes. Driving a motorhome isn't exactly like towing, of course. I do tend to cruise around the speed limit most of the time, at least here in the Northeast where we don't have super high limits.

From what I can tell, in many places Google Maps uses the actual speed limit in their calculations. I find the projected travel times are not something I can achieved in the western states, as I just won't tow at 80 MPH in Utah for instance. But in states where the speed limit is say 65 MPH, I am closer to what Google Maps projects. But on longer days (300+ miles) I always add an hour or so. Maybe lunch, a gasoline stop, and three or four bathroom breaks! ;)

50 mph is accurate for us and it makes the math easy to do in your head.

BarabooBob wrote:
I also add a lot of time to Googles time. I agree with gbopp, 50 mph average, so I just count on 2 hours per hundred miles. Not much thinking involved.

I'm going to use this.

I never use Google maps for anything. I live on a highly traveled main road, in a small town, just of I77. If I ask Google to find my house it can’t do it. Apple Maps does, Garmin does, just not Google. So if it can’t find me, I’m not using it.

But then again I don’t use anything owned by Google other than perhaps Utube to find out how to do something.

I use Google Maps mainly to get a idea of traffic in front of us while traveling. What ever the mileage is says to the destination I just divide by 50 and disregard their estimate arrival time.