Estimated monthly rent of the dwelling (model, advertised rent)

Estimated monthly advertised rent of the one dwelling at the address with an 80 % interval and the factors behind it, from a model trained on advertised rents. An estimate; listings are never published.

asking_rent_estimate19 fieldsNot in the demo

Source: Approach dwelling_asking_rent model (model platform) trained on advertised rents via AEDA and Matrikkel dwelling facts
Geography: The address point
Reported stale after: 120 days
Access: Requires a separate agreement (Kartverket Matrikkel)
Contract version: 1
In packages: models

Status right now

State: Empty
The source was read but holds no rows. The section answers “no data”, not “no”.
Last loaded: not measured
Newest record: not measured
Municipalities with data: 0

Measured 29 Oct 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.

Available with: a separate agreement, switched on per account · Ask about an agreement

Model and method

What monthly rent would the dwelling most likely be advertised at?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type: Model
Method: Machine learning
Declared maturity: Marked stable in the catalogue
Reference comparison: A reference is declared
Contract version: 1
Model artifact and runtime version: Not established by this catalogue description

Inputs, headline fields and comparison basis

Declared inputs

advertised rents (AEDA)
Matrikkel dwelling facts
SSB 06230
location sections

Headline output fields

asking_rent_estimate_nok_month, interval, status

Declared comparison basis

advertised rents on the last six months and on kommuner held out of the fit, against the area median rent per m2 and SSB 06230

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

Source terms and reuse

These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.

Declared licence or terms: Kartverket Matrikkel
Declared redistribution: Agreement terms apply
Catalogue basis: Separate agreement

Attribution and note

Shown from the contract in its original language.

Served under a separate agreement; its terms decide what may be shown or passed on.

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

Leie-estimat: the monthly rent the one dwelling Matrikkel records at the address would most likely be advertised at, at the newest SSB 06230 rent level (as_of). Not an agreed rent; furnishing, standard and what the rent includes are not inputs. status insufficient_data (ikke nok data) means no validated estimate for this dwelling type and market.
The dwelling_asking_rent model on the model platform: gradient-boosted trees on log monthly rent per m2, trained on advertised rents (FINN rent listings via AEDA; no listing is published), indexed with SSB 06230, with the dwelling's facts and Datakilde's location features. interval is a split-conformal 80 % interval; attribution lists the factors behind the estimate (TreeSHAP).
The validation block is the release's held-out figures on the last six months of listings and on kommuner the fit did not see, beside the area median rent per m2 and the SSB 06230 national rent per m2. A release is only built when it beats both with 80 % coverage.
Sources: advertised rents via AEDA (estimates only), Kartverket Matrikkel (by agreement), SSB 06230 (CC BY 4.0). Model: Approach.

Provider-contract fields

3 of 19 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

Field	Type	Role
method	string \| null	context
method_version	string \| null	context
estimate_kind	string \| null	context
status	string \| null	value
asking_rent_estimate_nok_month	number \| null	value
asking_rent_per_m2_nok_month	number \| null	context
currency	string \| null	context
as_of	string \| null	context
interval	object \| null	value
uncertainty	object \| null	context
attribution	object \| null	context
group	string \| null	context
location_level	string \| null	context
inputs	object \| null	context
missing_features	array<string> \| null	context
release_id	string \| null	context
artifact_sha256	string \| null	context
validation	object \| null	context
updated_at	timestamp \| null	context

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643?include=asking_rent_estimate'

# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/asking_rent_estimate?limit=25'

Why it cannot be tried here

This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.