Dubai Property Market News: This Week's Transaction, Listing and Source Dates

TL;DR: Dubai weekly transaction and listing signals

This Dubai property market news update separates three different evidence clocks rather than presenting them as one market number:

• DLD registration clock: The current reporting reference is 17–22 August 2026. The calendar week of 17–23 August 2026 was still incomplete at the 22 August research cutoff, so it cannot be presented as a final weekly Dubai Land Department transaction result.
• Portal listing clock: On 22 August 2026, Bayut displayed 116,487 Dubai residential properties for sale, with displayed prices ranging from AED 211,000 to AED 600 million. Property Finder displayed 109,565 Dubai properties for sale with prices shown in AED. Both are portal asking-price observations, not completed-sale data.
• Developer availability clock: Ellington’s Everly Place availability snapshot was dated 17 August 2026. It showed nine available units, quoted prices from AED 2,051,828 to AED 5,150,828, and a quoted 70/30 payment plan.

The numbers should not be combined, ranked, or treated as competing versions of one market-wide inventory total. Each signal has a distinct source, date, and measurement basis. For broader context, readers can also visit the Dubai Property Market Report Hub.

The central rule: identify the clock before interpreting the signal

This week’s Dubai weekly transaction and listing signals do not share one timestamp or one definition. A registered record has a DLD reporting window. A property portal result is an asking-price inventory observation at the moment the page is accessed. A developer availability page is a project-level snapshot published or shown on its own date.

Treating those three records as if they describe the same event can create misleading conclusions. This article therefore labels each item by source and date before describing its meaning. It does not report a transaction count, transaction value, median price, yield, forecast, or market-performance conclusion, because no such official aggregate was retrieved and documented for this reporting run.

The reporting reference used here is 17–22 August 2026 for the current incomplete DLD period. No final result is assigned to the full 17–23 August 2026 calendar week. Portal observations are explicitly dated 22 August 2026, while the developer snapshot retains its own 17 August 2026 date.

Clock one: DLD registration reporting through 22 August

What the DLD source can support

Dubai Land Department’s Real Estate Data portal is the appropriate source for a reproducible registered-transaction series when the reporting period is defined. The portal supports date-range selection and downloadable results. A transaction report using this source should state both its selected date range and the transaction scope used in the output.

For this article, the only DLD-side reference is the incomplete current period of 17–22 August 2026. The term “transaction” is used solely for the registration-side output available through Dubai Land Department’s date-bounded data source. No count, value, price, transaction type total, or comparison with an earlier period is asserted here.

The reason is straightforward: at the 22 August 2026 research cutoff, the calendar week ending 23 August 2026 had not finished. Reporting 17–23 August as a completed week would imply that all dates in that window had already passed and been included in a final weekly result. They had not.

The source basis for this distinction is Dubai Land Department — Real Estate Data. When reviewing transaction-focused coverage, check whether the author identifies the exact DLD date range rather than simply calling a partial period “this week.” Readers looking for prior source-led coverage can review this Dubai real estate market update with DLD transactions.

How to label this week correctly

A careful label is: “DLD registration reporting period: 17–22 August 2026, partial through the 22 August cutoff.” That wording identifies the selected reporting window without claiming a finalized weekly total.

An inaccurate label would be: “DLD results for the week of 17–23 August 2026.” That framing treats an unfinished calendar week as closed. It also invites unsupported week-on-week calculations, which this source bundle does not provide.

This distinction is not a technicality. The date range is part of the definition of the signal. A reader cannot determine whether two DLD figures are comparable without knowing whether they cover the same start and end dates and whether both periods are complete.

Clock two: portal asking-price inventory observed on 22 August

Bayut’s observed asking-price results

Bayut’s Dubai sale-results page displayed 116,487 residential properties for sale when accessed on 22 August 2026. The displayed price range ran from AED 211,000 to AED 600 million. This is a portal asking-price inventory observation from that access date.

It is not a Dubai Land Department transaction count. It is not a closed-sale price series. It is not evidence that a property sold at the displayed price, and it is not a market-wide listing total. Availability, inventory, and displayed asking prices can change after the observation date.

The exact source is Bayut — Properties for Sale in Dubai. The useful interpretation is narrow: it documents what that portal’s Dubai sale-results page displayed on 22 August, including the displayed count and visible asking-price range.

Property Finder’s observed asking-price results

Property Finder’s Dubai sale-results page displayed 109,565 properties for sale with prices shown in AED when accessed on 22 August 2026. Like the Bayut observation, this is an asking-price portal signal, not registered-sale evidence or a citywide transaction total.

The exact source is Property Finder — Properties for Sale in Dubai. The figure should retain both its portal identity and its access date: Property Finder, 22 August 2026.

Why the portal figures must remain separate

The Bayut and Property Finder counts should not be added together, subtracted from one another, reconciled, or ranked. Their search inventories and filters are portal-specific. The two observations are useful as separately dated asking-price signals, but this research does not provide a like-for-like method for converting them into one combined Dubai listing count.

The displayed numbers also cannot establish a completed-sale price, a transaction volume, or a market direction. A portal asking price is being observed on a listing-search page; a DLD registration record belongs to a different source and reporting clock.

This source discipline is part of the AiGentsRealty methodology. It is especially important where a large portal number may appear more current than a dated registration series but does not measure the same thing.

Clock three: developer availability dated 17 August

Ellington’s official availability page provided a third type of record: a developer-level project snapshot. The Everly Place snapshot was dated 17 August 2026 and showed nine available units. Its quoted price range was AED 2,051,828 to AED 5,150,828, and it displayed a 70/30 payment plan.

