4COPART2017 Tesla Model 3 Standard
5YJ3E1EA6HF000569
- Primary damage
- Front end
- Condition
- Enhanced condition report
- Title
- Salvage title
- Odometer
- 246,085 km · 152,910 mi
Sale status
Pure sale
Auction date: 7 Aug 2026 · SAN DIEGO, CA
Vehicle report
The archive contains 1 dated auction event and 1 full lot record for VIN 5YJ3E1EA0HF001832, spanning 6 Aug 2026 – 6 Aug 2026. Primary full record: IAAI in HUDSON, FL, USA.
Report updated: 9 Aug 2026
If you own this vehicle, or can otherwise show a connection to this VIN, you can request that its auction records be withheld from public view.

Decoded from the VIN structure itself. This describes the vehicle as built, and says nothing about its auction history.
Each row is a unique dated event reported by an auction source. A full lot link appears only when the archive has a standalone lot record for that event.
IAAI
Historical event
This report combines persisted auction records from IAAI. Values describe what the auction sources reported at each recorded date; they are not an independent inspection or a guarantee that no other history exists.
How this report is compiled
4COPART5YJ3E1EA6HF000569
Sale status
Pure sale
Auction date: 7 Aug 2026 · SAN DIEGO, CA
4COPART5YJ3E1EA3HF000478
Sale status
Pure sale
Auction date: 6 Aug 2026 · SAN BERNARDINO, CA
4COPART5YJ3E1EA6HF000068
Sale status
Sold
Final bid
US$3,600
Auction date: 28 Jul 2026 · SAN JOSE, CA
5IAAI5YJ3E1EA1HF001029
Sale status
Sold — buy now
Final bid
US$3,500
Auction date: 24 Jul 2026 · COLUMBUS, OH
4COPART5YJ3E1EA2HF002223
Sale status
Sold
Final bid
US$9,500
Auction date: 17 Jul 2026 · SPANAWAY, WA
4COPART5YJ3E1EAXHF001224
Sale status
Sold
Final bid
US$4,500
Auction date: 16 Jul 2026 · RANCHO CUCAMONGA, CA
If you own this vehicle, or can otherwise show a connection to this VIN, you can request that its auction records be withheld from public view.
Request removal of this VIN5YJ3E1EA0HF001832
Submitting opens a request. Each one is reviewed by a person, and the decision and its reasoning are recorded. Approved requests hide records from public pages; they do not erase the underlying data.