The Dubai Land Department's 1 to 30 September filter returned 10,770 residential Sales rows worth AED 24,056,650,692.92 at 04:12:02 GST on 30 September 2026. This is a dated query capture, not a closed monthly total: 229 returned rows carry an INSTANCE_DATE of 31 August, and the latest returned timestamp is 29 September at 17:58:20.

The capture returned 10,770 residential Sales rows

The most useful comparison keeps every figure inside the same official response. DLD returned the registration labels Off-Plan and Ready; the publication calculated their shares, sums and medians from the saved rows.

Source: Dubai Land Department Real Estate Data, official response captured 30 September 2026 at 04:12:02 GST; sums, medians and shares calculated from the saved rows.

The neutral read: Off-Plan supplied more returned rows and a larger share of returned value. The median is the middle TRANS_VALUE in each group. It is not a like-for-like property price because the response mixes Unit, Building and Land records.

The earlier week-ending 24 September transaction pulse used a shorter filter window. Its population should not be added to this one because those rows already sit inside the wider query.

The input register fixes the population before the total

The saved request sets Sales and Residential, then leaves registration type, freehold status, area and property type open. It asks for 15,000 rows from offset 0, sorted by the returned transaction-date field.

Source: the official DLD transaction interface, its public transaction script and the saved response from the POST endpoint https://gateway.dubailand.gov.ae/open-data/transactions, all accessed 30 September 2026.

The returned INSTANCE_DATE range is 31 August 2026 at 15:16:32 to 29 September 2026 at 17:58:20. Exactly 229 rows carry a 31 August date even though the From input is 1 September. The report preserves those official response rows. It does not replace DLD's boundary with a publication-created calendar cut or infer the gateway rule behind the difference.

That boundary is why the title says September filter capture. It does not call AED 24,056,650,692.92 an immutable September total.

Unit, Building and Land are separate returned property types

DLD's property-type field divides the response into 9,442 Unit rows, 743 Building rows and 585 Land rows. The publication does not translate Unit into apartment, Building into villa, or Land into a named project.

Source: saved DLD response captured 30 September 2026; labels returned in PROP_TYPE_EN; all numeric columns calculated from the returned rows.

The neutral read: Unit rows account for 87.67% of count and 68.64% of returned value. Land has 5.43% of rows and 19.33% of value. Different record types and property mixes make the medians descriptive of this response, not a citywide home-price index.

The five AREA_EN labels with the largest row counts are shown without editorial renaming or identifier mapping.

Source: saved DLD response captured 30 September 2026; names copied from AREA_EN; ranking, shares, sums and medians calculated from all returned rows.

An area label is not a project, building or community marketing name. Business Bay carries the largest returned value within this five-label sample, while JUMEIRAH VILLAGE CIRCLE has the largest row count. Neither fact establishes a price ranking because each label contains a different mix of returned records.

Returned fields and publication calculations stay separate

DLD supplied the row fields, response timestamp and repeated total. The publication calculated the aggregate numbers and kept the raw response unchanged.

The response has 10,770 rows but 10,767 distinct TRANSACTION_NUMBER values. The article therefore reports rows, not 10,770 unique legal transactions. The public response does not establish why an identifier repeats, so no cause is assigned.

The calculated average row value is AED 2,233,672.30, using AED 24,056,650,692.92 divided by 10,770. The average and median describe returned row amounts. They are not valuation opinions and do not merge this transaction table with DLD's separate rent, project, valuation, land, unit, building, broker or developer tables.

The evidence bundle makes the capture repeatable

Reproducing this result means saving the input bytes, output bytes and calculation together. A later re-run answers a new as-of question because the registry population can change.

The broader DLD real-estate data source map keeps transaction, rent, project, valuation, land, unit, building, broker and developer routes separate. This capture uses only the transaction response.

FAQ, checked 30 September 2026

How can I check Dubai real estate transactions?+

Use the official DLD Real Estate Data service. Record the From and To dates, transaction type, usage and every open filter, then save the response timestamp with the result. The page was accessed 30 September 2026.

Is AED 24,056,650,692.92 the final September 2026 residential-sales total?+

No. It is the sum of the 10,770 rows returned at 04:12:02 GST on 30 September by the exact filter shown above. The official page publishes no formal revision boundary, and the returned date range includes 229 rows dated 31 August.

Why did a 1 to 30 September DLD filter return rows dated 31 August?+

The official response returned 229 such rows. This report preserves that boundary and does not infer a timezone, registration or gateway rule that the public response does not state.

Are 10,770 rows the same as 10,770 unique transactions?+

No. The capture contains 10,770 rows and 10,767 distinct returned TRANSACTION_NUMBER values. The report uses row language because the public response does not establish why some identifiers repeat.

What does Off-Plan mean in this table?+

It is DLD's returned IS_OFFPLAN_EN registration-type label. It is not treated here as a separate statement about construction progress, project completion or unit availability.