Platform · ImmobilienScout24

ImmobilienScout24 Data Scraping

Q: Are these transaction prices?

No. price_type is a constant asking. German transaction data exists through separate official channels with different coverage and lag.

German rents are quoted cold. The number on the listing is not what the tenant pays, and the gap is not a constant.

ImmobilienScout24 data scraping collects German property listings, rents, asking prices and attributes. The single biggest trap in German rental data: rents are conventionally quoted as Kaltmiete — cold rent, excluding utilities and service charges. A German rent compared against a UK or French rent without that adjustment understates by a large and variable margin, and the margin cannot be estimated away.

Every German listing has at least two rent numbers and they mean different things. Taking the first one you find is the most common error in cross-border rental analysis.

Get a free sample See sample data

Free pilot on your own ImmobilienScout24 list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

is24.jsonl LIVE FEED

{"listing_id":"is-44120","city":"Berlin","district":"Example district", "rent_amount":980,"rent_basis":"kalt", "nebenkosten_amount":240,"heating_included":false, "warm_rent_total":1220, "living_area_sqm":68, "energy_value":142,"energy_class":"D", "energy_certificate_type":"bedarfsausweis", "note":"980 is the headline. 1220 is closer to what the tenant pays"} {"listing_id":"is-88120", "rent_amount":890,"rent_basis":"unstated", "nebenkosten_amount":"null", "nebenkosten_estimated":"not_produced", "caution":"estimating would need building, heating and consumption we do not observe"} {"observation_interval_minutes":60, "first_seen":"2026-08-25T09:14Z","last_seen":"2026-08-25T14:02Z", "note":"live for under 5 hours. a daily panel would never have seen it"}

3 of 984,220 listing rows · Germanyrent_basis MANDATORY · Nebenkosten never estimated · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to ImmobilienScout24 or its owners. ImmobilienScout24 and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

ImmobilienScout24 at a glance

How we handle ImmobilienScout24 specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Portal: ImmobilienScout24 — Germany
The trap: Kaltmiete — rents are quoted cold, excluding utilities
Also quoted: Warmmiete — warm rent, including service charges
The gap: Nebenkosten, and it varies by property, age and heating type
So: rent_basis is mandatory on every record
Energy: Energieausweis rating, with its type recorded
Deposit: Regulated. Captured where stated
Refresh: Daily. German rental listings move quickly in tight markets

Platform specifics

Two rents, and why the gap cannot be estimated

These are the reasons a ImmobilienScout24 dataset needs its own handling rather than a shared retail schema.

Cold rent, warm rent, and the charges between them

German rental listings conventionally quote Kaltmiete — the base rent for the property, excluding utilities and service charges. Separately they may quote Nebenkosten (service charges) and a Warmmiete total.

Kaltmiete is the headline number and it is not what the tenant pays.
Nebenkosten vary substantially by property size, building age, heating type and the services the building provides.
Heating may or may not be included in the quoted Nebenkosten, and listings differ in whether they say.
Warmmiete is not always shown, and where it is, what it includes is not standardised.

rent_basis is mandatory on every record — kalt, warm or unstated — with nebenkosten_amount and heating_included captured separately where the listing states them.

We do not estimate the gap

An estimated Nebenkosten figure would depend on building characteristics, heating system and consumption, none of which we observe. A cross-border comparison needs the real numbers or an explicit assumption you can state — not one we embedded.

Same position as bills on our SpareRoom page, and it matters more here because in Germany it is the convention rather than the exception.

Energieausweis, and the two types that are not comparable

German properties carry an Energieausweis, and there are two kinds that produce different numbers for the same building.

Verbrauchsausweis — based on actual consumption, which depends on how previous occupants used the building.
Bedarfsausweis — based on a calculated demand assessment of the building fabric.

They are not interchangeable, and comparing a consumption-based figure to a demand-based one measures partly the methodology rather than the building.

We record energy_certificate_type alongside the value and the class. Where the type is not stated we flag it rather than assuming, because an energy comparison across mixed types with no type field is measuring two things at once.

Asking, not transaction

As everywhere, price_type is a constant asking. German transaction data exists through separate official channels with different coverage.

Market tightness, and what we do not produce

Listing lifetime is short in tight markets

In the tightest German rental markets a listing can be live for hours. That has a practical consequence for collection design rather than being a market observation.

