Property Data
Dubai property transactions and recorded sales data
Asking prices tell you what sellers hope for. Recorded transactions tell you what buyers paid. Transaction Intelligence is a searchable record of completed sales — the evidence layer underneath every other analysis on the platform.
Product preview
Records found
12,480
Median AED/sqft
1,640
Median price
AED1.85M
Off-plan share
58%
Recorded transactions
Most recent registered sales
| Date | Community | Building | Beds | Size (sqft) | AED/sqft | Value (AED) |
|---|---|---|---|---|---|---|
| 14 October 2026 | Dubai Marina | Marina Gate | 2 | 1,180 | 2,180 | 2,572,000 |
| 14 October 2026 | Business Bay | Canal Heights | 1 | 735 | 2,020 | 1,484,000 |
| 13 October 2026 | Jumeirah Village Circle | Belgravia Square | 2 | 1,065 | 1,190 | 1,267,000 |
| 13 October 2026 | Dubai Hills Estate | Golf Place | 4 | 4,120 | 1,480 | 6,098,000 |
| 12 October 2026 | Dubai Creek Harbour | Creek Rise | 3 | 1,560 | 2,240 | 3,494,000 |
| 12 October 2026 | Downtown Dubai | Burj Vista | 2 | 1,290 | 2,810 | 3,625,000 |
| 11 October 2026 | Arjan | Vincitore Palacio | 1 | 690 | 1,105 | 762,000 |
Key capabilities
Searchable sales records
Query recorded sales by date, community, building, property type, bedrooms and size. Each record carries its sale value and the derived AED/sqft, so you can move between absolute price and normalised price without leaving the table.
Filters that match how you think
Narrow to the segment you actually care about — three-bedroom apartments in one community over the last six months — rather than filtering a city-wide export after the fact.
Aggregate and record view together
Summary measures sit above the records that produce them. When a median looks wrong, the transactions that explain it are one glance away.
Off-plan and ready classification
Transactions are distinguished by type, because off-plan and ready-property sales respond to different drivers and mixing them produces a median that describes neither.
Business use cases
What people actually use this module for, rather than a list of what it contains.
- 1
An agent pricing an instruction
Pull the recorded sales in the same building and unit size over recent months to ground a pricing recommendation in evidence a client can check.
- 2
A valuer assembling evidence
Identify and export the transaction set relevant to a subject property as the factual basis for a professional opinion.
- 3
An investor verifying a claim
Check whether a quoted "market price" for a building is supported by what has actually been recorded there.
How the analysis works
- 1
Query the record set
Filters define which registered sale transactions are in scope.
- 2
Normalise for comparison
Price per square foot is derived from recorded price and recorded area so that differently sized units can be compared.
- 3
Check recency and completeness
Because of reporting lag, the most recent weeks are the least complete part of any transaction dataset.
Filters and metrics
The filters that define what a figure is computed from. Setting them before reading a number is the difference between an answer and a coincidence.
- Date range
- Community
- Building
- Property type
- Bedrooms
- Size
- Transaction type
Data limitations
- Recorded sale prices reflect registered transaction values and may not capture every commercial term agreed between parties.
- Reporting lag means recent periods are incomplete and revise upward over time.
- Recorded area definitions can vary; AED/sqft comparisons are most reliable within a consistent property type and location.
Metrics used on this page
- Transaction value
- The total recorded value of property sale transactions in a selected market, period and segment. It is a sum of recorded sale prices, not an estimate of market size or of the value of all property stock.
- Transaction volume
- The count of recorded sale transactions in a period. Volume answers "how much activity", while transaction value answers "how much money" — a market can rise in value while volume falls if larger properties trade.
- Price per square foot (AED/sqft)
- A recorded sale price divided by the property’s recorded area, expressed in AED per square foot. It allows properties of different sizes to be compared, but only compares fairly within a similar property type, location and condition.
- Asking price versus recorded sale price
- An asking price is what a seller advertises. A recorded sale price is what a completed transaction was registered at. The two can differ materially, and only the second is evidence of what the market paid.
- Reporting lag
- The delay between a transaction happening and appearing in available records. Because of lag, the most recent period in any dataset is usually incomplete and will revise upward as records arrive.
Full definitions and method: data methodology
Frequently asked questions
Filter the transaction records by community and building, then narrow by property type, bedrooms and size to find comparable units. The result is the set of recorded sales for that building, each with its date, recorded price and AED/sqft — which is what "transaction history" means in practice.
An advertised price is a seller’s asking position. A recorded price is the value a completed transaction was registered at, after negotiation. The gap between them varies by market conditions, which is precisely why recorded transactions are the more useful evidence.
Start exploring transaction intelligence with a free account
Start exploring the Dubai property market with PropertyMetric.
Start with a free account. No card required.