Data Sources

Where our data comes from

These are key sources used by the product areas below—not a claim that every signal comes directly from an official dataset. Each entry states its source, coverage, method, limitations, update method, and lineage review date.

The date below records when this lineage was reviewed. We do not label pipeline runs as source freshness because a successful run can reuse an older upstream release.

Lineage reviewed as of 2026-08-31

How ChatHome Today is measured

ChatHome Today separates stable coverage facts from measured Greater Region marketplace activity. Missing, delayed or warming-up measurements are labelled instead of hidden or replaced with zero.

new homes: New homes are eligible Greater Region listings first created during the current Luxembourg calendar day.
updated today: Homes updated is the number of distinct eligible Greater Region homes with a detail, price or status event today. Price and status changes are subsets, not extra additions.
removed from market: Removed from market counts a transition detected today from a publicly visible active listing to terminal off-market. The timestamp is when ChatHome detected the transition, not necessarily when the transaction completed.
active ads withheld from search: Withheld ads are active Greater Region ads excluded from public search by the visibility and data-quality rules.

Each figure carries its own scope and time window. “Today” means Europe/Luxembourg from local midnight to the displayed measurement time.

Property listings

Agency and public-register records are normalised into listing records and deduplicated where matching confidence is sufficient.

Original agency listing page
Dataset / API identifier: listing.sourceUrl
Source type: Agency sourceUpdate method: Updated when the source publishes
Source URL varies by listing
Clicpublic public auctions
Dataset / API identifier: clicpublic
Source type: Official public dataUpdate method: Scheduled import
Chambre des Notaires — adjudications
Dataset / API identifier: notariat-auction-api
Source type: Official public dataUpdate method: Scheduled import
BusinessTransfer listings
Dataset / API identifier: businesstransfer
Source type: Public websiteUpdate method: Scheduled import

Source details

Coverage: Publicly accessible agency pages and named public registers; coverage varies with source access.
Method: Records are normalised and deduplicated when matching confidence is sufficient.
Known limitations: Source pages can be stale or inaccessible, and duplicates may remain.

Prices & market value

Selected official statistics support commune benchmarks and price-comparison signals.

Observatoire de l’Habitat — commune asking rents
Dataset / API identifier: reference edition lu_asking_rents · rolling 12-month mean
Source type: Official public dataUpdate method: Scheduled import
Observatoire de l’Habitat — recorded apartment sales by commune
Dataset / API identifier: reference edition lu_apartment_sale_prices · rolling 12-month mean
Source type: Official public dataUpdate method: Scheduled import

Source details

Coverage: Selected commune-level official statistics and named price datasets.
Method: Used for selected benchmarks and price-comparison signals.
Known limitations: Not every valuation uses these datasets; asking prices are not transaction prices.

Maps, zoning & risk

Official map layers support zoning and risk context where exact coordinates and the relevant layer are available.

Luxembourg Geoportail OGC API Features
Dataset / API identifier: flood · noise · cadastral · nature · heritage layers
Source type: Official public dataUpdate method: Scheduled snapshot
data.public.lu — communal PAG datasets
Dataset / API identifier: CKAN tag: pag
Source type: Official public dataUpdate method: Scheduled import

Source details

Coverage: Layer-specific coverage for Luxembourg; property-level checks require exact coordinates.
Method: Coordinates are matched against the relevant published map layer.
Known limitations: Publication dates and geographic coverage vary by layer.

Demographics & safety

Selected public-statistics datasets support commune context.

STATEC LUSTAT — population by commune
Dataset / API identifier: LU1:DF_X021(1.1) · annual population
Source type: Official public dataUpdate method: Scheduled import
Ministère des Affaires intérieures — 2024 crime by police region (answer to parliamentary question 2205)
Dataset / API identifier: QP 2205 (signed 2025-05-23)
Source type: Official public dataUpdate method: Manually verified import

Source details

Coverage: Selected public statistics by commune or other published geography.
Method: Imported and aggregated for commune context and derived indicators.
Known limitations: Reference year and geographic granularity vary; derived indicators must disclose any fallback.

Schools

School context comes from the dataset named on each feature.

OpenStreetMap contributors — childcare and family activities
Dataset / API identifier: luxembourg_parent_places.json:osmSource / poi_places
Source type: Community aggregatorUpdate method: Manually verified import

Source details

Coverage: Feature-specific school coverage; discovery counts use a static reference dataset.
Method: The consuming feature identifies whether it uses reference or imported ministry data.
Known limitations: Reference and imported datasets have different coverage and refresh paths.

Transport & commute

Timetables, precomputed profiles, and on-demand route estimates are separate inputs.

Administration des transports publics — GTFS
Dataset / API identifier: dataset 5a2a58b9111e9b7f34fc6606
Source type: Official public dataUpdate method: Scheduled snapshot
Mobiliteit.lu HAFAS departure API
Dataset / API identifier: ATP OpenAPI · departureBoard
Source type: Official public dataUpdate method: Scheduled snapshot
Self-hosted Valhalla and OpenTripPlanner routing
Dataset / API identifier: valhalla + open-trip-planner
Source type: Public websiteUpdate method: Scheduled snapshot

Source details

Coverage: Coverage varies across live lookups, timetable feeds, and precomputed profiles.
Method: Request-time routes, published timetables, and scheduled snapshots are kept separate.
Known limitations: A live lookup does not make precomputed profiles or timetables real-time.

Mortgages & finance

Published mortgage offers are sampled from the named providers.

BCL / ECB — housing-loan averages
Dataset / API identifier: lu_housing_loan_rates
Source type: Official public dataUpdate method: Scheduled import
BIL — published mortgage example
Dataset / API identifier: lu_bank_mortgage_examples:bil
Source type: Public websiteUpdate method: Scheduled import
BGL BNP Paribas — published mortgage example
Dataset / API identifier: lu_bank_mortgage_examples:bgl
Source type: Public websiteUpdate method: Scheduled import

Source details

Coverage: Named provider offers sampled by ChatHome; not the whole market.
Method: Published product and rate information is imported or manually verified.
Known limitations: Rates and eligibility can change before the next check. Confirm with the provider.

Air & noise

Station readings and strategic noise maps are separate sources.

Administration de l’environnement — live air-quality readings
Dataset / API identifier: official live service · not cached as listing evidence
Source type: Official public dataUpdate method: Updated when the source publishes
Luxembourg Geoportail strategic noise maps
Dataset / API identifier: road/rail Lden + Lnight · air Lden
Source type: Official public dataUpdate method: Scheduled snapshot

Source details

Coverage: Named air-monitoring stations and published strategic noise-map layers.
Method: Station readings and static map publications are tracked separately.
Known limitations: Station readings may be near-live; noise maps are not real-time and coverage varies.

Found something inaccurate? Send us the source and details. We'll review it and publish a correction when confirmed.

Report a data issue See how we rank listings Search listings

Where our data comes from

The date below records when this lineage was reviewed. We do not label pipeline runs as source freshness because a successful run can reuse an older upstream release.

Lineage reviewed as of 2026-08-31