Jump to content

Who is running 22" Wheels? Step in please!

Arkangel

By Arkangel
in Modifications & Accessories

 Share

Recommended Posts

Arkangel Enthusiast

Arkangel

Posted
Posted

Hey folks,

 

Just picked up my 2020 AT4 this past week and am looking at wheels/tires, but havent really found the look that I want, I am thinking 22" but not sure yet.

 

If you are running 22's can you please tell me how it affected the ride? Wheel/Tire Specs? Side view pic please?

 

TIA!

Arkangel Enthusiast

Arkangel

Posted
  • Author
Posted
1 hour ago, Schmidty said:

my ride improved with new shocks and new tires over stock. 

 

 

 

 

5EA209E3-7E68-421F-93A1-D7A1FFFB8012.png

That looks great!

 

whats the width/offset and tire size? Any rubbing?

 

What shocks Did you go with?

Schmidty Enthusiast

Schmidty

Posted
Posted
14 minutes ago, Arkangel said:

That looks great!

 

whats the width/offset and tire size? Any rubbing?

 

What shocks Did you go with?

check the other thread, a bunch of guys have included their lifts and wheels/tires combo specs

 

mine is a readylift 3.5/3” sst lift kit, 22x10 -18mm fuel blitz wheels with 35x12.50x22 nitto ridge grapplers

 

my lift kit came with bilstein shocks

firedab Enthusiast

firedab

Posted
Posted

I just ordered 22's but debated for a while. Hope they turn out like i'm expecting! 22x10's -18 and 285/55R22 Nitto Ridge. I have no leveling or lift kit, will see about the rubbing. Those tires from what I read should work with minimal trimming. I'll let you know and post a pic when they get here...

Arkangel Enthusiast

Arkangel

Posted
  • Author
Posted
1 hour ago, firedab said:

I just ordered 22's but debated for a while. Hope they turn out like i'm expecting! 22x10's -18 and 285/55R22 Nitto Ridge. I have no leveling or lift kit, will see about the rubbing. Those tires from what I read should work with minimal trimming. I'll let you know and post a pic when they get here...

Definitely let me know! I am not looking to lift or level, just want wheels/tires and looking at upgrading the shocks to Bilstein 4600 or 5100

Schmidty Enthusiast

Schmidty

Posted
Posted

I wouldn't get a low or negative offset wheel if you aren't leveling or willing to do some trimming. I have a 3.5" lift and I still rub on both the front and rear of the front wheel wells. I'd venture to say my -18 offset with my 10" wide wheel has a greater impact on the trimming and rubbing than the tire size does. The tires are only roughly .9" wider in diameter than stock, which is only less than a half inch wider from the center of the wheel (figure how much closer the tire is to the things it could rub on).  The offset is what creates the need for the trimming more than the tire, when turning the wheels and moving up and down with the suspension.

 

The offset matters because when you turn your wheels, your wheels/tires stick out further than before, effectively creating a larger radius from the mounting point, which is why you have to trim to accommodate them.  There's some good graphics out there demonstrating this, so you can better understand. But hopefully this helps clarify some of your concerns.

  • Like 1
Arkangel Enthusiast

Arkangel

Posted
  • Author
Posted

Thanks for the input, im pretty set on -18 to -25 offset and wouldnt mind trimming SOME plastic as I did for my 1500, but there doesnt seem go be many people who have put 22’s on without a lift, and depending on the tires some of the aftermarket 20’s just look too dinky on these trucks

  • 3 weeks later...
firedab Enthusiast

firedab

Posted
Posted (edited)

 

 

Ok, got them on...

I ended up moving the front bumper forward about 1/2", took front mud flaps off and will modify them to eliminate the rub there. Minimal mods to make this work. They do stick out a bit more than I would prefer, but I'll get used to it... Looks great, now debating on adding the 3/2 lift?!?

 

Truck 1.jpg

Edited by firedab
Arkangel Enthusiast

Arkangel

Posted
  • Author
Posted (edited)
5 hours ago, firedab said:

 

 

Ok, got them on...

I ended up moving the front bumper forward about 1/2", took front mud flaps off and will modify them to eliminate the rub there. Minimal mods to make this work. They do stick out a bit more than I would prefer, but I'll get used to it... Looks great, now debating on adding the 3/2 lift?!?

 

Truck 1.jpg

Man that looks great! You kept everything the same? 22x10 -18 and 285/55R22? Post pics of how much of the mudflap you have to trim

 

this is still with no leveling kit also right?

Edited by Arkangel
firedab Enthusiast

firedab

Posted
Posted

Yup, those are the wheel and tire specs, and no leveling kit, but I did turn the keys (bolts) two turns, have about an inch difference between front and rear. I’m going to work on mud flaps tomorrow, I’ll post when I get them done.

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

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...