4COPART2017 Lexus RX 350
JTJBZMCA3H2022906
- Primary damage
- Front end
- Condition
- Runs and drives
- Title
- Salvage title
- Odometer
- 73,599 km · 45,732 mi
Sale status
Pure sale
Auction date: 14 Aug 2026 · TUCSON, AZ
Vehicle report
The archive contains 2 dated auction events and 1 full lot record for VIN 2T2BZMCA2HC089903, spanning 12 Aug 2026 – 14 Aug 2026. Latest full record: 14 Aug 2026 at COPART in CHICAGO SOUTH, IL, USA.
Report updated: 14 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.
COPART
Historical event
This report combines persisted auction records from COPART. 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
4COPARTJTJBZMCA3H2022906
Sale status
Pure sale
Auction date: 14 Aug 2026 · TUCSON, AZ
4COPART2T2ZZMCA5HC034554
Sale status
Minimum bid
Auction date: 14 Aug 2026 · VALLEJO, CA
4COPART2T2BZMCA5HC070875
Sale status
Minimum bid
Auction date: 14 Aug 2026 · NORTH BOSTON, MA
19IAAI2T2ZZMCA9HC063281
Sale status
Sold — timed auction
Final bid
US$12,600
Auction date: 13 Aug 2026 · HOUSTON, TX
4COPART2T2BZMCA6HC112406
Sale status
Minimum bid
Auction date: 12 Aug 2026 · JACKSONVILLE NORTH, FL
5IAAI2T2ZZMCA0HC063525
Sale status
Sold — timed auction
Final bid
US$12,500
Auction date: 12 Aug 2026 · LEXINGTON, SC
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 VIN2T2BZMCA2HC089903
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.