Named sources
Core page data comes from Swiss public sources including ESTV, swisstopo, BFS, BAV, geo.admin.ch, and opendata.swiss.
Methodology
How postcode pages are produced
Every PLZHub page is built from named data sources, explicit transforms, and a review layer. The methodology matters because postcode pages can look simple while the geography and municipality relationships underneath them are not.
Refresh cadence
The build pipeline checks freshness metadata before build and syncs when a data year or upstream source date changes.
Verification rule
PLZHub is for orientation. The ESTV calculator and other official providers remain authoritative for personal, statistical, administrative, and legal confirmation.
Primary data sources
swisstopo provides the postcode and locality base, ESTV provides standardized municipal tax outcomes, BFS provides population and demographic statistics, and BAV provides the public-transport snapshot. GeoAdmin supplies the postcode-centre elevation and additional public services add warning, transit, and open-data context.
Street names are utility context only. They are not treated as an authoritative address register, and they are not the main indexable content surface of the site.
How tax and postcode-level values are interpreted
PLZHub compares three official ESTV household scenarios. The tax block uses the postcode’s primary municipality and does not blend municipal taxes when a postcode spans several municipalities.
Tax comparisons must use the same scenario. For a personal final amount, users should switch to the official ESTV calculator because deductions, religion, wealth, and individual circumstances can change the result.
How demographic and locality splits are derived
Postcodes and municipalities do not line up perfectly. When one postcode covers more than one municipality, PLZHub uses the address-share information available in the source data to estimate the split and make the weighting visible.
That estimate is useful for orientation, but it should not be treated as a population register. Municipal or cantonal statistical publications remain authoritative.
Known limitations
Public datasets update on different schedules, so a page may combine source years that are close but not identical. Runtime sections such as weather or warning data can also change after the static page was generated.
- A postcode is not the same thing as a municipality boundary
- Some metrics are weighted estimates, not direct postcode counts
- Live API sections can be temporarily unavailable or delayed
- Official providers remain the source of record for binding decisions