posted 2026-07-26 · auction.vin/blog/how-to-check-a-cars-auction-history-and-run-list-by-vin
How do I check a car's auction history and run-list presence by VIN?
Look up the VIN at auction.vin — run-list presence, sale history, and announcements, each line with source and timestamp, read before the block.
Look up the VIN at auction.vin and the lane record assembles from the record: whether the VIN sits on an upcoming run list and where in the run, its sale history across prior runs, and the announcements the lane will call at the block — each line carried with its source and its timestamp. Reading it before sale day means you hold what the block knows before the block says it, instead of learning the unit's story at announcement speed and the fee sheet after that. Register reads are free at every VIN, and what the record does not carry posts as EMPTY, never as silence.
That is the whole point of a lane record: to move the disclosures forward in time. On sale day the lane tells a unit's story in the order that favors the seller — the condition light, then the announcements, then the block's number, and the buy fee last — and by the time you've heard it, you're already bidding. The record inverts that sequence. The presence, the history, and the announcements are record lines before they are a speech, so you read them at your desk, one VIN at a time, and walk into the lane already knowing what it will call.
The three things the record carries
A run list is the roster of units scheduled to cross a lane on a given sale day, and "presence" is the first question a used-car manager or a buyer asks: is this VIN going to run, and where in the sequence? The record answers it with a dated line — on an upcoming run list, with the source and the timestamp of that entry — or, when the VIN is not on any list the record can see, as a typed EMPTY. It never fakes a yes. Absence is stated as absence, not left as a blank you have to interpret.
The second thing is sale history — the unit's prior runs, each as a dated event. A car that has crossed a block before carries that crossing on its record: sold, no-sale, or if-bid, with the date it happened. Where the record carries the block's number on a prior run, the hammer price sits in its slot; where it doesn't, the slot reads a dash. A dash is not a zero and not a guess — it is the record declining to state a figure it cannot source. That discipline is the difference between a record you can bid on and a listing you have to second-guess.
The third thing is announcements — the disclosed conditions the lane will call: title status, the condition light, the disclosures tied to arbitration. Each posts as its own line, sourced and timestamped, or typed EMPTY where the record carries nothing. Announcements are their own deep subject — what each one means for what you can send back after the sale — and the companion piece on reading announcements walks them line by line. Here it is enough to know they are on the record before the hammer, not sprung at it.
Look up, read, run
The door works in three moves, and it is honest about where it stops:
- Look up — a VIN at
auction.vin/{VIN}. The lane record assembles from the record; you don't fill a form, you read a page keyed to the seventeen characters. - Read — run-list presence, announcements, and sale history, each line carried with its source and its timestamp. Every dollar on the page fills its own slot: a slot without a sourced figure reads
$ —, never an estimate, so nothing on the record is inflated to look complete. - Run — the disposition decision hands to the wholesale door, and the rooftop works the unit — appraise, record, move — at dealers.vin. This door owns the record, not the decision.
That last move states a real boundary. No unit is consigned, run, or hammered at this address. The register reads; it does not transact. The gate that would let a lane door transact is open and named — dealer licensing and auction access, per the compliance checklist — and until it clears, every read here stays free and nothing here takes a fee. When you're ready to actually move metal, the disposition decision lives next door.
The number is free; precision is the ladder
The register read is the free base rung: anyone can look up a VIN and read the lane record with no account. It answers the question — is it running, what did it bring, what will it announce — from the record the door can see. The deepening step is the full history the block draws on. The lane announces a title brand or an odometer flag because the underlying record carries it, and that underlying record reads in full at vhr.vin — odometer, brand, and event history, the history the block announces, read before sale day. The register tells you what the lane will call; the report tells you why. The free face leads; the report is the step you take when the buy warrants the depth.
One honest limit worth stating plainly: the record shows what the record carries. A VIN with no prior lane events reads a page of EMPTY and dashes — not because the door is thin, but because there is nothing sourced to post, and posting a guess would be worse than posting nothing. Presence, history, and announcements fill as the lanes surface them; the record's promise is that every filled slot traces to a source and a timestamp, and every unfilled one says so.
Read the lane record for a unit at auction.vin — one VIN, presence, history, and announcements in hand before the block. The full history behind the announcements reads at vhr.vin; the rooftop's rails to work the unit live at dealers.vin.
The record, at its other addresses
- wholesale.vinDisposition: the unit runs to the wholesale door from the same record
- dealers.vinWork the unit: every dealer rail for any VIN at one address
- values.vinFive numbers with the auction band posted for any VIN
- vhr.vinThe history the block announces: any VIN, posted
- commerce.vinThe transaction layer: the whole deal settles as one order