Jump to content

MPG

Cuongdyna
 Share

Recommended Posts

Cuongdyna Enthusiast

Cuongdyna

Posted
Posted (edited)

Hey Everyone, new to the forum. I have 2021 GMC Sierra 1500 AT4 3.0 diesel. What are you guys getting on your MPG? If your getting 30+ mpg what speed are you driving? I'm getting 23 to 24 average hand Calculated and that driving 70% hwy. Thats driving between 70 to 80 mph on the hwy. I see people on YouTube getting 30+ mpg. The only way I can see me doing that is driving 55 mph on the hwy. I would like to hear what you guys are getting.  

Edited by Cuongdyna
btj_z71 Enthusiast

btj_z71

Posted
Posted
17 minutes ago, Cuongdyna said:

Hey Everyone, new to the forum. I have 2021 GMC Sierra 1500 AT4. What are you guys getting on your MPG? If your getting 30+ mpg what speed are you driving? I'm getting 23 to 24 average hand Calculated and that driving 70% hwy. Thats drive between 70 to 80 mph. I see people on YouTube getting 30+ mpg. The only way I can see me doing that us driving 55 mph on the hwy. I would like to hear what you guys are getting.  

If you have a 2wd with the 3.0L Duramax and low rolling resistance street tires, maybe 30 MPG is in the realm of possibility.  I've got 27.4 MPG with my LTZ Z71 3.0L Duramax for comparison.  Getting anymore than that would be a challenge.

 

No way 30 MPG is happening in an AT4 which has a 2in lift (increasing drag resistance) and AT tires (increased rolling resistance).

 

Go for a cruise at 55 or 65 MPH and you'll get about the best MPG you can squeeze out.

 

There are so many factors that play into MPG: Altitude, air temperature, relative humidity, headwinds, tailwinds, if its raining, what accessories you may or may not have installed, etc. 

71_340 Enthusiast

71_340

Posted
Posted

Mine is brand new.  DIC shows 24.5 MPG average for the first 180 miles, 50/50 highway/city.  It's cold here so I used the remote start twice.

 

Keep in mind that it take time for the engine to break in, it's cold and winter fuel (diesel or gas) carries less energy.

Duramax3oh Enthusiast

Duramax3oh

Posted
Posted

I’m roughly seeing these figures consistently. Flat drive, elevation sea level. 

60mph ~ 33mpg

65pmh ~ 30mpg

70mph ~ 26mpg

75mph ~ 23mpg

80mph ~ 20mpg

 

 

  • Thanks 1
Cuongdyna Enthusiast

Cuongdyna

Posted
  • Author
Posted
3 minutes ago, Duramax3oh said:

I’m roughly seeing these figures consistently. Flat drive, elevation sea level. 

60mph ~ 33mpg

65pmh ~ 30mpg

70mph ~ 26mpg

75mph ~ 23mpg

80mph ~ 20mpg

 

 

Nice! Is your truck 2X4 or 4X4?

Jason Rebellion Enthusiast

Jason Rebellion

Posted
Posted (edited)
3 hours ago, btj_z71 said:

If you have a 2wd with the 3.0L Duramax and low rolling resistance street tires, maybe 30 MPG is in the realm of possibility.  I've got 27.4 MPG with my LTZ Z71 3.0L Duramax for comparison.  Getting anymore than that would be a challenge.

 

No way 30 MPG is happening in an AT4 which has a 2in lift (increasing drag resistance) and AT tires (increased rolling resistance).

 

Go for a cruise at 55 or 65 MPH and you'll get about the best MPG you can squeeze out.

 

There are so many factors that play into MPG: Altitude, air temperature, relative humidity, headwinds, tailwinds, if its raining, what accessories you may or may not have installed, etc. 

I averaged 36 and some change for 25 miles going 55 thru Tennessee. BFG All terrains and the AT4 lift on my 5.3 X31 SLT. 

E717A5CE-CE90-487B-9044-6BCA566BDF0B.jpeg

Edited by Jason Rebellion
Salsa De Piña Enthusiast

Salsa De Piña

Posted
Posted
9 hours ago, Jason Rebellion said:

I averaged 36 and some change for 25 miles going 55 thru Tennessee. BFG All terrains and the AT4 lift on my 5.3 X31 SLT. 

Which hill were you going down?

Booger T Enthusiast

Booger T

Posted
Posted
8 minutes ago, f8l vnm said:

I sometimes average 99 MPG when I go downhill :)

Me too?

 

5 minutes ago, Salsa De Piña said:

Which hill were you going down?

You know, that hill?

Booger T Enthusiast

Booger T

Posted
Posted
12 hours ago, btj_z71 said:

There are so many factors that play into MPG: Altitude, air temperature, relative humidity, headwinds, tailwinds, if its raining, what accessories you may or may not have installed, etc. 

Well, there ya go

Duramax3oh Enthusiast

Duramax3oh

Posted
Posted

I don't like to use the instant mpg reading other than to get a vague idea of the general range we may be talking about.

 

I take a lot of long highway trips and prefer to set cruise control at different speeds and then see how the 25-mile avg and 50-mile avg readouts look. It's hard to get any more accurate than that IMO.  Particularly when you do that on I-10 in Texas and Louisiana... there is NO DOWNHILL ?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...