Skip to main content
Language
Postcode and municipality

Population Figures in Mixed Postcodes: What the Numbers Actually Mean

It sounds simple: you look up a postcode, you see a population number, you assume that's how many people live in the town. But in Switzerland, postcodes and municipal borders rarely line up perfectly. When they clash, that population figure can mean something entirely different.
Updated:
5 May 2026
Read time:
3 min
Share:XFacebookLinkedIn
Swiss city or alpine landscape used as the cover image

What the number actually measures

When you look at a mixed postcode, the population figure always covers the entire geographical footprint of that postcode.

Take 1008 Prilly. It shows a population of 14,384. But geographically, that postcode is split almost exactly 50/50 between the municipality of Prilly and the municipality of Jouxtens-Mézery. Those 14,384 people do not all live in Prilly, and they certainly don't all pay taxes there.

By contrast, 1000 Lausanne 25 has 14,299 people, and because its borders fit entirely inside Lausanne, that number maps cleanly to a single municipality.

This is why PLZHub explicitly shows the demographics.isEstimate flag. When that flag is true, the population number is still highly accurate for the postal delivery area, but you cannot treat it as a municipal headcount.

Map of Switzerland with its main regions and cantons
General map of Switzerland
Image: General_Map_of_Switzerland.jpg by swisstopo, via Wikimedia Commons.

Understanding the geographic weights

The municipalities.weightedSharePct metric tells you how the physical land of a postcode is divided. It does not tell you where the people are standing.

In 1040 Echallens, the land area is split into three roughly equal thirds: Echallens, Villars-le-Terroir, and Saint-Barthélemy (VD). In 1071 Chexbres, the territory is split straight down the middle between Chexbres and Rivaz, with tiny slivers bleeding into Puidoux. In 6110 Wolhusen, the municipality of Wolhusen clearly dominates with 75%, but Werthenstein and several smaller fragments are still trapped inside the same postcode boundary.

Even a seemingly straightforward place like 1033 Cheseaux-sur-Lausanne is mixed: it is 98.4% Cheseaux-sur-Lausanne, but fragments of Crissier and Lausanne are technically caught inside the postal lines.

Yellow Swiss mailbox on a stone wall
Swiss mailbox as an official reference point
Image: Swiss_mailbox_die_Post.jpg by Toni_V, via Wikimedia Commons.

How to use this data correctly

Read the population figure as a signal for the postcode's density and vibe, not as an official town census.

If you are comparing neighborhoods, looking at transit options, or checking general demographics for a move, the postcode population works perfectly well. But the moment you need to know exactly how many people belong to a specific municipal tax base, you must drop the postcode data and look at the official municipality figures. That is where the postcode's usefulness ends.

Real examples of mixed postcodes

Horizontal scroll to compare values

PostcodeMunicipal mixThe reality of the number
1008 PrillyPrilly 50%, Jouxtens-Mézery 50%The 14,384 residents live across the entire postcode area, not just in Prilly.
1040 EchallensEchallens 33.3%, Villars-le-Terroir 33.3%, Saint-Barthélemy (VD) 33.3%The 8,934 people are spread across three completely different municipalities.
6110 WolhusenWolhusen 75.4%, Werthenstein 18.9%, plus fragments2,453 people. Mostly Wolhusen, but roughly a fifth sit in Werthenstein.
1000 Lausanne 25Lausanne 100%14,299 people, cleanly and entirely assigned to one single municipality.

How to interpret the data correctly

  • Do not assume the population number on a postcode page equals the town's population.
  • Check the `demographics.isEstimate` flag. If it is true, you are looking at a mixed area.
  • Use `municipalities.weightedSharePct` to understand how the postcode's land area is divided.
  • Switch to official municipal sources if you need a hard headcount for local voting or tax totals.
Blog

Selected articles from the PLZHub blog