The source is Ellington Properties — Project Availability. This is neither a DLD registration record nor a portal-wide asking-price inventory observation. It is an official developer availability snapshot for the named project on its stated date.

The snapshot should therefore be read carefully:

• “Nine available units” describes the availability shown in that snapshot.
• The AED figures are quoted project prices, not evidence of completed sale prices.
• “70/30” is the payment-plan notation displayed in the snapshot, not an independently verified entitlement for every buyer or every unit.
• Availability and quoted prices can change after 17 August 2026.

This is useful project-level information, but it is not a basis for calling any unit a “best deal.” The available research does not supply a reproducible comparison across unit type, area, size, condition, tenure, payment structure, and matching source timestamp.

Source and date map for this update

The table is intended to preserve the boundary between sources. It does not convert listing counts into transactions or project availability into a broader market result.

How to read the signals without creating unsupported conclusions

A useful sequence is to ask four questions.

1. What is being measured?

First, identify whether the number comes from DLD registration reporting, a portal sale-results page, or a developer availability page. The source itself determines the measurement basis. A DLD date-range output is the correct starting point for registered-transaction reporting; Bayut and Property Finder observations describe their respective asking-price search inventories; Ellington’s page describes the availability it showed for Everly Place.

2. What date does the number belong to?

Second, retain the source-specific date. This update has three: the partial DLD reference period of 17–22 August 2026, portal access on 22 August 2026, and the Ellington snapshot date of 17 August 2026. Dates are not interchangeable just because they occur in the same calendar week.

3. Is the period complete?

Third, check whether the stated reporting window has ended. The 17–23 August calendar week was incomplete at the 22 August cutoff. No final weekly DLD transaction conclusion should be drawn from this period, and no week-on-week movement should be calculated from it.

4. Can the values be compared directly?

Finally, do not assume that similarly formatted figures have the same scope. The Bayut and Property Finder counts are separate portal observations. The Ellington availability figure covers a named project snapshot. None should be merged into a transaction figure or used to infer a combined citywide supply number.

For a discussion of how short reporting windows can affect interpretation, see How to interpret short-term Dubai transaction volatility. That related reading does not change the source boundaries used in this update.

What this week’s evidence does and does not say

The evidence supports a date-labelled view of available signals. It supports reporting the two portal observations as asking-price results accessed on 22 August. It supports reporting the Everly Place availability snapshot as dated 17 August. It supports using DLD’s date-range data source for registered-transaction reporting and treating 17–23 August as incomplete at the 22 August cutoff.

It does not support a claim about total Dubai transactions for the week, transaction value, median prices, rental yields, buyer demand, supply growth, market direction, or a forecast. It also does not support a claim that one portal’s displayed inventory is larger, more complete, or more representative than the other’s.

The absence of a final DLD weekly aggregate in this update is intentional. A partial week should remain partial. A portal asking-price observation should remain an asking-price observation. A developer availability snapshot should remain a developer availability snapshot.

A practical checklist for the next Dubai market update

When the next source review is prepared, use the same order of operations:

1. Set the DLD reporting window and state its exact start and end date.
2. Confirm whether the calendar period is complete before describing it as a weekly result.
3. Record the portal access date beside every displayed inventory or asking-price figure.
4. Keep each portal’s figures separate rather than producing a combined listing number.
5. Record the developer page’s availability or publication date beside project-level quoted prices and payment-plan language.
6. Label prices according to their source: registered transaction data, portal asking prices, or developer quoted prices.

Readers who want continuing context can follow Dubai real estate market trends. For this specific update, however, the central takeaway remains the same: source and date are part of the data, not footnotes to be removed.

FAQs

Is 17–23 August 2026 a finalized DLD transaction week?

No. At the 22 August 2026 research cutoff, the 17–23 August calendar week was still in progress. This update therefore uses a partial 17–22 August reporting reference and does not publish a final weekly DLD transaction result. The source basis is Dubai Land Department — Real Estate Data.

What does Bayut’s 116,487 figure represent?

It represents the number of Dubai residential properties for sale displayed on Bayut’s sale-results page when accessed on 22 August 2026. It is a portal asking-price inventory observation, not a DLD transaction count, completed-sale total, or market-wide listing total. Source: Bayut — Properties for Sale in Dubai.

Can Bayut and Property Finder listing counts be combined?

No. The available research requires that the figures remain separate because their search inventories and filters are portal-specific. Bayut displayed 116,487 residential properties for sale, while Property Finder displayed 109,565 properties for sale, both observed on 22 August 2026. Neither number should be added, subtracted, or ranked against the other.

Are portal asking prices the same as registered sale prices?

No. The Bayut and Property Finder figures in this update are expressly asking-price portal observations. They are not DLD registered transaction data and are not closed-sale price series. The relevant sources are Bayut — Properties for Sale in Dubai and Property Finder — Properties for Sale in Dubai.

What does the Ellington Everly Place snapshot show?

The snapshot dated 17 August 2026 showed nine available units, quoted prices from AED 2,051,828 to AED 5,150,828, and a quoted 70/30 payment plan. It is an official developer availability snapshot, not evidence of completed sales or a DLD registration record. Source: Ellington Properties — Project Availability.

Why are source dates important in Dubai property market news?

The dates identify what each observation can mean. This article distinguishes a DLD reporting window through 22 August 2026, portal observations accessed on 22 August 2026, and a developer snapshot dated 17 August 2026. Keeping those clocks separate prevents an incomplete transaction week, a portal asking-price result, and project availability from being presented as one measure.