Spain Property Price Stats – Pisos.com prices by province

Median asking price, price per m² and size of homes for sale and to rent on Pisos.com, in each of Spain's 52 provinces and by number of bedrooms, with the number of listings behind each figure. Name one province (or a comarca or town as Pisos.com writes it) to look at it in depth.

Example

Region	Sale / rent	Listings	Median asking price	Median price per m²	Median size
Madrid	sale	9	€292,000	€5,072	75 m²
Barcelona	sale	9	€430,000	€5,303	99 m²
Madrid	rent	9	€1,800	€21.20	87 m²

Default input, run on 22 October 2026: 988 listings read in 1.9 minutes, 261 aggregate rows; at $1.50 per 1,000 listings read the run cost $1.48.

What you get, and what you don't

• Counts, not listings. The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts, no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
• List pages only. The run reads the site's public search-result pages, paced as the site's own Actor in this catalogue is (one request every 2 seconds), and never opens a listing's own page.
• A sample of the newest listings. The site lists newest first; the run counts up to maxListings of them. The summary row says how many were read and, where the site shows it, the site's own total.
• Medians need 5 values. A median is shown only where at least 5 listings have the value; otherwise it is empty.
• The last row of every run is a summary per site: listings read, the site's own total where shown, whether the run stopped at maxListings, and any warning (an unknown place, a blocked page).

Input

Field	What it does
maxListings	Listings to read and count at most (default 1,000, up to 10,000), shared evenly across the places and sale / rent searched.
transaction	sale (default), rent or both.
region	One place only (see below). Empty: every place listed below.

Example: {"region": "Málaga", "transaction": "sale", "maxListings": 3000}. An input the run cannot use (a place the site does not know) ends SUCCEEDED with no rows and the reason in the status message and the run report (RUN_REPORT).

Output

Field	Meaning
level	region (one row per place and sale / rent), region_rooms (per place, sale / rent and bedrooms) or summary.
date	Day of the run (UTC).
source	The site counted.
region	The place searched.
transaction	sale or rent.
rooms	Bedrooms: 0 (studio), 1, 2, 3, 4+, unknown; all on region rows.
listings	Listings read in this group.
median_asking_price	Median asking price (rent: per month); empty below 5 listings.
median_price_per_m2	Median of price / living area; empty below 5 listings with an area.
median_size_m2	Median living area.
currency	EUR.

How the counts are made

region is the province (or place) searched on Pisos.com, as the site files the listing. With no region the run reads every province for the transaction asked (sale by default; both adds rent), sharing maxListings evenly: with the default 1,000 that is about 19 listings per province (about 9 per province and type with both), enough for a first look; raise maxListings (up to 10,000) or name one province for firmer medians.

Prices are the asking prices shown (rent per month). Price per m² is price divided by the living area shown; listings without an area count in listings but not in the m² medians.

Pricing

$1.50 per 1,000 listings read (event listing-analyzed), no start fee. The aggregate rows themselves are free: a default run reads up to 1,000 listings and costs at most $1.50. Set a maximum charge per run in the run options to cap it.

Good to know

• The data is what Pisos.com shows on its public list pages on the day of the run.
• Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its date.
• Questions or a missing region: open an issue on this Actor.