30 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHIs you spedo accurate ?
Leading reported evidence
Check cayman
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
I take that back, checked my new Cayman today, it's dead-on accurate!
Leading evidence: 'Check cayman' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check cayman' (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
And phones usually only update at about 1Hz (although I think they could do 10Hz if programmed for it?), so for any measurements, make sure your speed is constant on level terrain, and wait one second to check your GPS speed.
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
my 970 GTS - high by 3 mph (also noticed that the cruise is 1 mph than the set speed...set cruise at 79, speedo reads 80?!)
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
my 970 GTS - high by 3 mph (also noticed that the cruise is 1 mph than the set speed...set cruise at 79, speedo reads 80?!)
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
And phones usually only update at about 1Hz (although I think they could do 10Hz if programmed for it?), so for any measurements, make sure your speed is constant on level terrain, and wait one second to check your GPS speed.
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.
30 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 · 1 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T201111Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Saw this posted:
Since we have the benefit of modern GPS technology, I am guessing a lot of people drive around with a map app open that shows your GPS calculated speed.
Can you confirm if the above is true in your Porsche ? this is 100% not true in my DD.
What is your experience ?
Vehicles cannot display speeds less than actual speeds, therefore they over-report speeds.
The MFG's are fined if their Speedo's do not meet International laws ...
One such Law is
ECE-R39 that states that speedometers can't show speeds less than the actual speed, and can never register more than 110 percent of the true speed, plus 4 kph.
That is -0 to +10%+4kph ........So at a true 50mph speed the speedo can't show less than 52.5 mph or more than 57.5 mph
The formula is
0 (V1 - V2) 0.1 V2 + 4 km/h
To read the full ECE-R39 ....
https://unece.org/fileadmin/DAM/tran...18/R039r2e.pdf
Easy test to do is pull up Waze on your phone and drive your 996 or any car. Works the same in my Q7. You can track your speedo and see that its fast in relation to whats reported by Waze.
If this sounds strange to some, the US/Canada are not signatories to UNECE 1958 that initiated these standards.
But Germany is. So while a US car may read within +/- of the actual, our German cars always display faster than actual.
My two Honda's, a 13 Accord and a 14 Accord, they're speedometers are dead on accurate with a GPS speed checker. Both my Porsche's are about 2 mph over. All the European cars I've owned over the years were all about 2 mph off also.
Interesting about ECE-R39
My truck (GM) is within a MPH +/- at 70MPH.
I am really curious if people are actually seeing 75MPH on the speedo at a GPS indicated 70MPH on stock tires as was relayed in the quote in the OP.
Maybe a couple dudes/dudettes could run a test of delta at 10MPH increments from like 20 to 70... Anyone generous to take it on if you could relays the tires (brand and size) you're running that would be helpful.
Here's a good read on the subject from Motor Trend a couple years ago touching on the regulatory stuff and other factors that affect speedo indicated MPH.
https://www.roadandtrack.com/car-cul...ters-accurate/
2010 Volvo xc90 is 100 % accurate.
2001 GMC dually is 100 % accurate.
1999 996 C4 reads 4-5 mph high .
2002 Boxster S reads 4-5 mph high .
All on stock size wheels and tires . Accuracy was measured via Android phone GPS .
My 2003 996 C2 is 4-5 mph over at 80 mph. Seems to be about 5% +/-. When switched over to kph here in Canada, same, approximately 5% deviation happens. I say percentage, rather than a straight speed number, as it does seem (although I�ve not tracked it quantifiably) to change at lower speeds and get closer. This seems to also include new cars, as we just did a trip with two friends, one in a 2017 GTS and another in a 2023 T, all noting similar variances.
My Honda is within 1 kph accurate.
My 6TT reads 4mph high at indicated 75 mph, with 305/30 and 245/40.
My other 6TT (blue) reads 4mph high at indicated 75 mph with 295/35 & 225/40 which are stock sizes. With 315/35 and 245/40 it's spot on.
My cayenne reads spot on at all speeds on stock tire sizes.
My VW's read 3-5 mph high at 75 indicated. No digital display in the VW's, just read the needles.
I don�t usually go off topic but who remembers these? I wonder about the accuracy given its manufacturer. Although is doesn�t have any electrical components.
I've had a strange thing happen with my car. I've had it for over 13 years and it always read 3 MPH faster than the actual speed. I know that is by design for the above mentioned reasons. However, since about 2 years ago it displays the actual MPH as confirmed by GPS and radar.
We should be careful here about looking for precision. There are a lot of error sources.
Brand new 295/30R18 on my C4S have a circumference of 1992 mm. If I were to run off all 9/32 of tread, the outer circumference is now 1947 mm, or about 2.2% less. So if my Speedo was accurate with new tires at 70mph, the old tires will now read 71.6, or 2.2% faster. (So if it was 3mph fast before, it's now 4.6mph fast.)
My understanding from the article linked above was that sometimes even different manufacturers with the same tire sizes, can differ a little in outer circumference.
What width rim is the tire on? Is it stretched? That can change outer circumference.
GPS isn't perfect either. With positional error of about 16ft, and up to 32ft between two points used to calculate velocity, that's 70*(32/5280)=0.42mph error. Error can be worse if you are in a hilly or mountainous area, or in buildings were there may be multipath reflections.
And phones usually only update at about 1Hz (although I think they could do 10Hz if programmed for it?), so for any measurements, make sure your speed is constant on level terrain, and wait one second to check your GPS speed.
I may be wrong on some of my assumptions above specifically, but my overall point is that while we can say that our Porsche speedometer seems about 3mph fast, anything more specific is kind of a waste of time without rigorous data collection and error analysis.
This is exactly why ECE-R39 makes manufacturers read fast. That buffer accounts for unknown error on individual cars. They feel that the error determined by that equation is sufficient so that no car should ever read slower than it is actually going.
So if they rigorously calculated a potential error of about 3mph, I don't think we're going to guess our way to be much more precise than that.
My '03 Targa with Tiptronic and new 285/3018 rear tires reads 2-4 MPH higher, depending on speed. This seems consistent with the information reported above.
I found with most cars, that it's usually pretty accurate at city speeds, and the error margin increases with speed. If I remember correctly, on my old BMW E90 it could be programmed to either show the speed precisely or with the "error" (and at ~260km/h on the speedo, GPS displayed something about 245km/h - not a huge deal imo).
my 996 C4S - high by 2 mph
my 958 GTS - high by 3 mph
my 970 GTS - high by 3 mph (also noticed that the cruise is 1 mph than the set speed...set cruise at 79, speedo reads 80?!)