Source: Dubai Land Department open data via data.dubai, Dubai Open Data Licence (licence text). Independent analysis by WIZI Premium, not affiliated with or endorsed by the Dubai Land Department, any government entity, developer, management company or data provider.

Service charges (owners-association budgets)

Script: scripts/modules/service_charges.py · Public data: data/out/service_charges/ · Site data: site/data/service_charges.json

Source

Dubai Land Department (DLD) service charge index, published on data.dubai under the Dubai Open Data Licence and staged as table service_charges (169,109 rows, budget years 2017–2026). Each row is one line of an approved owners-association (OA) budget: budget year × property group × usage × service category → AED per sq ft per year. A property group is the DLD unit the budget is approved for: usually one building, sometimes a cluster, a shared area or a master-community zone.

Coverage grows sharply over time (property groups with a budget: 9 in 2017, 73 in 2018, about 1,000 in 2019, about 3,000 in 2025–2026). Years before 2017 are not in the open data. Treat 2017–2018 as sparse.

Definitions

Budget record = one property group × usage × budget year. Usage is the DLD usage label (Residential, Retail, Offices, Parking, Mixed, Stores, Hospitality, ...). The two DLD usage codes that are both labelled "Parking" are merged by label (no property group has both in the same year).

Total service charge (AED/sq ft/yr) = sum of the budget's service-category lines, where

Totals are rounded to 2 decimals (the source precision).

Top categories = the three largest positive added lines, as text.

Budget type (heuristic from the DLD property-group name):

Quality flag (budget kept in the building tables, excluded from all statistics):

Year-on-year change (yoy_pct) = total / total of the same property group and usage in the previous budget year − 1. In building_latest a second basis is allowed when the property group was re-registered under a new id (yoy_basis = 'name_link'): exactly one budget with the same normalised name, usage and master community exists in both the latest year and the year before. same_id means the same DLD property group id. When neither applies, YoY is empty.

Keys, unspecified projects and multiple budgets

Outputs (data/out/service_charges/, parquet + csv)

file grain content
building_year_usage property group × usage × year total, previous-year total, YoY %, top categories, budget type, quality flag, one column per category (anc_ = ancillary, not in total)
category_lines one row per DLD budget line category, AED/sq ft, role in total (added / subtracted / ancillary_excluded)
building_latest property group × usage latest budget year and total, YoY with basis, first year and its total, number of years
community_latest master community × usage, latest budget year (2026) number of building budgets, p25 / median / p75 / mean / min / max, median YoY of budgets present in both years
community_year master community × usage × year same statistics for every year
city_year usage × year same statistics, all of Dubai
category_composition_latest usage × category, latest year median and mean AED/sq ft of each category across budgets that have the line
same_name_budgets year × name × usage × community property groups sharing a name
coverage year counts of property groups, budgets, budgets without a project, flagged budgets, budgets by type

Statistics (community, city, composition) use building budgets only (budget_type = 'building'), exclude flagged budgets, and the "Unspecified" master community is left out of community tables (it stays in city tables). Each budget counts once, not weighted by size. The open data has no area per budget, so these are medians of buildings, not of square feet.

Privacy and licence rules applied

Caveats