Part of a Data Solution
- Explore →
Postal Codes Solution
Every worldwide postal-code dataset in one bundle — the ultimate global reference for precise postal codes.
Premium
You're viewing a free sample
Get the complete dataset — all rows and files — delivered instantly after checkout, with lifetime access to the latest version.
- Secure checkout via Stripe
- Instant download after payment
- Lifetime access to the latest version
- Norwegian Licence for Open Government Data 2.0 license
API Access
Access dataset files directly from scripts, code, or AI agents.
Browse dataset files
API Access
Access dataset files directly from scripts, code, or AI agents.
Each file has a stable URL (r-link) that you can use directly in scripts, apps, or AI agents. These URLs are permanent and safe to hardcode.
Start with these files — they give you everything you need to understand and access the dataset.
- 1. Fetch datapackage.yaml to inspect schema and resources
- 2. Download data resources listed in datapackage.yaml
- 3. Read README.md for full context
Data Files
postal-codes-no-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 -- always NO | Country Code | |
| postal_code | string | Norwegian postal code (4 digits) | { "pattern": "^\\d{4}$" } | Postal Code |
| place_name | string | Postal town/place name, as maintained by Bring/Posten Norge | Place Name | |
| admin_name1 | string | Fylke (county) -- 17/17 covered, including the special territories Svalbard and Jan Mayen | Administrative Name 1 | |
| admin_code1 | string | Norway's own official fylkesnummer, NO- prefixed. 10 of 17 have a current ISO 3166-2:NO entry; the other 7 (Ostfold, Akershus, Buskerud, Vestfold, Telemark, Troms, Finnmark) are real post-2024 fylkesnummer with no individual ISO entry yet -- ISO's register has not caught up with Norway's 2024 fylke reform, see ATTRIBUTION.txt | Administrative Code 1 | |
| admin_name2 | string | Kommune (municipality) -- 359/359 covered | Administrative Name 2 | |
| admin_code2 | string | Official kommunenummer (4-digit) | Administrative Code 2 | |
| admin_name3 | string | Not populated -- Bring's own register does not carry a tier below kommune | Administrative Name 3 | |
| admin_code3 | string | Not populated | Administrative Code 3 | |
| latitude | number | Not populated in this release -- Bring's postnummerregister carries no coordinates | Latitude | |
| longitude | number | Not populated in this release | Longitude | |
| accuracy | string | Not populated | Accuracy | |
| alternative_city_name | string | Not populated in this release | Alternative City Name |
Download
Download sample CSVAbout
- Total rows
- ...
- Format
- CSV
About this dataset
Norway (NO): migration notes
Internal record of the P5 migration. This is a dated record (2026-10-05) and is not shipped in the zip.
- Issue: pc-28e.7.39 (open, stays on live data)
- Producer: none written. The descriptor keeps
pipeline: producer: customwith refresh disabled, and the data stays as harvested from the live zip in09d7c89. - Parity: not run (no producer).
Why it stays on live data
- There are no builder scripts:
scripts/only haspublish_r2.py. Nothing records how the live CSV was built. - Rule (user, 2026-10-03): no producer from scratch for a dataset with no builder scripts.
Decisions
| Decision | By | Basis |
|---|---|---|
| No producer; stay on live data | Standing rule (user, 2026-10-03) | No builder scripts to port |
Open questions
- None for P5. A producer would be new work (a new source and licence check), so it needs a user decision.
Provenance
Written 2026-10-05 from docs/parity/p5.md (batch sign-offs) and the bd notes on pc-28e.7.39.