9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHYet another tire and wheel question
Leading reported evidence
Check caluclators and the difference
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I've checked the caluclators and the difference from stock is less than 3%.
Leading evidence: 'Check caluclators and the difference' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check caluclators and the difference' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
285 is a no issue on an 11 inch wheel, you can even run 295 with no issues.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
9 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T052503Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I really apologize for asking this question, but I've looked through dozens of threads and haven't seen this exact combo. I have some GT3 wheels, 11 x 18. I would like to put 285 35s on the rear with the 11s. Is there any chance of rubbing? I've checked the caluclators and the difference from stock is less than 3%. Thanks
Just to get a little more tire between the wheel and the road mainly. 30s just seem so darn thin to me and there are potholes everywhere in Atlanta. It also looks a little better to me. I currently have 275 35s on 10 inch rears and my car looks almost lowered relative to the top of the tire and the quarter panel. There doesn't seem to be a lot of room width wise with my current setup, but I have no rubbing issues now.
You realize you don't pick tire size based on look but rather the stock RD (diameter) of the tire? By choosing a tire like the 285/35 you are slapping on a tire with a RD of over 26". Not good. You can get away with it but you are going to get even longer gearing than you have right now. Is your 996 a C4? FYI....your stock RD is 25".
No it's a C2. The calculator I used shows the overall diameter of a 285 35 is 25.85 in or 656.59 mm. The 265 35 is 25.30 in or 642.62 mm. The difference is 2.13% and speedometer is slow by about 2.174%. By contrast the difference in the diameter of the 285 30 is 2.26% and the speedometer is fast by 2.298%. Both are under the 3% margin and shouldn't wreak any havoc with PSM or ABS, at least I don't think so. I want the grip of the 285s for my jaunts through the dragon, but don't want to chance ruining my wheels on potholes or steel plates on our wonderful city streets. My worry is rubbing. Just eyeballing the clearance of my current 275 35s makes me think it could be really close. If I buy the 285 35s on line I'm pretty much stuck with them, hence my foray into the 996 forum. I'm willing to endure the wrath of the purists to get some solid opinions.
