Jump to content

16x10’s on a 2003 Silverado z71 1500

T_Grant
 Share

Recommended Posts

T_Grant New Member

T_Grant

Posted
Posted

I have a 2003 Silverado 1500 z71 and I’m looking for someone who might be able to give me more insight on whether or not 16x10’s will fit on my truck. 
 

it is 4wd wheel drive and has disc brakes on the front and rear. It also has factory 16 inch rims on it now. 
 

I’m reading that apparently that only the HD’s and the hybrids came with factory 16’s and mine isn’t, and hasn’t been either. 
 

I’m just looking for someone who can give me a clearer picture and a more exact answer. I’m reading a ton of different things with conflicting answers. Thanks in advance for any and all feedback! 
 

 

Sharpz Enthusiast

Sharpz

Posted
Posted
3 minutes ago, T_Grant said:

I have a 2003 Silverado 1500 z71 and I’m looking for someone who might be able to give me more insight on whether or not 16x10’s will fit on my truck. 
 

it is 4wd wheel drive and has disc brakes on the front and rear. It also has factory 16 inch rims on it now. 
 

I’m reading that apparently that only the HD’s and the hybrids came with factory 16’s and mine isn’t, and hasn’t been either. 
 

I’m just looking for someone who can give me a clearer picture and a more exact answer. I’m reading a ton of different things with conflicting answers. Thanks in advance for any and all feedback! 
 

 

If you look on the inside drivers door panel around where the lock assembly is, you will see a print out of what tire size your truck came with or you can do a vin number check.  Just so you know though, my 2004 GMC sierra says 16 inch on the door but came with 17s at the time when I bought it.  I have a 99 (new style) that came with 16s.

swathdiver Senior Enthusiast

swathdiver

Posted
Posted
6 hours ago, T_Grant said:

I have a 2003 Silverado 1500 z71 and I’m looking for someone who might be able to give me more insight on whether or not 16x10’s will fit on my truck. 

 

You're going to need to trim, they are going to rub and you will definitely need to lift the truck to get that wide of a tire in there.  Those will kill your gas mileage.

 

Most folks with these trucks looking for bigger wheels opt for an eight or nine inch wide wheel in either 17" or 18" or 20" diameter.

 

 

  • Like 1
T_Grant New Member

T_Grant

Posted
  • Author
Posted
6 hours ago, Sharpz said:

If you look on the inside drivers door panel around where the lock assembly is, you will see a print out of what tire size your truck came with or you can do a vin number check.  Just so you know though, my 2004 GMC sierra says 16 inch on the door but came with 17s at the time when I bought it.  I have a 99 (new style) that came with 16s.

The inside panel says that it came with 16s. So does that mean that if I opted for the 16x10 rims that I shouldn’t have fitment issues from the caliper?

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

So long as the offset of the rim is similar to the factory, they won't hit the calipers.

 

The tires will just rub everything else because they much wider than stock.

  • Like 2
Sharpz Enthusiast

Sharpz

Posted
Posted
15 hours ago, T_Grant said:

The inside panel says that it came with 16s. So does that mean that if I opted for the 16x10 rims that I shouldn’t have fitment issues from the caliper?

as stated by SD and Cam, the issue you will have is rubbing not your caliper or rotor.  

  • Like 1

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...