Mobile coverage in the municipality (4G/5G)
mobile_coverage23 fields23 of these fields open in the demo
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.
- Kommune is the finest grain Nkom publishes for mobile coverage: these are shares of the kommune's households and land area, not the signal at this address. Shares are 0-1. basis is any coverage; 30 and 100 are estimated download speeds of at least 30 and 100 Mbit/s outdoors; any is 4G or 5G. Indoor coverage, operator and capacity at busy hours are not represented.
- Nkom names kommuner, not codes; the pipeline resolves names with Nkom's own name/code pairs from the same survey and skips any it cannot match rather than guessing.
Fields
18 of 23 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” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| municipality_code | string | null | context | open |
| municipality_name | string | null | context | open |
| county_name | string | null | context | open |
| survey_year | integer | null (årstall) | context | open |
| households_4g_basis | number | null | value | open |
| households_4g_30 | number | null | value | open |
| households_4g_100 | number | null | value | open |
| households_5g_basis | number | null | value | open |
| households_5g_30 | number | null | value | open |
| households_5g_100 | number | null | value | open |
| households_any_basis | number | null | value | open |
| households_any_30 | number | null | value | open |
| households_any_100 | number | null | value | open |
| area_4g_basis | number | null | value | open |
| area_4g_30 | number | null | value | open |
| area_4g_100 | number | null | value | open |
| area_5g_basis | number | null | value | open |
| area_5g_30 | number | null | value | open |
| area_5g_100 | number | null | value | open |
| area_any_basis | number | null | value | open |
| area_any_30 | number | null | value | open |
| area_any_100 | number | null | value | open |
| fetched_at | timestamp | null | context | open |
Fetch this section
curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643?include=mobile_coverage" # paginated, one section at a time curl -H "X-API-Key: $APPROACH_API_KEY" \ "https://api.approach.no/api/v1/addresses/285717643/sections/mobile_coverage?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.