Reading the data

How to Read Dubai Land Department Sales Data (Without Getting Misled)

Every residential sale in Dubai is a matter of public record. The Dubai Land Department (DLD) registers each transaction and publishes the register as open data, which means the price a flat two doors down actually sold for is not a secret, an estimate, or an agent's opinion. It's a filed fact.

The catch is that the raw register is genuinely hard to read. In its native form it repeats each transaction several times, mixes financing events and gift transfers in with real sales, includes offices and land plots alongside homes, records locations under cadastral zone names nobody searches for, and carries the occasional 22-square-foot "villa." Read carelessly, it will mislead you as easily as it informs you.

This guide is about reading it well: what a transaction actually is, which numbers mean what, and the specific misreadings that trip people up. KhaleejKeys does this filtering for you, but the reasoning below is worth understanding whether you use our search or the raw file.

First: not every "transaction" is a sale

The DLD groups every registration into one of three types (Sales, Mortgages, and Gifts), and only the first is a price you can trust as market evidence.

The misreading: treating "number of transactions" as "number of sales." KhaleejKeys keeps only genuine Sales, so a count here is a count of arm's-length purchases, nothing else.

The big one: ready vs off-plan

This is the single most important distinction in Dubai property data, and the one most casual analyses get wrong.

These are two different markets with two different price levels, buyer profiles, and risk profiles. Blend them and your "average price" is a meaningless midpoint between a developer's launch price list and the resale market. KhaleejKeys is a ready-market product (off-plan is excluded by design), so the prices you see are what real, standing homes actually traded for.

The misreading: comparing an off-plan launch price to a ready-market average and concluding a community is "cheap" or "overpriced." You're comparing two different things.

Price per square foot is the honest comparator (with three caveats)

Absolute prices tell you little on their own: a 2,500 sqft villa and a 500 sqft studio aren't comparable. Price per square foot (AED/sqft) normalises for size and is the fairest way to compare like with like. But respect its limits:

  1. Unit mix moves the average. A community's average AED/sqft reflects what happened to sell that period. A month heavy on small, high-per-sqft studios will read higher than a month of large villas, even with no real price change. Look at the mix, not just the headline.
  2. Small samples are noise, not signal. A "27% jump" computed off three sales is statistical noise. It's why KhaleejKeys suppresses percentage moves below a 10-sale floor and labels them "limited data" rather than dressing up randomness as a trend.
  3. Per-sqft says nothing about quality. Floor, view, condition, and finish all move price and none are in the register. Two identical-on-paper units can trade 20% apart for reasons the data can't see.

The misreading: reacting to a big percentage move without checking how many sales it's built on, or comparing two communities' averages when one is mostly villas and the other mostly apartments.

Locations aren't named the way you search

DLD records locations as cadastral zone names ("Marsa Dubai," "Al Hebiah Fourth," "Al Thanyah Fifth"), not the market names people actually use ("Dubai Marina," "Dubai Sports City," "JLT"). One zone can also contain several distinct communities. Mapping raw zones to the names buyers recognise is careful, error-prone work; done wrong, a search for "Dubai Marina" quietly misses half its sales.

The misreading: searching a raw zone name and trusting an empty or partial result. On KhaleejKeys every sale is mapped to a consistent community name, and anything that can't be mapped confidently is flagged, never silently guessed.

What the register does not tell you

Reading the data well is also knowing where it goes quiet. The public register does not contain:

The misreading: inferring something the register can't support. If a figure can't be traced to a registered sale, treat it as opinion.

Sanity bands catch the impossible rows

Even genuine sales sometimes carry data-entry errors: a 22-sqft "villa," a 340-million-dirham one-bed. Left in, a single fat-fingered row can wreck a community's average. Sensible reading applies bounds: positive, plausible sizes; a price-per-sqft band wide enough to keep genuine ultra-prime (Dubai's top honest sales run ~16,000 to 18,000/sqft) but tight enough to cut errors.

The misreading: taking an outlier at face value. One improbable number is far more likely an error than a discovery.

What's in scope, at a glance

Included Excluded
Ready & secondary-market sales Off-plan sales
Apartments, villas, townhouses Gift & nominal transfers
Named Dubai communities Mortgages / financing events, land plots, commercial units

The principle underneath all of this: if the public register can't support a figure, show nothing rather than something invented. That honesty is the product.

How to sanity-check any number you see here

Good data invites checking. Every figure on KhaleejKeys traces back to registered sales you can inspect: start from a headline, open the underlying transactions, and confirm it for yourself. The full rule-by-rule pipeline (and how to reproduce our dataset from the same public file) is on the methodology page; the FAQ covers what's in and out of scope.

Search the transaction register

Filter genuine, ready-market DLD sales by community, size and price. Free, every figure traceable to a registered sale.

Search transactions →

Read this way (knowing what's a sale, what's ready, what per-sqft can and can't tell you, and where the register stays silent), Dubai's transaction data stops being a wall of numbers and becomes one of the most honest tools you have for deciding what a home is actually worth.

No saved transactions yet.
Tap the bookmark icon on any row to save it.