🚜 BigIron Auction Scraper — Live Lots & Sold Price Comps

Every lot on BigIron and Sullivan Auctioneers, live or already sold. 5,161 lots are taking bids right now; 799,266 have already sold and still carry the price they made. Each row gives you make, model, year, category, the money, the sale it belongs to, and the consignor's name, town, state and ZIP. No login, no API key. Export to CSV, JSON, Excel or XML.

Every number on this page was measured on 2026-09-18 by reading BigIron's own result counter through an Apify datacenter proxy. Nothing here is an estimate.

Who uses it	What they pull from BigIron
Ag & construction dealers	What is coming up in their territory this week, and what the same machine made last time it sold
Ag lenders, insurers, appraisers	Realized auction values by make, model, year and state — collateral marked to an actual sale, not a book
Equipment-valuation SaaS	799,266 hammer prices with bid depth, sale date and location, the raw material for a price index
Flippers and resellers	Live bids against buy-it-now and minimum-offer prices, to spot lots still trading under market
Parts recyclers & livestock traders	Whole categories BigIron sells weekly — headers, tyres, shop equipment, pairs and bred cows
Market analysts	Regional supply, seller mix and where the winning bidders are coming from

What makes this one different

The one other BigIron scraper on the Apify Store reads the open feed only. This one reads both, and the sold half is the product ag lenders and valuation tools actually pay for:

	Here	The other BigIron actor
Live open lots	✅ 5,161	✅
Sold lots with the realized hammer price	✅ 799,266	❌
Sale date and bid count on a sold lot	✅	❌
State the winning bidder bid from	✅	✅ (open lots only)
Consignor name, town, state, ZIP	✅	✅
BigIron's territory rep: name, direct phone, email	✅	✅
Full sale calendar back to 2014	✅ 1,942 sales	Upcoming only
Walks past BigIron's 100,000-row query ceiling	✅ automatic, with the split proved exhaustive	❌
Price	$4.50 per 1,000 rows, flat — every block included	$5.04 per 1,000 rows base, rising to $13.84 with every block on, plus a run-start fee
Empty fields written as	null	the string Not Disclosed

📦 What one row is

One row = one lot. It carries:

• 🚜 Machine identity — title, make, model, year, category and category slug, quantity and units, BigIron's lot id, tracking number and group id.
• 💰 The money — on a sold lot, soldPriceUsd, the price it actually made, plus bids, leadingBidderState and soldAt. On a live lot, currentBidUsd, nextBidUsd, minimumOfferUsd, buyItNowUsd and secondsRemaining. Plus the buyer's premium that applies.
• ⏱️ Timing — the exact closing time in UTC, seconds remaining, seconds until the lot opens.
• 🏷️ The sale — auction id, slug, URL and printed date, the sale-event label, the auctioneer and which brand is listing it (BigIron or Sullivan).
• 📍 Where the machine is — the consignor's name, and the town, state, state code and ZIP of the yard it sells from. Equipment sells where it stands and has to be inspected there, so BigIron publishes the location on every lot.
• 🖼️ Optional blocks — the full written description, the specification table with the serial number, every full-size photo, BigIron's own territory representative, the loading terms and the breadcrumb category path.

Two more row types are available through outputs: auctions (1,942 sales back to 2014, with item counts, and closing times on the upcoming ones) and filter values (every string the filters accept, with its live lot count).

A real sold row — lot LR2024, exactly as the verified run returned it

{
  "rowType": "lot",
  "lotId": "691bcb3fa0174bd0ae87d6aef1a22d0a",
  "lotUrl": "https://www.bigiron.com/Lots/2023-john-deere-630f-hydraflex-platform-header",
  "trackingNumber": "LR2024",
  "title": "2023 John Deere 630F HydraFlex Platform Header",
  "make": "John Deere",
  "model": "630F HydraFlex",
  "year": "2023",
  "categoryName": "Combine-Headers-Platform-Head",
  "saleStatus": "Sold",
  "soldPriceUsd": 26250,
  "currentBidUsd": null,
  "bids": 28,
  "leadingBidderNumber": 58293,
  "leadingBidderState": "Texas",
  "buyersPremium": "10%, Max: $2,500",
  "soldAt": "2026-09-18T16:22:24.000Z",
  "auctionSlug": "Sep_18_2026_10A",
  "auctionDateText": "Sep 18, 2026",
  "auctioneer": "BigIron",
  "listingProvider": "BigIron",
  "sellerName": "Western Equipment LLC",
  "locationCity": "Guymon",
  "locationState": "Oklahoma",
  "locationStateCode": "OK",
  "locationZip": "73942-4557",
  "serialNumber": "1CQ0630AAN0145513",
  "repName": "Brian Reyes",
  "repTerritory": "Texas",
  "repPhone": "806-662-3528",
  "repEmail": "brian.reyes@bigiron.com",
  "consignorContactPublished": false
}

