Mud Tires

Open data: every number, dated and sourced. Take it.

Open data

Every figure on Mud Tires comes from a manufacturer specification or a named retailer listing, dated, with the source shown. The tables behind the site are published here as CSV and JSON under a Creative Commons licence, for your own research, reporting or product. No signup, no API key, no rate limit.

  • 24 specification rows
  • 36 price readings
  • 4 warranty records
  • CC BY 4.0

Bottom line up frontby Bill Belcamino, who writes Mud Tires

Editorial assessment

Can I reuse Mud Tires’ data, and what is it actually good for?

Yes: every table is published as CSV and JSON under CC BY 4.0, with no signup and no key, as long as you credit Mud Tires and link back.

That is 24 specification rows (six mud-terrains in four sizes, every figure from one source read on one day, so a gap between rows is a gap between tires, not between databases), 36 monthly price readings for nine tracked listings at the same retailer, and the warranty each tire actually publishes (one of four does; none is mileage-based).

The most useful column is weight. It is the specification people underestimate most and the one retailers bury: in the same LT285/70R17 size, BFGoodrich KM3 lists 67.1 lb against 62.2 lb for Milestar Patagonia M/T-02, a 4.9 lb difference per corner. The price history is the second most useful, because nobody else publishes one for mud-terrains; in its first month two of the nine listings moved and both moved down. Keep the reading date next to any price you copy, and treat a single-source spec table as a single source: where it contradicts itself we say so rather than picking a side.

My read of the verified data on this page. Disagree or spot an error? Tell Bill.

The datasets

One page per dataset, each with the full table, how it was built, what it cannot tell you, the sources, and a citation line.

Licence and citation

These datasets are released under Creative Commons Attribution 4.0. You may copy, redistribute, transform and build on them, including commercially, as long as you credit Mud Tires and link back. The underlying specifications and prices are the manufacturers’ and retailers’ facts.

Mud Tires. Mud-terrain tire datasets. Retrieved 24 September 2026.
https://mudtires.org/data/

How the data is produced

Every row originates on a Mud Tires page where the records are maintained: the specification database, the price tracker and the warranty comparison. The datasets are generated from those pages, following the rules on the methodology page: manufacturer specifications first, retailer databases for price only, one source per table, and a note whenever a number cannot be verified. Nothing is estimated; where a figure is missing, the cell says so.

Prices are re-read monthly against the same listings. A reading that cannot be taken is recorded as missing, never carried forward from the previous month.

Known limits

  • One source can be wrong. The spec table deliberately uses a single source so rows are comparable; where that source contradicts itself, both versions are recorded (see what the spec sheets get wrong).
  • A price is one retailer, one day. Readings are the listed price at SimpleTire on the reading date, not a market average and not what you will pay after fitting.
  • Warranty rows record what was published. “None found” means none was published in the sources reviewed, not that no warranty exists.
  • Coverage is deliberate, not exhaustive. Six tires in four sizes, the ones the site compares in full; not every mud-terrain on sale.

Using this data in something public? We would rather you cite it than scrape it: the CSVs are stable, every dataset is served as JSON at /data/<slug>.json with open CORS, and the guide for AI tools is at /llms.txt.