Jump to content

Average Gas Mileage Poll


MarkD

Average Gas Mileage Poll  

121 members have voted

You do not have permission to vote in this poll, or see the poll results. Please sign in or register to vote in this poll.

Recommended Posts

Posted
Please post your trucks configuration and mileage.  Is your truck stock?  Comments?  What made the biggest improvement?
Posted

Depends...I get 9-10 in town, got almost 14mpg once on the highway and get 6-7mpg towing our 10,000lb 5er.

 

Truck currently is a few miles short of 12,000 miles and is completely stock.  Have thought about getting the Superchips tuner for the mighty 8.1, but it has enough power already, its just a bit thirsty under load.

 

Truck specs in sig.

 

Bob

Posted

Stock

12.5 unloaded avg. speed 50mph

8.9 loaded with slide in camper, towing approx. 4000 lbs @ avg. 55 mph

 

Believe it or not I did get 17 mpg once with my slide in, no trailer though at an avg. 68 mph.  I checked the calculator 3 times, couldn't believe it.  Must have had a really good tailwind... :nono:

Posted

8.1l, 2002 Crew CAb, automatic.  100% stock, short bed.  14500 miles

 

It is my daily 'commuter' (30 miles 1 way).  City or highway, I get about what I expected when I purchased this vehicle, a consistant 12.3 to 12.6 mpg of gas (and of course the unexpected 'normal' 1 qt of oil per 1300 miles! :angry:)  The absolule best I ever got was on one leg of a road trip where I was the 5th car in a 8 vehicle 'convoy'.  I got 13.2 doing 85+ mph (for a whole tank).

 

 

bummed.

Posted

01 CC short bed, 3" lift running 295's, Superchips programmer, The Other Guys headers, UPD intake, de-screened mafs, Direct Hits ignition.

Getting 12 mpg @80-85 mph

13-14 mpg @60-65 mph

and 10-11 around town.

No complaints from me specially with a big truck pushing 400 or so ponies. :cheers:

Posted

02 HD.  Ext cab, 6.5 bed, 4x4, 8.1 with Allison.

 

So far I have just bolt-ons like Volant intake, custom Magnaflow mufflers and a few "free" mods.  I have my cam in the garage awaiting installation as well as some heads 8.1 heads being worked on now.

 

I posted about 9.5mpg, but that has to do with my heavy left foot.  I race just about anything in the lane next to me and commonly run it up to the 100mph speed limiter.   :cheers:

Posted

That doesn't surprise me.  Simple physics really.

 

On paper, the 6000 is smaller therefore should consume less than the 8100.

 

However, in reality, the 6000, being smaller and less powerful, has to to be worked harder to move the same amount of mass as the bigger 8100.

 

THe 6000 does have one positive though, it doesn't have to twist that Allison.

Posted
Hey, I'm new to this site, and the main reason I joined, was to pick other brains about my truck's mileage. I have a 2001 4x4, ex-cab dually, 8100, Allison, and can't seem to break the 9 M.P.G. barrier! The truck has 6400 miles. Will this get any better? Please say it will, because the Power Stroke is calling my name if something doesn't give!
Posted

That's Ok, I don't get too worked up over the 10mpg avg.  I knew when I bought the truck I was buying a truck that weighs 6,260lbs and has a nearly 500 cubic inch mill under the hood and packing 4.10's in the pumpkins, wasn't going to scare Chevy Metro's anytime soon.

 

As a matter of fact, fuel economy ranked about 129th on my list of "important things to consider" when I purchased it.  That's why I can't comprehend why people come asking how bad the mileage is on a 496 cube monster.  What where they expecting to see?  24mpg??   ???

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...