12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHtrack day chestnut
Leading reported evidence
Test car yet
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
Just wondered whether you had tested your car yet.
Leading evidence: 'Test car yet' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Recommend track days' (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.
Suggestion
I would recommend track days to anyone who wants to find out about their cars.
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
So I chose not to book the track day as it was non-refundable but I am still going (next wednesday) as a passenger so they can measure the car using their equipment.
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
So I chose not to book the track day as it was non-refundable but I am still going (next wednesday) as a passenger so they can measure the car using their equipment.
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.
12 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Porsche Club GB: 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: 20261027T031046Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Sorry to ask the obvious but I'm trying to find a thread decribing how i measure my exhaust noise levels. I have borrowed a meter and want to know where I stand to measure and at what revs. I'm planning Silverstone evening event limited at 98dB. Any chance? 996C2 + fabspeed exhaust.
Thanks.
no chance with the fabspeed!!
go to a local track or get a db noise measurer. I reckon with the fabspeed you woul dbe knocking on 104dbs.
if you do go to the track, park the rear over the grass to absorb noise. also make sure you are not near other cars or walls that will reverberate the noise.
At Goodwood in my previous 993, the sound tester was approx a metre from the back of the car and at c.4,250rpm.
It did not seem to me to be very scientific since I hit 105Db straight away with the RSR's. A second attempt by bringing the revs up slowly through the range secured entry onto the track where we had a brilliant time but being completely outshone by the GT3 boys.[
]
HTH, Simon
Yes I did test it. Got quite a variation but mostly over 100-102db (3db being double the volume!). So I chose not to book the track day as it was non-refundable but I am still going (next wednesday) as a passenger so they can measure the car using their equipment.
Having siad that - took the Porker to work today and drove home the scenic route. What a blast
and the exhaust note sounded lovely.
I do find the fabspeeds slightly tiring on long journeys, the boxes are a different shape to standard and mine fouled slightly with the heat shield on one side. I suspect that is responsible for a slight boom in the cabin.
If you are near Derby or Uttoxeter (or Silverstone next Wed eve) you can hear it for yourself.
Thanks for the offer Neil but I live in Surrey so won't be around. Took my car to the all day at Silverstone on 29th June though and had an absolute blast, you will enjoy it.
I am booked in to Goodwood on 1st August which has a 105dB limit, so it sounds like the Fabspeeds should be okay (assuming that they arrive and I fit by then).
Looking forward to the soundtrack.
Ended up I didnt do the track day in my car and I couldnt find the noise man at silverstone either to check if mine would be ok in the future. But there were 2 Noble M12's that were a lot noisier than mine and yet the noise man said it was a well behaved day with noone near the limit.
There another silverston eve aug 2 so Im probably going to do that.
Probably bad etiquete to reply to your own comment but ....
Went back to silverstone and did the track day this eve. Had no problems with the noise man, and I was far from being the loudest. Fantastic day, no mishaps, thoroughly reccommend it to anyone who hasnt yet done a track day with their 911. Just confirmed what fabulous fabulous car it is. Never felt out of control, progressive understeer followed by gentle oversteer under power. Munched my tyres but worth every penny.
Regards
Neil
Pleased to hear you enjoyed Silverstone Neil. I have also been to Castle Coombe and Goodwood this year and thoroughly enjoyed it. I can't praise the 996 enough. I would recommend track days to anyone who wants to find out about their cars.
Fabspeed boxes arrived last week and are now fitted. Fairly easy, apart from the rusted bolts that needed to be cut off the existing clamps.
What a fantastic sound. Still surprises me when I fire it up in the morning, probably surprises my neighbours even more. The car definitely seems to breathe easier now and feels a bit quicker, but one of the baffles in the old box was loose and this was probably choking the car. I look forward to every tunnel now.
Enjoy the car.
Malcolm