8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTire wear, is this normal?
Leading reported evidence
Reset back
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.
Leading evidence: 'Reset back' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust settings' (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 · Original poster
I'm taking the car in on Wednesday to have the alignment checked, will report back if anyone is interested.
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
This, of course, is assuming that you're running a factory USA stock suspension.
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 · Original poster
A few weeks ago my pressure was running a little low but I would expect that to result in some wear on both sides of the tire, right now it's extremely uneven.
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 · Original poster
A few weeks ago my pressure was running a little low but I would expect that to result in some wear on both sides of the tire, right now it's extremely uneven.
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.
8 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: 20261027T035758Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I had a nail in the tire this weekend and while I was checking out the puncture I noticed that the tires had what I consider to be excessive wear on the innermost treadblock. This is on both rear tires.
The innermost block is about 75% gone while even the second one is barely worn at all (hardly any wear at all).
I know these cars have a lot of negative camber and additional wear could be expected due to the rear weight bias but is this considered normal?
The tires only have about 6000 miles on them (Pilot sports) and it bugs me that the treadwear is so uneven across the surface.
I'll take it and have the alignment checked this week but wanted to get a feel for whether I should get used to this or not.
Thanks,
Keith
I had similar wear on the fronts.
When replacing all 4 tires I had the alignment measured and found extra camber had been applied.
I reset back to a standard setting.
You sound like you have too much negative camber. Yes the rear on a 996 does not last long(average 10-12K), but your uneven ware and 6K is too quick. Have you lowered the car as most lower cars have a hard time having the correct camber adjusted.
Echoing jetskied, your rear tire wear seems excessive, and it's likely due to too much negative camber in back, although other alignment issues may also cause this pattern. How are your tire pressures?
Take your car in and have the alignment checked. If you're concerned about tire wear and longevity, then just have the car reset to the appropriate USA Standard alignment specs.
This, of course, is assuming that you're running a factory USA stock suspension.
Thanks to all for the info, yes this is factory standard US suspension with no mods.
A few weeks ago my pressure was running a little low but I would expect that to result in some wear on both sides of the tire, right now it's extremely uneven.
I'm taking the car in on Wednesday to have the alignment checked, will report back if anyone is interested.
Cheers,
Keith
My inner rears on a 2002 C4 also wore badly by 8000 miles. Toe and camber was out when checked, but tech. did not have porsche tools to adjust settings. any idea how to do it without going to a Porsche dealer.
This is a source reference. Confirm exact model applicability in the original material.
