# Luxembourg Property Price Stats – atHome prices by town (`listingworks/luxembourg-property-price-stats`) Actor

Median asking prices, price per m² and size of apartments and houses for sale and to rent on atHome.lu, by town and by number of bedrooms, with listing counts. Aggregates only, no listings, addresses or names. Read live each run.

- **URL**: https://apify.com/listingworks/luxembourg-property-price-stats.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 listing analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Luxembourg Property Price Stats – atHome prices by town

Median asking price, price per m² and size of apartments and houses for sale and to rent on atHome.lu, in Luxembourg's 20 largest towns on the site and by number of bedrooms, with the number of listings behind each figure. Name one town (or a quarter, e.g. luxembourg/kirchberg) to look at it in depth.

### Example

| Region | Sale / rent | Listings | Median asking price | Median price per m² | Median size |
|---|---|---:|---:|---:|---:|
| Luxembourg | sale | 24 | €1,215,000 | €9,798 | 121 m² |
| Esch-sur-Alzette | sale | 24 | €597,000 | €6,165 | 112 m² |
| Luxembourg | rent | 24 | €3,100 | €28.85 | 122 m² |

Default input, run on 22 October 2026: 993 listings read in 3.7 minutes, 115 aggregate rows; at $1.50 per 1,000 listings read the run cost $1.49.

### What you get, and what you don't

- **Counts, not listings.** The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts,
  no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
- **List pages only.** The run reads the site's public search-result pages, paced as the site's own Actor in this
  catalogue is (one request every 2 seconds), and never opens a listing's own page.
- **A sample of the newest listings.** The site lists newest first; the run counts up to `maxListings` of them. The
  summary row says how many were read and, where the site shows it, the site's own total.
- **Medians need 5 values.** A median is shown only where at least 5 listings have the value; otherwise it is empty.
- The last row of every run is a `summary` per site: listings read, the site's own total where shown, whether the run
  stopped at `maxListings`, and any warning (an unknown place, a blocked page).

### Input

| Field | What it does |
|---|---|
| `maxListings` | Listings to read and count at most (default 1,000, up to 10,000), shared evenly across the places and sale / rent searched. |
| `transaction` | `sale` (default), `rent` or `both`. |
| `region` | One place only (see below). Empty: every place listed below. |

Example: `{"region": "Esch-sur-Alzette", "transaction": "rent"}`. An input the run cannot use (a place the site does not know) ends
SUCCEEDED with no rows and the reason in the status message and the run report (`RUN_REPORT`).

### Output

| Field | Meaning |
|---|---|
| `level` | `region` (one row per place and sale / rent), `region_rooms` (per place, sale / rent and bedrooms) or `summary`. |
| `date` | Day of the run (UTC). |
| `source` | The site counted. |
| `region` | The place searched. |
| `transaction` | `sale` or `rent`. |
| `rooms` | Bedrooms: `0` (studio), `1`, `2`, `3`, `4+`, `unknown`; `all` on `region` rows. |
| `listings` | Listings read in this group. |
| `median_asking_price` | Median asking price (rent: per month); empty below 5 listings. |
| `median_price_per_m2` | Median of price / living area; empty below 5 listings with an area. |
| `median_size_m2` | Median living area. |
| `currency` | EUR. |

### How the counts are made

`region` is the town searched on atHome.lu (the site browses by town, not by the 100 communes). With no `region` the run reads 20 towns (Luxembourg, Esch-sur-Alzette, Diekirch, Bascharage, Differdange, Dudelange, ...), apartments and houses, for the transaction asked (sale by default; `both` adds rent), sharing `maxListings` evenly: with the default 1,000 that is about 25 listings per town and type (about 12 per town, type and sale / rent with `both`). Raise `maxListings` or name one town for firmer medians. Listings outside these towns are not counted unless you name the town.

Prices are the asking prices shown (rent per month). Price per m² is price divided by the living area shown; listings without an area count in `listings` but not in the m² medians.

### Pricing

$1.50 per 1,000 listings read (event `listing-analyzed`), no start fee. The aggregate rows themselves
are free: a default run reads up to 1,000 listings and costs at most $1.50. Set a maximum charge per run
in the run options to cap it.

### Good to know

- The data is what atHome.lu shows on its public list pages on the day of the run.
- Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its `date`.
- Questions or a missing region: open an issue on this Actor.

# Actor input Schema

## `maxListings` (type: `integer`):

How many listings the run reads and counts at most (charged per listing read). The counts are a sample of the newest listings, not the whole market, unless the site holds fewer. Shared evenly across the places and sale / rent searched.

## `transaction` (type: `string`):

Which listings to count.

## `region` (type: `string`):

Count only this place: give a town as atHome writes it (e.g. Luxembourg, Esch-sur-Alzette, Mondorf-les-Bains), or a town and quarter (e.g. luxembourg/kirchberg). Empty: the 20 largest towns.

## Actor input object example

```json
{
  "maxListings": 1000,
  "transaction": "sale",
  "region": ""
}
```

# Actor output Schema

## `overview` (type: `string`):

The aggregate rows of the run.

## `summary` (type: `string`):

One row per site: listings read and warnings.

## `runReport` (type: `string`):

Every search made, with its verdict.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/luxembourg-property-price-stats").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/luxembourg-property-price-stats").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call listingworks/luxembourg-property-price-stats --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/luxembourg-property-price-stats"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Pd4uRFveh1nqfjDce/builds/BOk9e2DuvaeoLWNnC/openapi.json