Jump to content

285/45R22 Tire choice is limited, any real usage recomendations?

Blackpearl#1
 Share

Recommended Posts

Blackpearl#1 Enthusiast

Blackpearl#1

Posted
Posted (edited)

1.  I already own the truck and am just looking for recs from people who have used this tire size before.

2. I already know there are many out there that don't like the 22s, but refer to 1.

3. I live in WI so snow does come into play

4. I do tow snowmobile trailer and boat now and then, but nothing too heavy. 

5. I put Advanta ATX-750s on my plow truck and like them, but that's a 16 wheel.

6. The Bridgestone's that are on there now have treated me good.

 

EDIT:  Just read another tire thread and this was a cool idea

Noise,  kind of important.  Don't want loud for sure

Appearance,  not much tire showing anyways but as long as it looks like a truck tire, I'm good.

Traction,  I live in WI so all season is a must

Tread life, would love a hi mileage tire, but I do understand that when you get into the low profile stuff, that's a tough one.

 

So any real world advice would be greatly appreciated.

Kris

Edited by Blackpearl#1
kylant Enthusiast

kylant

Posted
Posted

this size tire sucks. there is a very limited supply. 

the only one I have found that may work for you is the nitto terra grappler g2.

i am in a similar situation. 

i am looking at 20" wheels for the simple fact there are many more tires to choose from

Denali34 Enthusiast

Denali34

Posted
Posted
23 hours ago, Blackpearl#1 said:

1.  I already own the truck and am just looking for recs from people who have used this tire size before.

2. I already know there are many out there that don't like the 22s, but refer to 1.

3. I live in WI so snow does come into play

4. I do tow snowmobile trailer and boat now and then, but nothing too heavy. 

5. I put Advanta ATX-750s on my plow truck and like them, but that's a 16 wheel.

6. The Bridgestone's that are on there now have treated me good.

 

EDIT:  Just read another tire thread and this was a cool idea

Noise,  kind of important.  Don't want loud for sure

Appearance,  not much tire showing anyways but as long as it looks like a truck tire, I'm good.

Traction,  I live in WI so all season is a must

Tread life, would love a hi mileage tire, but I do understand that when you get into the low profile stuff, that's a tough one.

 

So any real world advice would be greatly appreciated.

Kris

I am currently running 285/55R22 Nitto Terra Grappler G2 tires. I found them much smoother than the OE Bridgestone's. They are stiffer being 10ply but I prefer that. They also come with a 55k warranty which is important to me as I drive 100 miles a day for work. I am very pleased with them. They were very reasonable too! I got the set for less than $1900 out the door with road hazard!! 

KMGZ400 Senior Enthusiast

KMGZ400

Posted
Posted

if you are looking for a beefy tire, the Nitto Ridge Grappler are really good tires, aggressive tread pattern and look great while not having the annoyances of the Toyo MT's. Terra Grapplers are great tires as well.

DrewSal Enthusiast

DrewSal

Posted
Posted (edited)

Nitto Terra Grappler in that size is also a good option. Less chunk but very quiet and a great ride

Edited by DrewSal
updated with photo
DrewSal Enthusiast

DrewSal

Posted
Posted (edited)

Edit these are the 285/55/22 not 45s

Wheel.jpg

Edited by DrewSal
updated tire size
parthery Enthusiast

parthery

Posted
Posted

Same problem. The stock Bridgestones are disappointing. I did get GM to pay for two and I paid for 2 so I had to go through the dealer to get them. My choices were either another set of Bridgestone RT H-S, Alenzas, or Michelin Defenders. I went with the Michelins. I miss the aggressive tread, but the truck rides better on the highway. 

kylant Enthusiast

kylant

Posted
Posted
9 hours ago, DrewSal said:

Edit these are the 285/55/22 not 45s

Wheel.jpg

those are 285/55 (34.37" tall) and not 285/50 (33.27" tall)???

 

deputy Enthusiast

deputy

Posted
Posted

I am using

yokohama 305/45r22 118v with no rubbing issues.

20171218_111257_HDR.jpg

DrewSal Enthusiast

DrewSal

Posted
Posted
13 hours ago, kylant said:

those are 285/55 (34.37" tall) and not 285/50 (33.27" tall)???

 

Correct

  • 6 months later...
Blackpearl#1 Enthusiast

Blackpearl#1

Posted
  • Author
Posted

Bumping this up.  Getting much closer to tire time for me.  Thanks to all that have replied.  Also wondering if there is another forum section I should have put this post in?  Not the best with this forum yet, still learning my way around.  

Kris

dieselfan1 Senior Enthusiast

dieselfan1

Posted
Posted

I have the 285 45 22's Bridgestone Dueler AT RHS's that came on on my truck and I think they are a good all around tire.

I'm in Minnesota so I see plenty of snow and I'm not dissatisfied with them.

At Discount Tires they are $255 each.  So for a little over a grand not going to break you.

NWI Denali Enthusiast

NWI Denali

Posted
Posted

I think the AT RHS's are a pretty good tire. It's always fun to try something new, but I just may replace them with the RHS's again. They have great reviews on tirerack too. Seem to be one of the better oem tire offerings. Usually oem tires are garbage.

MullerLite New Member

MullerLite

Posted
Posted (edited)

Does anyone know the rim width for the GMC 22" rims that came on the black pack? They have the same 285/45-22 tire on them.

20181013_104800.jpg

Edited by MullerLite
Add photo

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...