The plot (teig) under the address and the plots around it
The plot (teig) under the address and the plots around it: registered and polygon area, boundary accuracy class, buildings and dwellings on the plot, and plot sizes within 500 m.
Status right now
Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing
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
- Creative Commons Attribution 4.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Publisher terms
Attribution and note
Shown from the contract in its original language.
© Kartverket — Matrikkelen eiendomskart (Teig), CC BY 4.0
API warnings
The API returns these notes in warnings.
- plot_area_m2 is the Matrikkel's registered (beregnet) area of the teig containing the address point; plot_area_geometry_m2 is the area of the published polygon, which differs where boundaries are uncertain — boundary_accuracy_class is Kartverket's own class. A matrikkelenhet can consist of several teiger; this is the piece under the house. Neighbourhood figures are over teiger of 50–20 000 m² within 500 m, which excludes roads, commons and outfields.
Provider-contract fields
15 of 20 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| gnr | string | null | context | open |
| bnr | string | null | context | open |
| fnr | string | null | context | open |
| snr | string | null | context | open |
| plot_area_m2 | number | null (m2) | value | open |
| plot_area_geometry_m2 | integer | null (m2) | value | open |
| boundary_accuracy_class | string | null | value | open |
| plot_shared_by_several_units | boolean | null | value | open |
| has_heritage_site | boolean | null | value | open |
| has_ground_contamination | boolean | null | value | open |
| land_consolidation_requested | boolean | null | value | open |
| point_lease | boolean | null | value | open |
| boundary_dispute | boolean | null | value | open |
| buildings_on_plot | integer | null (antall) | value | open |
| dwellings_on_plot | integer | null (antall) | value | open |
| plot_area_per_dwelling_m2 | number | null (m2) | value | open |
| plots_500m | integer | null | value | open |
| median_plot_area_m2_500m | number | null (m2) | value | open |
| share_under_500m2_500m | number | null | value | open |
| updated_at | string | null | context | open |
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=plot'
# 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/plot?limit=25'Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.