Take the data with you

Every filter you set anywhere on this site narrows the export too, and the download carries the derived columns as well as the raw ones. That is deliberate: almost nothing in this table is stored as the type it represents — the nightly rate is a sentence, the capacity is prose, the stay type and the city share a column — so an export of raw fields alone would leave every consumer to re-derive the same fifteen expressions and to hit the same traps.

Scrape

—

Match your filters

—

listings, deduplicated

This download

1,000

cap 25,000

Columns

default set

Available

—

raw and derived

Build your download

Format, row count, and columns

Format

Rows

Download

Download CSV

Columns

Derived columns are computed by the same SQL the charts use, so a number here and the same number on a chart cannot drift

The comparison export

One row per listing seen in both scrapes, with what changed

Download CSV

→

Sorted so the biggest movers survive the 25,000-row cap

This file does not exist anywhere else on the site, and it cannot be reconstructed from two single-snapshot downloads without redoing the id match and re-deriving every delta — including the two traps already handled here: review counts occasionally tick down and are clamped at zero, and badge is deliberately absent because its fill rate differs so much between crawls that a delta would read as 48% of listings losing a badge in ten days. Not streamed like the export above, because the matched set only exists once both sides are in memory and joined.

Preview

The first rows your current filters and columns produce

Data dictionary

What each column is, and which of them had to be parsed out of prose

Two columns from the source table are missing on purpose: checkin and checkout are empty strings on every row of every snapshot, so nothing derives from them and shipping them would only suggest they carry something. The stay dates behind a quoted rate are simply not in this data.