Skip to main content
Language
Postcode and municipality

Check an address before moving: how to assign locality and municipality correctly

The name on your future address line doesn't always tell you which municipality you are actually moving to. If you assume they match, you might build your shortlist on the wrong foundation.
Updated:
5 May 2026
Read time:
4 min
Share:XFacebookLinkedIn
Close-up of a set of house keys with a wooden house-shaped keychain on a wooden table

What this check actually accomplishes

A postcode looks like a simple, single answer. But it can easily point to two entirely different things: the name the post office uses (the locality) and the administration you pay taxes to (the municipality). When you are planning a move, the only practical question is whether those two layers line up cleanly, or if the address requires a much closer look.

You can see the contrast perfectly by looking at four examples. 8001 Zurich is the clean dream: one locality, one municipality, zero ambiguity.

Then you get a case like 6052 Hergiswil NW. It looks perfectly clean on an envelope, but the municipality layer reveals a tiny 0.199% sliver that belongs to Horw.

1700 Fribourg takes it further. It looks like a single, solid city label, but the postcode footprint quietly spills over into Tafers and Düdingen.

And finally, you have 1008 Prilly, which doesn't even try to hide the split. Both its locality and municipality layers are cut straight down the middle, exactly 50/50 between Prilly and Jouxtens-Mézery.

Flow diagram for checking an address before moving
Graphic: PLZHub, practical check order before moving.

The signals you should read first

When you do your first pass on an address, you only need to check the localities, municipalities, and the search index. These three layers instantly tell you if you are dealing with a clean one-to-one match, a mostly clean setup with a tiny spillover, or a fundamentally mixed postcode that you can never trust on its face.

This matters most when the name on the address line sounds a lot more confident than the underlying data actually is. 1700 Fribourg is the perfect trap: the postal name feels incredibly singular, but the municipal reality is not. 1008 Prilly is even more obvious; the data tells you immediately that the postcode alone is practically useless for administrative decisions.

Diagram of risks when locality and municipality are confused
Graphic: PLZHub, why a good-looking address does not automatically mean the expected municipality.

When the official source takes over

The moment an address is going to trigger an actual signed lease or a moving truck, your first read is no longer enough. By that point, the postcode page has already done the heavy lifting: it warned you whether the address was straightforward like 8001 Zurich, slightly blurry like 6052 Hergiswil NW, or fully tangled like 1700 Fribourg and 1008 Prilly.

You use the official municipal register to make the final, binding confirmation. You shouldn't be using it to try to map out the general structure from scratch.

What this article helps clarify first

Horizontal scroll to compare values

AspectWhat to checkWhy it matters
Starting questionHow to verify locality and municipality before movingKeeps the article tied to the real use case
NamingLocality and municipalityShows where the address lands in practice
Multiple hitsPostcodes with several municipalitiesAvoids misreading mixed postcode areas
Data basislocalities, municipalities, search indexShows which PLZHub signals actually support the read

How to use this article

  • Start with a clean case like 8001 Zurich so you know what normal looks like.
  • Use 6052 Hergiswil NW to spot a tiny municipality overlap that technically matters.
  • Use 1700 Fribourg and 1008 Prilly to recognize genuinely mixed postcode structures.
  • Verify the exact address only after you know which layer is causing the ambiguity.
Blog

Selected articles from the PLZHub blog