Police log messages in the address's kommune, last 90 days
Police log messages (Politiloggen) in the address's kommune over the last 90 days, counted by category such as traffic, fire, violence and theft. Operations-centre messages, not reported crimes, and not placed at the address.
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
- Norsk lisens for offentlige data 2.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av Politiet Politiloggen (NLOD 2.0)
API warnings
The API returns these notes in warnings.
- Operations-centre messages, not reported crimes: what the police chose to publish about incidents they attended. Categories are Politiet's own. Counts are for the address's kommune over the last 90 days; the kommune-level crime statistics are in the crime section.
- placement is district_centroid: Politiloggen names a kommune and an area ("Sentrum", "Åsane"), never a position, and our geocoding puts a message at the centre of the area or kommune it names. No figure here is a distance to an incident or a count around the address; areas_90d lists the police's own area names in the kommune with their message counts, most first, at most 20 (area null when the message names none). An area name says nothing about which street in it.
- latest_incidents carries each message's category, area and time, never its text: Politiloggen's messages describe the people involved ("en mann i 40-årene") at a named street, which near one address can identify them.
Provider-contract fields
9 of 12 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 |
|---|---|---|---|
| municipality_code | string | null | context | open |
| placement | string | null | context | open |
| incidents_90d_municipality | integer | null | value | open |
| traffic_90d_municipality | integer | null | value | open |
| fire_90d_municipality | integer | null | value | open |
| violence_90d_municipality | integer | null | value | open |
| theft_burglary_90d_municipality | integer | null | value | open |
| public_order_90d_municipality | integer | null | value | open |
| accidents_90d_municipality | integer | null | value | open |
| areas_90d | array<object> | null | value | open |
| latest_incidents | array<object> | 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=police_incidents'
# 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/police_incidents?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.