I do it for the tranquility
I absolutely wouldn’t do this job if I couldn’t drive nights.
What's the reasonable average speed for trucks in North America?
Discussion in 'Ask An Owner Operator' started by fourbugs, Jun 20, 2025.
Page 5 of 7
-
-
Trucking Jobs in 30 seconds
Every month 400 people find a job with the help of TruckersReport.
-
77fib77 Thanks this.
-
Okay, here it is for the believers, lol
I was thinking that it would actually be lower than I said because of two factors..One I haven’t looked at my stats in a year or so and also I’ve been running a lot slower the last few months. My last quarter ifta that I posted awhile back came in at a shockingly low 4.2? Mpg. Was a significant drop from my norm.
Lately I’ve been just setting the cruise on 66-67 mph. Between that and my steer tires causing vibrations at 70 and above. Seems to be paying off because according to my dash I’m seeing mpg’s that I’ve never seen before..
just turn your computer on its side to view
Sons Hero, D.Tibbitt and bryan21384 Thank this. -
rluky13, Sons Hero and bryan21384 Thank this.
-
It's a lot of moving parts to this question. So today, I started in Holts Summit, MO and ended in Sioux Falls, SD. 525 miles roughly. That's an average of 56 mph. Traffic in Kansas City, construction in Iowa and South Dakota, and about 30 min idle time today. I set my cruise to 65. I think for the life of a truck, the average is probably going to be closer to the low 50s on average. Mountains, construction, west coast speed limits, all are factors. If you idle a lot, i see a scenario where that will go down because performance will be impacted over time. You won't have the same power because of soot build up in these emissions trucks, not to mention fuel injectors get messed up over time if you don't have regular overheads. Not to mention if you don't use the cruise, I believe that can lower the average over the life of the truck. Speed limit is one thing, but actual speed is another and anything north of 60 is difficult to keep consistently.
DISCLAIMER: I am only speaking about running in the USA. I don't have any first hand knowledge about running in Mexico or Canada.TexasRiverRat Thanks this. -
I'm happy there is no digital evidence from the 80s.
Leave Salinas Ca. on Thursday night and be sitting in Montreal Quebec on Monday morning.Sons Hero, Numb, D.Tibbitt and 1 other person Thank this. -
-
Bet that fighter jet woke you right up!Sons Hero, FullMetalJacket and Star Rider Thank this. -
Didn’t even realize this stuff was available to look at. Wish it showed the average of the total miles I’ve driven this truck.
Guess I’m just an outlaw truckerSons Hero Thanks this. -
- Garmin's 'total time' is exactly the number of hours the device has been powered on (regardless of its status, such as whether the destination is set or not, etc)
- your Garmin is always on when your engine is running, and always off when your engine is not running.
If you ever saw raw GPS data, you'd know that the positioning estimates from each signal refresh NEVER stays on the exact same spot. Rather, it constantly jumps around (usually within 1-50ft circle). In other words, something like the speed you see on your Garmin as well as the position icon on your map, is not exact representation of raw data. It interprets the raw data and creates somewhat imaginary to provide more useful data that is more in line with real world (otherwise, your GPS will show you some speed when you're completely stationary, and your position icon constantly moves around your actual position, and your distance on GPS would be far longer than actual distance).
What all this means? It means GPS is not really accurate at low speed (especially on <5 mph) and also it's not really good at differentiating between slow movement and complete stationary (especially if it's set primarily for vehicle use), hence it probably uses some sort of threshold speed or positioning difference to differentiate between moving and stationary time. If threshold is set to 10mph, then huge portion of your slow driving time (around truck stops, loading/unloading point, etc) wouldn't be included on your moving time and this will boost up your moving avg speed significantly. To determine its accuracy, you have to know its algorithm and parameter exactly, but since that is unknown, it's pretty useless at this point.
If you want to compare apples to apples, then just use the same methodology, odometer / engine hours. Of course, even the exact same driving can result in drastically different data with this method (a person who idles all night vs who stops engine immediately on every stop), and that's why I try to look for someone who never (or at least rarely) idles.
- 27.2 mph = 252,918.46 / 9277.2
- 20.7 mph = 252.918.46 / 12,167.2
- 36.1 mph = 335,121.1 / 9277.2
- 27.5 mph = 335,121.1 / 12,167.2
Trucking Jobs in 30 seconds
Every month 400 people find a job with the help of TruckersReport.
Page 5 of 7