Shareholder-register density for the address's postal code
Aggregated shareholder-register density for the address's postal code. It describes the postal code, never a person or household.
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: approved pilot customer and named section access
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.
- Aggregated register counts; person-level shareholder data is never exported. Postal codes with fewer than 10 distinct shareholders in a year are suppressed entirely, and suppressed codes still count toward the national median.
- Postal-code aggregate, not a per-capita rate and not information about any resident or household. The register covers unlisted AS/ASA reporting; nominee-held listed shares are not included. Figures are annual year-end snapshots.
Provider-contract fields
5 of 9 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| postal_code | string | null | context |
| fiscal_year | integer | null (årstall) | context |
| distinct_shareholders | integer | null | value |
| distinct_companies_held | integer | null | value |
| total_positions | integer | null | value |
| national_median_shareholders | number | null | context |
| density_index | number | null | value |
| national_percentile | number | null | value |
| refreshed_at | string | null | context |
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=investment_density'
# 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/investment_density?limit=25'Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.