6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHWatch out for tis car/seller
Reported or suspected cause
car fax would show the mileage at some point
Suggestion or failed attempt
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
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 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
actually there are a few states that says that mileage or odometer is not necessary, anyway more than likely the car fax would show the mileage at some point.
Leading evidence: 'car fax would show the mileage at some point' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'car fax would show the mileage at some point' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Recommend everyone' (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 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.
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.
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
Someone just grabbed the picture and is using the ad to mine contact info.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
car fax would show the mileage at some point
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
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
actually there are a few states that says that mileage or odometer is not necessary, anyway more than likely the car fax would show the mileage at some point.
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.
6 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: 20261027T000231Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
So my good friend had a car almost the same as mine, 2000 C4 Cab, Ocean Blue with a grey interior (mine has a beige interior) but with higher mileage. He bought the car back in 2006 and moved to Washington state two years ago. The car had 144,000 miles and about a month ago he sold it for $14,000. He just found it on Facebook Market place stating it has only 72,000 miles, listed as a 99 with an asking price of $28,500.
He can tell it is his by the pictures and by the fact that it is the same license plate he sold it with (in Washington apparently cars are sold with the license plates). So it has had the mileage turned back! I asked him how they can do this as in Illinois you have to put the mileage on the title when you sell the car and this is shown on any new title.. This is not required in Washington on cars older than 20 years.
Not sure if this would show up with a Durametric or PWIS. He called the DMV out there and was told they won't get involved.
So be careful of this car and others, there are lots of scammers out there!
actually there are a few states that says that mileage or odometer is not necessary, anyway more than likely the car fax would show the mileage at some point. Unfortunately people would do all kind of stuff for money. Thanks for the heads up .
Always beware of the car flippers
There is something to be said about long time ownership and pride of ones car.
Thank you for your warning on the Cabriolet
I've experienced this with Facebook Marketplace before. With FB marketplace they allow you to use the terminology "Driven X miles". In order words, the odometer may say 150K miles, but technically the seller only drove it 50K of those miles. (see picture) But this allows sellers to lie or fudge about the actual mileage on the odometer. It's a cleaver way of pulling in click bate traffic. And yes, could very well be a scam. Always... buyer beware.
Had this happen to me, inquired about the car that said "Driven 50K miles". Ran a Carfax and found out the car had well over 100K miles. Ugh!
Here's the VIN on this car DHARN mentioned:
WP0CA2996YS650202
This is a source reference. Confirm exact model applicability in the original material.
