31 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHis this the most expensive 996?
Leading reported evidence
Repair front end damage and sold
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
It had repaired front end damage and sold for 75k.
Leading evidence: 'Repair front end damage and sold' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'rpms didn't get too high' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Repair front end damage and sold' (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 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
Bought a salvage car, swapped motors (motor ended up being a rebuilt with all of the upgraded IMS, etc), sold the rest of the parts from the car, and actually made some money.
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 suspect a cause
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.
Suspected cause
Assuming it happened all at once, it it likely the RPMs didn't get too high.
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
Funny how a little change on the headlights change the car's look completely.
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
Funny how a little change on the headlights change the car's look completely.
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
Bought a salvage car, swapped motors (motor ended up being a rebuilt with all of the upgraded IMS, etc), sold the rest of the parts from the car, and actually made some money.
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.
31 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I also imagine the carbon interior didn't help the final price, not the best looking option IMO for a 996.
I would be afraid of an 18 year old car with only 5,176 miles on it. Every seal on the engine is dried up from non-use. There are times when low mileage is not a good thing. And for 50K? The engine is probably full of sludge and acid.
This is for collectors only; for $50k you can get a nice 996 turbo, pull off the FWD system to make it RWD only, add performance exhaust and maybe some aftermarket intercoolers, a small tune and you have almost the same car.
Precisely. I find that BAT auction hilarious. It just can't be "car people" bidding on that thing, at least i hope not. Investor collectors have ruined the market for so many models and if they thing they're gonna triple or even double their money on this in 5-10 years they are mistaken.
I am living proof that a number of 214 in Range 2 (even less time that this motor) is enough to destroy a motor. Of course that is in a stock 996 which is not as beefy as the GT2.
And it seems like each spec of 966 doubles in value. $20K for a nice C2/4 - $40K for a Turbo - $80K for a GT3 - $160K for a GT2.
Did your engine failure occur shortly after a "money shift"? It seams that 0.8 seconds, or 0.55 seconds in your case, wouldn't be enough to get the revs way up. Is there a chance your failure was coincidental?
It 100% happened after a money shift, made it two more laps, and have it on video. Going from 4th to 1st while doing a 100 will do some crazy things. I have seen plenty of cars with higher range 2 counts than mine go on to lead perfectly fine lives though. Mine was just not one of them.
Sold for $150k + buyers premium. Gotta wonder if the seller would have benefited from putting another 25hrs on the engine before selling, to dissuade the Range 2 fears. I also imagine the carbon interior didn't help the final price, not the best looking option IMO for a 996.
It all worked out. Bought a salvage car, swapped motors (motor ended up being a rebuilt with all of the upgraded IMS, etc), sold the rest of the parts from the car, and actually made some money.
Lots of work to get it done, but was still kinda fun. Still just wish the shift didn't happen the first run session of a three day weekend.
Wife hates riding in it and shoots down idea of selling it. My son will get it when he older, buying him long hood bomber to restore for his first car! Planning on 6cup to take care of track duty in future when he gets older.
Now its time more garage space!
Funny how a little change on the headlights change the car's look completely. This distinction will caught on later in terms of value and collectability just for the odd ball creation.
I understand that you could make one similar for less by taking a "regular" TT and doing the work but I think bidders are paying this because it is a real GT2. Might not matter to some but matters to others. Same argument for Shelby Mustangs and Cobras. I'm cheap so I'd take a TT and do it myself.
Dif'rent strokes for dif'rent folks, especially when considering this cars specific options and exclusivity. I wonder how many GT2s are left? I found a burned one in a junkyard in NC. Shame.
As far as the DME report hullabaloo, who cares? You didn't buy it.
50 hours is the recommended post over-rev cut off for assuming the engine internals are likely undamaged. Doing the math, the entire time spent in range 2 was 0.81 seconds. Assuming it happened all at once, it it likely the RPMs didn't get too high. Unfortunately, the ECU doesn't capture max RPMs.
My 1999 has spent 3.1 seconds in range 2, the last time in 2014.
There was another GT2 that sold recently with much higher range 1 (maxed out) and range 2 values. It had repaired front end damage and sold for 75k.
Edit: I didn't realize this was an older thread I had made a similar comment on.
