Skip to main content
Language
Commuting and public transport

Suburban postcodes with good public transport: how to build a realistic shortlist

A useful suburban shortlist shouldn't start with a national ranking. It starts with one real city node and two or three plausible outer candidates. Lausanne, Bern, and their commuter belts make this clear immediately.
Updated:
14 July 2026
Read time:
4 min
Share:XFacebookLinkedIn
Old Chapel Bridge over the river in Lucerne

What a real shortlist looks like

A realistic shortlist is almost never "all suburbs around one city." It usually comes down to three or four places with distinctly different everyday profiles.

Take a look at 1260 Nyon. It gives you a large Lake Geneva commuter town with 23,616 residents and a single-person tax rate of 11.0%. 4600 Olten gives you a highly connected central rail hub with 19,047 residents and 10.5%. 3052 Zollikofen offers a Bern-fringe base with 12,287 residents and 11.3%. That is a usable shortlist because each place implies a completely different daily routine.

Good public transport on paper simply isn't enough. A credible shortlist has to survive the morning rush, the evening return, and the inevitable delays that happen in real life. A suburban postcode can look perfect in a brochure and still be a terrible fit once you properly measure the route.

Swiss S-Bahn network
Source: Wikimedia Commons, file S-Bahn-Netze Schweiz.png.

The S-Bahn map helps because it shows how the network hangs together. But it absolutely does not tell you whether the walk from your front door to the platform is short enough.

What belongs on the list

The places that belong on your shortlist are the ones that fit a strict time budget and have enough local scale to support your routine. The nearbyPlz field helps you see whether a postcode sits inside a real, integrated commuter ring. Population and household counts help you distinguish a mature commuter town from a tiny settlement that just happens to have a train station.

Zollikon station
Source: Wikimedia Commons, file Bahnhof Zollikon Gleis.JPG.

A station can look incredibly convenient on a map and still be a poor fit if the transfer is awkward, the frequency drops off early, or the final walk is unpleasant. This is exactly why your shortlist should stay short: if you can't mentally picture the real trip just from looking at the page, you should probably drop the option.

Transport and tariff association map of Switzerland
Source: Wikimedia Commons, file Karte der Verkehrsverbünde und Tarifverbünde in der Schweiz.png.

Tariff zones change the picture faster than most people expect. If you are commuting every single day, the zone boundaries, transfer points, and exact timetable fit matter infinitely more than a nice-looking dot on a map.

How to keep it short

The cleanest rule is to brutally cut any postcode that fails one of three basic tests: the route looks messy, the tax savings are too small to justify the extra distance, or the place is just too small to support your daily needs. What survives should feel like a real alternative, not just a map pin near some train tracks.

That is where a data shortlist ends. After that, you need the actual timetable, the fare zone map, and the exact street address to take over.

What to check first

Horizontal scroll to compare values

PointWhat to verifyWhy it helps
Anchor/plz/1003-lausanne, /plz/3004-bernGives the comparison a real frame
Useful dataoev stop density, nearbyPlz, demographics.populationShows which signals can carry the list
Follow-up pages/blog/how-to-evaluate-a-postcode-before-moving, /methodologyAdds criteria and limits
VerificationTimetable, register, calculatorTakes over once the decision becomes binding

How to use this article

  • Open the starting page first and read the context there.
  • Keep only the data points that describe the commute.
  • Check whether a place is merely close on a map or genuinely workable day to day.
  • Switch to the official source before making a final decision.
Blog

Selected articles from the PLZHub blog