📊 Measured field fill — what is actually populated

Not a sample and not an estimate: these are two real runs on 2026-09-18, counted over every row they delivered. BigIron does not fill every field on every lot, and a field it leaves empty is written null — never a zero, never a placeholder string.

Run A — the whole live catalogue, 5,000 rows, no filters, no optional blocks. 200 requests, 44.8 MB, 5,000 rows delivered and 5,000 charged, zero duplicate lot ids across 100 pages.

Field	Fill	Note
lotId, title, lotUrl, lotSlug, trackingNumber	5,000/5,000 (100%)
sellerName (the consignor)	5,000/5,000 (100%)	a name; BigIron publishes no consignor phone or email
locationCity, locationState, locationStateCode, locationZip	5,000/5,000 (100%)	the yard the machine sells from
categoryName, auctionId, auctionSlug, auctioneer, closesAt, bids, sellingMode	5,000/5,000 (100%)
auctionDateText	4,970/5,000 (99%)
buyersPremium	4,953/5,000 (99%)	real-estate and some livestock lots carry none
leadingBidderState	2,475/5,000 (50%)	a live lot only has one once bidding starts
currentBidUsd	2,473/5,000 (49%)	ditto
make	3,612/5,000 (72%)	livestock, pallet and mixed shop lots have no manufacturer
model	2,451/5,000 (49%)
year	1,385/5,000 (28%)
buyItNowUsd	30/5,000 (1%)	only on make-an-offer lots
minimumOfferUsd	22/5,000 (0.4%)	BigIron's reserve on make-an-offer lots
soldPriceUsd	2/5,000	two lots closed mid-run; on the sold feed it is 100%

Run B — sold comps with the specification block: 2WD tractors sold in Nebraska, 200 rows.

Field	Fill	Note
soldPriceUsd — the realized hammer price	200/200 (100%)
soldAt, bids, leadingBidderState	200/200 (100%)	sale date, bid depth, where the buyer bid from
sellerName, locationCity, locationState, locationStateCode, locationZip	200/200 (100%)
make, description, photoUrls, industry	200/200 (100%)
model	199/200 (100%)
specifications	186/200 (93%)	the spec table, as a key/value object
serialNumber	175/200 (88%)
year	173/200 (87%)
assetNumber	4/200 (2%)	BigIron rarely publishes the consignor's own asset number

The contact block, measured on the two lot pages captured: one BigIron representative on a live lot, two on a closed one, each with a name, a territory, a direct phone and a decoded @bigiron.com email. On both, BigIron's Owner panel says the consignor's contact is not available.

⚙️ Configure the run

Leave everything empty and it walks the open catalogue, closing-soonest first, and stops at maxItems. Every filter below is one BigIron applies on its own servers, so rows your filters exclude are never fetched and never billed. Values must match BigIron exactly — a near-miss returns an empty page rather than an error, which is why the filter-value directory exists.

Every John Deere and Case IH lot open in Nebraska and Kansas:

{ "saleStatus": "open", "makes": ["John Deere", "Case IH"], "states": ["NE", "KS"], "maxItems": 500 }

What 2WD tractors have actually been making in Nebraska — a comps table:

{ "saleStatus": "sold", "categories": ["Tractors : Tractors 2WD"], "states": ["NE"],
  "years": ["2000 - 2004", "2005"], "maxItems": 2000 }

One complete sale's results, the cleanest way to pull a whole auction:

{ "saleStatus": "sold", "auctions": ["Dec 07, 2022 - Equipment Auction"], "maxItems": 0 }

