Jump to content

Will it Fit Guide

Kman220
 Share

Recommended Posts

Kman220 New Member

Kman220

Posted
Posted

Will it Fit Guide:

These are all sizes that will fit our trucks stock or with the correct modifications listed next to the size.

I hope this becomes a useful tool for everyone. This is strictly a guide, not an end all be all. Full disclosure: there will be some variation between tire manufacturers, lift manufacturers etc.

This is a live tool I am constantly updating and need more information to continue growing it. I have mostly focused on stock size wheels, but would like this to eventually grow into a comprehensive chart for other configurations. If you have set ups not listed here (or is on here, but you have more information) that you think should be added let me know.

Please include all information for your setup.

Version 1.0

e07ba4459064fee286f022e64c42ce25.jpg

  • Like 2
  • Thanks 1
Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

Pretty cool idea. I'll contribute, since I have 17's, which is less common. 

 

285/75/17 will fit on the stock 17's, at stock height, with GM mudflaps, and no trimming. I ran those for nearly 5k miles, without any issues. 

 

285/75/17 will fit on 17x9, +18mm, with 7 cranks on the stock keys (1.5"), without any trimming and GM mudflaps. 

  • Like 1
GTBensley Enthusiast

GTBensley

Posted
Posted

I too run 285/70/17 on stock rims with no rubbing. I started with the truck stock and have plenty of room....now how they keys turned up some and could clear much larger. 

  • Like 1
Kman220 New Member

Kman220

Posted
  • Author
Posted
Pretty cool idea. I'll contribute, since I have 17's, which is less common. 
 
285/75/17 will fit on the stock 17's, at stock height, with GM mudflaps, and no trimming. I ran those for nearly 5k miles, without any issues. 
 
285/75/17 will fit on 17x9, +18mm, with 7 cranks on the stock keys (1.5"), without any trimming and GM mudflaps. 

Thanks Big Whiskey. Your post on another thread is actually where I verified that the 285/75R17 would fit! I appreciate the info, I’ll add to it!


Sent from my iPad using Tapatalk
  • Like 1
Kman220 New Member

Kman220

Posted
  • Author
Posted

I should be pushing out a new update later today. Any other inputs, notes or corrections? This will be update v1.1. It should clarify some things as well




Sent from my iPad using Tapatalk

  • txab pinned this topic
  • 2 weeks later...
  • 1 month later...
gforce_15 Enthusiast

gforce_15

Posted
Posted

I see you have info on 275 65 20 on a +15 offset wheel requires trimming of mud flaps. I have 275 65 20 on stock +44 wheels and they fit without trimming. I previously zip tied the fender liner a little tighter to the frame on both front fenders for my other wheel set up so I'm not sure if that was required or not for the 275 65 20 on stock wheels. I guess I will add my other set up is 275/60/20 on +18 wheels and they fit with no trimming either. 

  • 2 months later...
  • 4 months later...
  • 4 months later...
Jrs 94 Enthusiast

Jrs 94

Posted
Posted

What is "bags on rear" on the chart for size 305/70/18? What does that mean? I have a 2018 2500hd 4wd. Will have a leveling kit. Want to keep stock wheels.

  • 1 year later...
DMAXNAZ Enthusiast

DMAXNAZ

Posted
Posted

2015 GMC 2500hd cc 4wd 2in level, nothing trimmed and front flaps are still installed. Wheels are fuel sledge 18x9 +1. My last set of tires were 285/70/18 open country mt. They rubbed only at full turn, mainly for about the first 20k miles. I just installed a set of 285/70/18 ridge grapplers and they have plenty of clearance. After looking at the way the tread pattern is on them, I bet I could have fit 295/70/18 ridge grapplers. I'm bummed that I didn't try one of that size first. I had a set of those tires already waiting for when my new 18x9 +18 wheels showed up. I figured coming in 17mm would allow me one size larger. Long story short is that 5 sets of backordered wheels later, I gave up and just replaced my existing 285's on my existing wheels that were just going to be an extra set in my garage. I guess ridge grapplers must clear a little better for their size compared to the open country mt. Hope this helps the next guy questioning a similar fitment 

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   4 Members, 0 Anonymous, 2,121 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...