datawebotRitchie Bros auction data: lots, bids and inspection reports
Ritchie Bros auction lot identifiers, equipment fields, inspection readings, bid and sale states, buyer fees, and terms on automated access and Auction Data reuse.
Ritchie Bros. is an auction marketplace for equipment lots
Ritchie Bros. publishes auction events and numbered equipment lots. The event establishes the sale location, dates, and format; each lot describes the asset or group offered within it. A manufacturer model can appear on multiple assets, so a model name alone is not a lot identifier or a transaction record.
Scroll to compare →
| Record layer | Fields to keep together | Interpretation limit |
|---|---|---|
| Auction event | Displayed event title or identifier, sale region, site/location, date range, format, and event source page. | Event dates and participating sites can change; keep them with the event and review date. |
| Auction lot | Lot number, event relationship, displayed category, item location, auction state, and closing date/time when shown. | A lot is the sale unit. Similar equipment models can belong to separate assets and lots. |
| Physical asset | Make, model, year, usage and specifications when stated, plus the detail-page relationship. | A manufacturer model is a product family, not proof that two lots are the same machine. |
Event, lot, item ID, and asset are separate identifiers
Ritchie Bros. event pages and item details expose more than one identity layer. Preserve the event-to-lot relationship and the separate item-page ID; do not substitute a model name for either. Serial numbers and VINs may appear in item or inspection areas, but this guide does not reproduce them.
Scroll to compare →
| Identifier | What it identifies | Boundary |
|---|---|---|
| Event identifier | The auction event or catalog context, with its site and scheduled dates. | An event can include more than one site, date, format, or category. |
| Lot number | The auction lot within its event; keep any group-lot relationship and displayed lot state. | Do not treat a lot number as a manufacturer SKU or a globally unique asset ID. |
| Item-page ID | The separate platform ID shown in the equipment detail page. | Retain it only with the source page and event/lot context; do not use it as the physical serial number. |
| Make/model/year | The manufacturer and model family and the year wording shown for that machine. | A year may be presented in a source-specific way; preserve its label and do not infer build or service date. |
Equipment fields depend on the category
Ritchie Bros. item pages expose category-specific specifications and usage labels. Keep the source wording, unit, equipment type, and page date with each field. A blank or absent value is not zero, and a field seen on one category should not be required on every lot.
Scroll to compare →
| Equipment group | Field groups that may appear | Comparison check |
|---|---|---|
| Earthmoving and material handling | Make/model/year, operating hours, lift or digging capacity, reach or dimensions, engine and hydraulic checks, configuration, and attachments. | Keep each rating, dimension, and unit with the exact machine type and inspected component. |
| Trucks and road equipment | Odometer or mileage, configuration/axles, engine or drivetrain information, condition notes, and title or registration statements when shown. | Keep mileage separate from hours, preserve miles versus kilometers, and attribute title wording to the item page. |
| Agricultural equipment and implements | Machine type, make/model/year, usage meter, capacity or working dimensions, configuration, and included attachments when stated. | A compatible or pictured attachment is not automatically included in the lot. |
| Multi-station machinery | Separate engine or station labels, such as lower/carrier and upper-engine hours, and the component each reading describes. | Do not add separate meter readings into one lifetime-use total. |
An inspection report is bounded evidence
A report can separate general appearance, feature notes, meter readings, and limited checks of individual systems. Ritchie Bros. item pages warn that the report scope is limited to what is expressly recorded; reported meter values reflect visual observations and are not guaranteed actual hours or mileage. Inspection coverage varies by item.
Scroll to compare →
| Report field | Preserve the distinction | Do not infer |
|---|---|---|
| Meter or odometer | Hour meter versus odometer, displayed value and unit, source label, reading status, and inspection date. | A reading that could not be obtained, an inoperable meter, or a missing field is not zero or verified lifetime usage. |
| Functional check | The exact component checked and the result recorded for that check. | A limited function check does not certify the whole machine, performance under load, or every operating mode. |
| Deficiency or additional reading | The report's own note and the component or meter it refers to, if the project has permission to use it. | Do not resolve conflicting meter or service-history statements by choosing one value without evidence. |
| Photos and video | Whether the report says visual material or an operating video is available. | Do not copy or republish Ritchie Bros. inspection photos, report pages, or item-specific descriptions. |
Bid, close, reserve, and sold states are different
Auction format and lot state determine what a bid label means. Ritchie Bros. documents both live and online timed formats, as well as reserved-auction outcomes. Preserve the event's displayed format and each lot's state instead of treating every closing bid as a completed sale.
Scroll to compare →
| State or mechanic | What it describes | Comparison rule |
|---|---|---|
| Live auction | The event uses an auctioneer and its own event schedule and lot sequence. | Do not apply timed-auction closing extensions to a live lot. |
| Timed Auction | Online bidding runs without an auctioneer; bids near the close can extend the lot's closing time. | Record the displayed close time and state at observation; a displayed countdown can change. |
| Grouped lots | Lots in a group share closing times; activity on one lot may extend the group's closing time. | Keep group membership explicit and do not assume one lot's result is another's. |
| Reserved outcome | If an event is reserved and the reserve is not met, the highest bid may not result in a sale. | A high bid, a closed lot, and a Sold state are different observations. |
| Displayed result | A source-labeled sold/result amount, if available in the relevant official service view. | Do not infer a transaction amount from a current bid, a closed event, or a Sold label alone. |
A winning bid is not the buyer's total cost
Ritchie Bros. says a transaction fee applies to each lot won and that fees vary by region and may vary by event. Taxes are additional; titled lots, extra services, and late removal can have separate charges. Use the effective schedule for the event and location rather than a static percentage.
Scroll to compare →
| Cost layer | Keep with the amount | Interpretation limit |
|---|---|---|
| Winning bid | Lot, event, currency, auction format, and source-labeled result state. | A bid amount is not the buyer's invoice total or a market-wide value. |
| Transaction fee | Fee schedule version, event region, lot, winning-bid basis, and applicable minimum or cap where stated. | Rates vary; this guide does not publish a universal fee amount. |
| Documentation and services | Titled/registered-item status and any event-specific documentation or optional service charge. | Do not assume every lot has the same documentation or service costs. |
| Tax and removal | Applicable tax context, removal deadline, location, and any stated storage charge. | Do not infer a delivered or after-tax total from the bid alone. |
The General User Terms limit automated access and Auction Data reuse
The General User Terms reviewed October 8, 2026 prohibit using a robot, spider, scraper, data-gathering or extraction tool, or other automated means to access, collect, copy, or record the Services. Section 2 defines Auction Data to include listings, descriptions, bids, selling prices, and values, then limits use to assisting a user's own bidding on similar items or sale of the user's own equipment through the Services. Other uses require prior express written consent.
Scroll to compare →
| Terms section | Posted boundary | How this guide treats it |
|---|---|---|
| Section 1.3(c) | Prohibits the listed automated means from accessing, collecting, copying, or recording the Services. | This page gives no collection steps, workarounds, or claim that an automated route is available. |
| Section 2 permitted uses | Limits Auction Data use to the stated bidding and sale decisions through the Services. | A public listing does not establish a right to build an external collection or dataset. |
| Section 2 restrictions | Without prior express written consent, restricts paid publication/distribution, derivative market analyses, securities use, and use in used-equipment pricing tools or dashboards. | Do not present Ritchie Bros. Auction Data as a third-party resale-price feed or valuation dataset. |
| Effective-date note | The page's date wording appears inconsistent between April 6 and April 18, 2026. | The clauses are attributed to the terms as reviewed October 8, 2026; the effective date is not resolved here. |
A robots file does not replace the posted terms
The Ritchie Bros. robots.txt copy reviewed October 8, 2026 lists paths disallowed for the wildcard crawler group, selected paths it allows, and four sitemap locations. These crawler directives do not replace the General User Terms’ restrictions on automated access and Auction Data use.
Scroll to compare →
| Evidence item | Review status | Boundary |
|---|---|---|
| Disallowed paths | In the copy reviewed October 8, 2026, the wildcard group lists /api/, /myaccount/, /watchlist/, /ar/, /rba-msapi/, /rba-api/ and /search* as disallowed. | Treat the listed paths as dated crawler rules; do not infer a data-use license from them. |
| Listed allowed paths | The wildcard group lists /cp/, /lp/, /services/, /buying/, /selling/, /heavy-equipment-auctions/, /timed-auction/ and /pdp/. | An Allow directive does not override the Terms’ automated-access or Auction Data limits. |
| Sitemap declarations | The file names CMS, search, PDP and location sitemap endpoints. | The sitemap contents were not reviewed; a sitemap declaration does not establish a complete inventory, API, or collection permission. |
| Posted terms | General User Terms Sections 1.3(c) and 2 address automated access and Auction Data use. | Recheck the terms for the intended use; a crawler path rule does not supply separate consent. |
Keep equipment records attributable and within their permitted use
For a buyer's own permitted evaluation or a separately authorized project, keep auction context and evidence attached to every equipment field. Ritchie Bros. restricts automated access and narrows Auction Data use, so this field map does not authorize collecting or republishing its content.
Scroll to compare →
| Record group | Fields to distinguish | Use boundary |
|---|---|---|
| Sale context | Event and region, event format, lot number, item-page ID relationship, and review date. | Use only within the source's posted terms or separate express written permission. |
| Asset and inspection | Category, source-labeled make/model/year, relevant specifications, meter type/value/unit/status, and component-specific report state. | Do not copy reports or photos; exclude serial/VIN values and private account or bidder data. |
| Bid and costs | Exact displayed bid/result label, currency and result basis, fee schedule effective date, and applicable charge categories. | Do not infer a sale price or build a third-party used-equipment pricing tool or dashboard from Auction Data. |
| Provenance and rights | Source page, observation/review date, and written permission or other applicable use context. | Keep any permitted internal evaluation separate from public market analyses and resale datasets. |
Content reviewed 2026-10-07.