Skip to content

← All sections

Election results for the address's polling district

Election results for the address's polling district (stemmekrets) and the kommune total: turnout, votes and the leading party. Aggregates only, nothing about any voter, and districts are redrawn between elections.

election_results11 fields11 of these fields open in the demo
Source
Valgdirektoratet valgresultat.no
Geography
The address point
Reported stale after
400 days
Access
Requires an API key granted this section
Contract version
1
In packages
local_economy

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
9 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 9 Nov 2026
Newest record
9 Nov 2026
Municipalities with data
357

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
unverified
Declared redistribution
Not established
Catalogue basis
Unverified

API warnings

The API returns these notes in warnings.

  • Aggregate results for the polling district (stemmekrets) the address register assigns to this address, plus the municipality total; nothing about any voter. Districts are redrawn between elections.

Provider-contract fields

2 of 11 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
district_namestring | nullcontextopen
levelstring | nullcontextopen
election_yearstring | null (årstall)contextopen
election_typestring | nullcontextopen
turnout_pctnumber | null (%)valueopen
votes_totalinteger | nullcontextopen
top_partystring | nullvalueopen
top_party_pctnumber | null (%)contextopen
partiesobject | nullcontextopen
updated_atstring | nullcontextopen

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=election_results'

# 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/election_results?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.