DATAKILDE / PILOT ON REQUEST

Building and property data for your product.

Connect addresses to building facts and relevant property context through one API. We start with a focused dataset and document coverage, sources and freshness for your use case.

Discuss API access ↗

We validate the data and access terms before agreeing a delivery.

01 / FROM ADDRESS TO BUILDING

Useful data starts with the right building.

An address can belong to several buildings and dwelling units. We establish the level your product needs and distinguish reliable matches from ambiguous links.

Address or registry ID
Match and relationship checks
Building profile with sources

Identity

Address, address ID and building number. Multiple buildings or uncertain matches are presented as alternatives.

Building profile

Registered building type, status, area, floors and dwelling count, where recorded.

Technical details

Selected water, sewage and heating information. Coverage and meaning are validated for each field.

Property context

Selected geographic hazard and proximity information can be evaluated as a pilot extension.

02 / PRODUCT USE CASES

Less manual research. A better starting point.

Customer onboarding

Prefill relevant building facts and let customers verify them.

Service planning

Use a documented building profile to plan services and follow-up.

Property products

Bring address and building context into your own workspace.

03 / AN EXPLICIT RESPONSE

Including when a fact is missing.

Unknown means unknown. A missing field does not mean zero area or no risk. Source, timestamps and match status accompany the agreed delivery.

Illustrative response format. Fictional example, not a live lookup or a final API contract.

{
  "example": true,
  "match_status": "matched",
  "building_number": "EXAMPLE-001",
  "area_m2": 144,
  "heating": null,
  "provenance": {
    "source": "Matrikkel",
    "source_updated_at": null,
    "last_successful_retrieval": null,
    "freshness": "unverified"
  }
}

04 / SOURCES AND QUALITY

Quality you can verify.

We work with address and building data from Geonorge and Matrikkel. Coverage and age vary. The pilot documents what is available for your addresses, its sources and what needs confirmation.

Registry facts are not a condition assessment. Resident data, alarm installations and live sensor readings are not included. Source agreements and permitted use are checked before fields are made available.

POSSIBLE EXTENSIONS / LOCAL CONTEXT

Put the building in context.

These data layers can be evaluated in a pilot. We verify coverage, freshness and calculation methods before including them in a delivery.

Fire and police stations

Nearest registered station and distance. Driving time requires a verified route and is not an emergency response-time estimate.

Local crime statistics

Published, aggregated SSB figures with municipality, offence group and reporting period. Area context, not a risk estimate for an individual home.

Traffic sensors

Nearest relevant counting point, distance and available traffic volumes. Measurement periods and data quality accompany each value.

Traffic events

Vegvesen reports including road closures and roadworks. Access and geographic matching are evaluated in the pilot.

Inspect the documentation before getting in touch.

The API contract and data catalogue are publicly readable. They describe endpoints, fields, sources and limitations. Address queries and customer-specific usage require approved access; the links below do not expose household records.

A published contract does not mean every field is available for every address. Nationwide building coverage has not been verified. Coverage and source material are checked for the specific pilot.

05 / START WITH A FOCUSED PILOT

Let’s test against your needs.

Define the use case, required fields, volume and freshness needs.
Evaluate 20–50 representative addresses and document matches, coverage and gaps.
Agree the dataset, access, price and integration when the result proves useful.