A daily observation misses listings entirely. They appear and go between runs.
A supply count from daily snapshots understates in exactly the markets clients care most about.
Sub-daily collection is genuinely necessary in those cities, unlike most property markets where daily is ample.

We record observation_interval_minutes so a supply figure is interpretable, and we recommend sub-daily in the tight markets rather than selling a daily panel that will quietly miss stock.

What we do not collect

Landlord or agent individual details, applicant information, or any personal data. Agency name is a commercial entity. German data protection is strict and our exclusion predates it, as it does everywhere.

Scope

What we collect on ImmobilienScout24, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

rent_basis mandatory — kalt, warm or unstated — on every record
Nebenkosten amount and heating_included where the listing states them
energy_certificate_type alongside value and class, or flagged unstated
Deposit amount where stated
observation_interval_minutes, so a supply figure is interpretable
Sub-daily collection recommended in tight markets, with the reasoning
price_type constant asking
Agency name as a commercial entity
Property attributes, district and build year as published

❌ What we do not, and why

A Kaltmiete compared against an all-in rent from another market
An estimated Nebenkosten figure
An energy value compared across certificate types with no type field
A daily supply count sold in a market where listings live for hours
Landlord, agent or applicant personal data

Core ImmobilienScout24 fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
listing_id / agency_name / city / district	The listing, agency and geography
rent_amount / rent_basis	The rent, and what it is. Mandatory
nebenkosten_amount / heating_included	Where the listing states them
warm_rent_total	Where shown. What it includes is not standardised
deposit_amount	Where stated
energy_value / energy_class / energy_certificate_type	Value, class and which kind
price / price_type	For sales. Asking, with the type constant
living_area_sqm / rooms / build_year	As published
observation_interval_minutes	So a supply figure is interpretable
first_seen / last_seen	Lifecycle, which is short in tight markets
observed_at	Timestamp

Use cases

What teams do with ImmobilienScout24 data

Cross-border rental comparison that is not systematically wrong

rent_basis on every record with Nebenkosten separate, so a German rent is compared to a UK or French one on a basis you state rather than understated by a variable margin.

German rental supply in tight markets

Sub-daily observation with the interval recorded, since in the tightest cities a daily snapshot misses listings that live for hours — in exactly the markets clients care most about.

Energy-efficiency analysis with type recorded

Certificate type alongside value, so consumption-based and demand-based assessments are not compared as though they measured the same thing.

District-level rent benchmarking

Cold rent per square metre by district on a consistent basis, which is the standard German reference and only works if the basis is recorded.

The 24-hour sample — run on your sources, not ours

Send us a ImmobilienScout24 item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

REST endpoints on the same pipeline, with sandbox keys for testing.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A fixed-scope extraction for a single project or research question.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Pricing is quoted individually, based on category scope, number of markets, cadence and ongoing identity maintenance. After a scoping call and free pilot, we quote a fixed monthly figure, with no per-request metering.

Book a 20-min scoping call Request a quote Talk to an engineer

ImmobilienScout24 is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. ImmobilienScout24 data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what real estate data covers, and a ImmobilienScout24-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

ImmobilienScout24 data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Cold rent — the base rent excluding utilities and service charges. It is the headline number on German listings and it is not what the tenant pays.

A German rent compared against a UK or French rent without that adjustment understates by a large margin, and the margin varies by property size, building age and heating type.

No. An estimated figure would depend on building characteristics, heating system and consumption, none of which we observe.

We capture Nebenkosten and heating inclusion where the listing states them, and leave the rest to an assumption you can state rather than one we embedded.

Because there are two kinds and they produce different numbers for the same building — one based on actual consumption, one on a calculated assessment of the building fabric.

Comparing across them without a type field measures partly the methodology rather than the property. We record the type, and flag it where the listing does not state it.

In the tightest German rental markets, yes. A listing can be live for hours, so a daily observation misses stock entirely and a supply count understates in exactly the markets clients care most about.

This is unusual — in most property markets daily is ample. We record the observation interval so a supply figure is always interpretable.

No. price_type is a constant asking. German transaction data exists through separate official channels with different coverage and lag.

We quote individually. Observation frequency is the main driver here rather than listing volume, because tight markets need sub-daily runs to produce an honest supply figure.

One scoping call, a free pilot within 24 hours, then a fixed monthly quote. Request a quote.

See real ImmobilienScout24 data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner