Skip to main content
Language
Commuting and public transport

How to read public-transport stops around a postcode (and what density means)

Having dozens of bus stops doesn't automatically mean a place is great for commuters. A postcode's public transport count is only useful when you know what kind of neighborhood produced it.
Updated:
14 July 2026
Read time:
4 min
Share:XFacebookLinkedIn
Map of Switzerland

What density tells you

I often see people assume that a high number of transport stops guarantees an easy commute. It doesn't. A high stop count is just a proximity signal.

For example, 8001 Zurich has 49 recorded public-transport stops, and 8050 Zurich (Oerlikon) has 44. That makes perfect sense for a dense city center and a major northern hub. But 8702 Zollikon, an affluent suburb right next to Zurich, has only 16 stops. Meanwhile, 8048 Zurich (Altstetten) has 41.

This comparison immediately exposes the limits of counting stops. Zollikon can be a fantastic commuter location, despite having fewer stops, if the specific bus or train lines run directly to your office. Altstetten might look vastly superior on paper simply because its larger urban footprint overlaps with dozens of different tram and bus routes.

Map of Switzerland
Image: Switzerland-map.png, via Wikimedia Commons.

What the raw numbers leave out

Stop density completely ignores frequency, transfer times, and the actual walking distance from your front door to the platform. A neighborhood with 49 stops isn't automatically better than one with 16 if those 16 stops include a direct, high-speed S-Bahn connection that gets you to work in ten minutes.

I see the opposite mistake happen all the time when people look at towns outside the big cities. 1260 Nyon has 52 stops. That looks strong! But the takeaway isn't just "Nyon wins." The takeaway is that Nyon is a fully developed regional hub with a dense bus network feeding into its rail station. The question becomes whether your specific apartment sits on one of those useful bus corridors.

Conversely, 6203 Sempach Station has only 5 stops. But one of those stops is the actual railway station. For many commuters, living a five-minute walk from a reliable train is far better than having thirty bus stops scattered randomly across town.

Zurich main station
Image: Zuerich_Hauptbahnhof-2.jpg, via Wikimedia Commons.

How to read the data

To get real value out of these numbers, start by comparing a dense postcode with a leaner alternative in the same region. Comparing 8001 Zurich against 8702 Zollikon works because they share the same metropolitan area. Comparing 1260 Nyon against 6203 Sempach Station helps you understand the difference between a full-service regional center and a small commuter village.

When you look at a PLZHub page, combine these three things:

  1. The raw stop count.
  2. The type of postcode (is it a city core, a sprawling suburb, or a small village?).
  3. The nearby postcodes and major rail nodes surrounding it.

When to stop using PLZHub

That method is great for answering high-level questions like, "Do I want a dense city network or a quiet village with one good train station?"

It is completely useless for answering, "How long is my morning commute from this specific apartment?" Once you find an apartment you like, stop looking at PLZHub. Open the SBB app, type in the exact street address, and check the door-to-door timetable for a Tuesday morning at 7:30 AM.

What to look at first

Horizontal scroll to compare values

PointWhat to checkWhy it helps
Starting point/plz/8001-zurichKeeps the comparison in the right context
Relevant data`oev stops by PLZ`, `centroid`, `nearbyPlz`Keeps the focus on the signals that carry the answer
Follow-up pages/blog/how-to-use-plzhub-data-and-where-it-stops, /methodologyAdds context without scattering the reading
VerificationOfficial source or timetableStill needed once the decision is real

How to use this comparison

  • Open /plz/8001-zurich first and read the starting context there.
  • Use only the data points that answer the question.
  • Add one or two focused follow-up pages instead of reading everything in parallel.
  • Check the final step against an official source.
Blog

Selected articles from the PLZHub blog