Skip to main content
Language
Moving and taxes

How to evaluate a postcode before moving (the right order)

Most people start their apartment hunt by looking at the lowest tax rates. That's usually a mistake. A postcode page is only useful if it helps you quickly cross the wrong places off your list.
Updated:
13 March 2026
Read time:
4 min
Share:XFacebookLinkedIn
Swiss urban, rail, or alpine landscape used as the cover image

Find the real trade-off

A good shortlist forces you to make a real choice. 8001 Zurich gives you a dense city center with a clean, single-municipality layout and a tax rate of 10.1% (for a single person). 6300 Zug is financially lighter at 7.9%, but you have to treat its page as an estimate because the postcode doesn't perfectly match a single municipality. 1003 Lausanne is heavier on taxes at 11.5%, but offers a very clear urban structure.

Before you move, you shouldn't just ask, "Which postcode is cheapest?" You should ask, "Which trade-off am I actually willing to make?" Living costs, administrative simplicity, and daily commute times rarely point to the exact same place.

If your current shortlist doesn't force a difficult choice, it's probably too vague. A useful list has built-in tension: one place is cheaper but harder to commute from, another is administratively simpler but more expensive.

Map of Switzerland
Source and image credit: Wikimedia Commons, File:General_Map_of_Switzerland.jpg.

Don't treat geography as decoration

Once you check the taxes, look immediately at the surrounding area. 8001 Zurich sits directly next to dense urban postcodes like 8006, 8002, and 8004. That tells you instantly that you're moving into a highly connected city fabric. 1003 Lausanne sits in a similar urban cluster.

But what about a mixed postcode like 1008 Prilly? It might still be a great place to live, but you have to check the exact street address because the postcode crosses municipal borders.

This is why I always tell people to read our pages in a specific order: municipality split first, taxes second, local geography third, and public transport last. If you do it backwards—falling in love with the map before checking the municipality split—you might end up accidentally comparing the wrong tax rates.

Bern railway station tracks
Source and image credit: Wikimedia Commons, File:Bern_railway_station,_Tracks.jpg. Source and image credit: Wikimedia Commons, File:Bern_railway_station,_Tracks.jpg.

Know when to verify

PLZHub does a great job showing you if a postcode crosses municipal lines, if the local taxes fit your budget, and what the surrounding towns look like. It does not confirm your lease agreement, your door-to-door train connection, or your final tax bill.

Stop browsing once your shortlist is concrete enough to verify at the street level. If your conclusion is "Zurich or Zug," you need to dig deeper. But if you end up saying "I'm looking at 8001 Zurich for the lifestyle, 6300 Zug for the taxes, and 1008 Prilly as a compromise," then you've used the data perfectly. Your next step is simply checking the exact street addresses with official calculators.

A practical relocation reading order

Horizontal scroll to compare values

PriorityPLZHub sectionWhat it helps you answer
1Municipality and locality splitWhich administrative context really applies?
2Tax sectionIs the area roughly in budget for your scenario?
3Map and nearby postcodesWhat is the surrounding geography and local context?
4Transport and live sectionsDoes the area look workable day to day?

Move-decision checklist

  • Check whether the postcode spans more than one municipality.
  • Compare tax pages only after you lock the same scenario.
  • Use the map and nearby-postcode links to understand the area around it.
  • Verify the exact address with official municipality tools before you commit.
Blog

Selected articles from the PLZHub blog