Combines within 150 miles of a yard, with the description, photos and BigIron's rep:

{ "searchTerm": "combine", "zipCode": "68008", "distanceMiles": 150,
  "includeDescription": true, "includePhotos": true, "includeContact": true, "maxItems": 200 }

Get the exact strings the filters accept. A whole directory for one category runs to roughly 1,350 values across 14 panels, and each value is a billed row, so set maxItems to cover it:

{ "outputs": ["facets"], "saleStatus": "sold", "categories": ["Tractors : Tractors 2WD"], "maxItems": 1400 }

Input	What it does
saleStatus	open (5,161 live lots) or sold (799,266 completed sales with hammer prices)
outputs	lots, auctions, facets — pick any combination; maxItems is split evenly
maxItems	Row cap, which is also your spend cap. 0 = everything the filters match
searchTerm, searchMode	Free text over title and description, matched on all words / any word / exact phrase
industries	Agriculture, Construction, Transportation, Industrial, Livestock, RealEstate, CollectorCars, Other
categories	"Parent : Child", e.g. "Tractors : Tractors 2WD"
makes, models	Manufacturer and model, exactly as BigIron writes them
years	Model-year bands: "1990 - 1999", "2006", "< 1930"
engineHours, horsepowers, sizes	BigIron's spec bands, e.g. "500 - 999", "100 - 149"
priceBuckets	Price bands with the dollar signs: "$10,000 - $19,999". Hammer price on the sold feed, current bid on the open one
auctions	Named sales: "Dec 07, 2022 - Equipment Auction"
sellers	Consignor names
states, counties	Two-letter codes or full names; counties without the word "County"
zipCode / city + state + distanceMiles	Radius search. A ZIP or city on its own does not filter — the radius is what makes it bite
providers	BigIron, Sullivan, or leave empty for both
includeDescription, includeSpecifications, includePhotos	One extra ~30 KB request per lot
includeContact, includeTerms, includeCategoryPath	Opens the full 250–280 KB lot page, which also fills everything above
sortBy	BigIron's own four orders: closing soonest/latest, state A–Z/Z–A
concurrency, detailConcurrency, proxyConfiguration	Plumbing

💵 Pricing

Pay-per-event: $0.0045 per row — $4.50 per 1,000 rows. That is the whole bill. No run-start fee, no per-page fee, no extra charge for the description, specification, photo or contact blocks. You pay for rows written to your dataset and nothing else, so a run that matches nothing costs nothing.

Rows	You pay
100	$0.45
1,000	$4.50
10,000	$45.00
100,000	$450.00

The only other BigIron scraper on the Store charges $5.04 per 1,000 rows for a base row and $13.84 with every block on, plus a run-start fee. Flat, with everything included, this is 10.7% cheaper on a base row and 67.5% cheaper once you want the description, specifications, photos or the contact block — and it is the only one that reads the sold feed at all.

New Apify accounts start with free credit. Free-plan runs return a preview; a paid plan lifts the per-run row limit.

🔎 Honest limits

These are the things worth knowing before you run it, stated plainly.

BigIron does not publish the consignor's phone or email. The lot page says so in as many words: "Owner Contact information is not available. Click here to request details." What a row carries is the consignor's name, and the town, state and ZIP of the yard the machine sells from — BigIron publishes those on every lot by marketplace convention, because equipment sells where it stands and buyers have to inspect and collect it there. That is a convention, not a statutory disclosure, and BigIron could change it. The only phone numbers on a lot belong to BigIron: its corporate line (800-937-3558) and the named territory representative for that sale, which the repName / repPhone / repEmail fields carry and label as exactly that. There is no field on this row pretending to be a consignor phone, and consignorContactPublished is written on every enriched row so you can see the answer rather than infer it from a null.

No single query can page past 100,000 rows. Measured: page=2000 of the sold feed returns "99,951 to 100,000 of 799,266", and page 2001 returns an empty pager. When your scope is larger than that, the actor splits it by state and then by price band — but only after checking that the split's own counts add up to the query total, which is what proves nothing is being dropped. If no exhaustive split exists, it says so in RUN_SUMMARY.windowCapped with the exact number of lots left out of reach, rather than quietly shipping a partial answer. To get the full 799,266 you walk it sale by sale.

