Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Prices / Asking-price index

Off-plan asking-price index

How the prices developers advertise move, market by market, measured only on the same projects from one daily snapshot to the next. Every figure below is recomputed in your browser from the published changes.

Read this first. Our history starts on 28 October 2026, so this index covers a few days and rests on thin counts. It measures advertised asking prices, not what buyers pay. It is not a forecast and is never extended past the last snapshot.
…markets with an index
…same-project price pairs used
…actual price moves among them
…snapshots since 28 Oct 2026

All tracked markets

Every price move in this view, in percent

By market

Markets are listed when at least one step has five or more same-project pairs. Click a market to see its chain.

MarketBase dateIndex nowPairsMoves up / downLeft out

Official registered sales, for context

Where a government publishes its sales register openly, we show the monthly median next to the index. It is a different measure: it covers every unit sold, and the mix of units changes from month to month. It is never blended into the index.

How it is computed

  1. Observation. A project counts on a given day only if our research agent re-read its page that day and found a positive advertised "from" price with a currency. A value carried over from an earlier day is not an observation.
  2. Pair. The same project, observed on two consecutive snapshots, in the same currency. Projects that changed currency between the two are left out and counted.
  3. Jumps left out. A step of more than 25 percent up or down is left out and counted. In our data such jumps are nearly always a different unit type, a currency mix-up or a misread page, not a price change. We do not correct them.
  4. Step. The geometric mean of new price divided by old price over the kept pairs (a chained Jevons index). Unchanged prices count as no change. A step needs at least 5 pairs.
  5. Chain. The index starts at 100 on the market's base date and multiplies the steps since then. If a step is too thin, the chain is not bridged across it: the base moves to after the gap.

Limits: an advertised "from" price is the cheapest unit on offer, so it moves when that unit sells out as well as when a developer reprices. Prices are read from web pages by a language model and can be misread. Snapshots are not evenly spaced. Per-project amounts and names are not published, only percentage changes and counts, so projects stay anonymous.

Data: /data/price-index.json (CC BY 4.0), rebuilt every day after the research agent's run. Inputs and their SHA-256: …. Related: advertised prices versus registered sales, the database.

Protect my purchase