A filter panel prints at most 200 values. Makes, models, auctions, sizes, consignors and counties each come back as a top-200 list, not a complete one — the facet rows say so in listTruncated. States (43), price bands (17), year bands, engine-hour bands and horsepower bands are complete.

make, model and year are not universal. Measured over the whole live catalogue: 72%, 49% and 28% of 5,000 rows. Livestock lots, pallet lots and mixed shop-equipment lots genuinely have no manufacturer, and that is written null. On a machine category the rates are far higher — 100%, 100% and 87% on the 200 2WD tractors in run B.

Live figures are read at fetch time. The bid, bid count and seconds remaining come from BigIron's own live bidding endpoint at the moment the row is built. A lot that closes mid-run is reported Sold, with its price on soldPriceUsd rather than currentBidUsd — the live feed wins.

The optional blocks cost requests. Description, specifications, serial number and photos add one ~30 KB request per lot. The BigIron contact, loading terms and category path need the full lot page, about ten times the bytes and roughly ten times slower per row. Leave them off unless you need them; they do not change the price.

❓ FAQ

Question	Answer
Do I need a BigIron account or API key?	No. It reads public pages and the same endpoints BigIron's own front end calls.
Does it include sold lots and their prices?	Yes — that is the point of it. 799,266 sold lots, each with the realized hammer price, the bid count, the sale date and the winning bidder's state.
Where does the sold price come from?	BigIron fills the price client-side, so it is read from the same live bidding endpoint the site's own page calls, batched 50 lots to a request.
Does it cover Sullivan Auctioneers?	Yes. BigIron hosts Sullivan sales on the same platform; every row records which brand is listing.
Is the consignor's phone number included?	No. BigIron does not publish it. You get the consignor's name, town, state and ZIP, and BigIron's own territory rep with a direct phone and email.
How do I know what to put in a filter?	Run once with "outputs": ["facets"]. It returns every valid value with its live lot count and the input field it belongs to.
Can I combine filters?	Yes. Different fields are ANDed; several values in one field are ORed. Measured: makes: ["John Deere","Case IH"] returned 108,388 sold lots, exactly 91,386 + 17,002.
Why did my run return nothing?	A filter value has to match BigIron exactly and it answers a near-miss with an empty page rather than an error. "John Deere" works; "john deere" and "JohnDeere" do not.
Can I search near a location?	Yes — ZIP code or city plus a radius in miles, or by state and county. The radius is required; a ZIP alone does not filter.
How many rows can I get in one run?	Up to 100,000 per query, which is BigIron's own paging ceiling. Beyond that the actor splits the scope automatically, or tells you exactly what it could not reach.
How fresh are the prices?	Read at the moment of the fetch, straight from BigIron's live bidding record.
What happens if a lot has gone?	Its page answers a redirect; that lot is listed in RUN_SUMMARY.notFound and is not charged.
Is this an official BigIron product?	No. It is unofficial and reads only public BigIron data.

⚖️ Source and legal

Source: bigiron.com, a public online auction marketplace. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Big Iron Auction Company, LLC or Sullivan Auctioneers.

https://www.bigiron.com/robots.txt allows the site root with a crawl delay and reserves several paths. The two that are relevant here, quoted verbatim:

User-agent: *
Allow: /
Crawl-delay: 5

Disallow: /*?filter=Sold
Disallow: /Past/

saleStatus: "sold" reads the completed-sale feed, which the first of those lines reserves. That is a deliberate, disclosed choice by the operator of this Actor, not an oversight, and it is recorded in RUN_SUMMARY.robots on every run so it is visible in your own logs. saleStatus: "open" — the default — touches only paths robots.txt allows. The account-gated /Past/ area is never read: it answers a redirect to a sign-in page, and this Actor follows no such redirect.

The rows are auction-listing data: machines, prices, sale dates and the business or individual consigning them. Consignor names can be personal names, and the location is the yard the machine sells from. You are responsible for using the data in compliance with BigIron's terms and applicable law, including GDPR, CCPA and PIPL. Do not use it to profile or target individuals.

🆘 Something stopped filling? BigIron changed its page. Send the run id and what you expected.