Track SBB trains live: train tracking in Switzerland

Updated: August 2026 – SBB live tracking works technically just like everywhere else in Europe – and still feels different. The reason is the integrated clock-face timetable: where connections repeat precisely every hour and connections are bundled at hubs, you need a live query less often and an understanding of the underlying pattern more often. This guide shows you both.

Tracking SBB trains live: the short answer

You track a Swiss train live by entering its train number into a real-time enquiry, choosing today’s date, and expanding the full run. That gives you the stops along with scheduled and actual times – the information everything in rail traffic hinges on.

The second part of the answer is typically Swiss: you need the live query less often than you’d think. Because the timetable is clock-faced, you can infer the next hour from one known connection. Live data then becomes mainly a tool for deviations – delays, track changes, cancellations. How much this way of thinking differs from everyday practice in Germany becomes clear as soon as you set the two systems side by side; the general mechanics behind it are explained in the article can you track trains live.

Why the clock-face timetable changes tracking

An integrated clock-face timetable arranges all traffic around a small number of hub times. Trains arrive there within a tight window, exchange passengers and depart together again. For you as an observer this has three concrete consequences:

• Predictability instead of constant querying. Once you know the pattern, you know it for the whole day. That replaces many live queries.
• Dense time windows at hubs. Around the hub time, a lot happens at once – ideal for observation, demanding for photo planning.
• Delays have a stronger effect. Because connections are tightly interlocked, a deviation has noticeably more visible consequences than in an untimed network.

That’s exactly why the pure map view is often less useful in Switzerland than the departure board of a hub station: there you see the whole bundling at a glance instead of individual points on a line.

Reading Swiss train numbers

The basic numbering rules are European in origin and therefore work similarly to the German and Austrian networks:

• Number of digits roughly indicates the service tier – short numbers tend to be long-distance, longer ones regional and S-Bahn services.
• Parity separates the directions: even one way, odd the other.
• Number ranges belong to line families, which is why related runs are often close together.
• Category codes stand for the service tier, not the vehicle type.

Anyone who has learned this system on the German network can carry it over without relearning – the article on decoding train numbers for ICE, IC, RE and RB explains it in detail. And how the same logic applies in neighbouring Austria is shown in the guide to ÖBB train radar and live tracking in Austria.

An overview of data sources for Switzerland

Rather than recommending individual apps whose feature set keeps changing, it’s worth looking at the types of sources and their respective limits.

Source type	What it typically delivers	Strength	Typical limit
Operator’s enquiry	Train run, stops, actual times	Close to actual operations	Focused on its own services
Regional transport authority enquiry	S-Bahn, regional services, connections	Dense coverage in conurbations	Ends at the authority’s boundary
Third-party maps	Position display across country borders	Good overall view	Coverage varies, data sometimes delayed
Station departure board	Track, actual time, short-term changes	Most up-to-date source on site	Only the current station
Community sightings	Formation, special workings, diversions	Answers vehicle questions	Depends on active observers

Which mapping tools are suitable for cross-border observation is set out in the comparison of the best train radar tools. It’s also worth noting that not every Swiss service comes from SBB: in the canton of Graubünden, the Rhaetian Railway runs on its own metre-gauge network.

Step by step: tracking an SBB train

Cross-border traffic: Basel and Schaffhausen as a practical case

At the crossings between the German and Swiss networks, two operational and data worlds meet. Basel is the best-known example: services from both networks converge here, and depending on which part of the station you’re in, different areas of responsibility apply. Schaffhausen is the second classic case, because the region is geographically interlocked and services switch networks several times.

For your tracking, this concretely means: a through working can be represented differently in two systems – with its own number, its own delay calculation and its own display endpoint. If you use only one source, you’ll regularly see a train “end” that in reality carries on.

In freight traffic this is even more pronounced: SBB Cargo International runs through trains between Northern Europe and Italy, crossing several national systems along the way. A train from Hupac, on the other hand, you recognise by the wagons, not by the locomotive at the front.

Thinking in hubs instead of in lines

The biggest difference for German spotters is more conceptual than technical. In an untimed network, you think in lines: you look for a section with a lot of traffic and wait there. In a clock-face network, you think in hubs: you look for the station where connections bundle together and plan around its hub time.

The practical advantage is considerable. Around a hub time, you see services from several directions within a few minutes, sometimes with different vehicle families. Afterwards it gets noticeably quieter for a good half hour – time to review your shots, log sightings, or change location.

Three things you should clarify beforehand:

• What hub time applies at your station? It results from the arrival and departure minutes of the main services and repeats reliably.
• Which directions do services converge from? The more feeder lines, the greater the vehicle variety in the same time window.
• Where can you stand without being in the way? At hubs there’s a lot of passenger movement at the hub time. A spot at the platform end is usually quieter than the middle – and still remains publicly accessible.

Anyone who plans this way needs far fewer live queries and still sees more. That’s the real trick to the Swiss system.

Conversely: between two hub times, a lineside position is often the worse choice, because simply little happens there. If you want to change location between the windows, plan the move deliberately into this quiet phase – then you’ll already be at the new point for the next hub time and won’t lose any subjects.

What to watch out for

• Only looking at the map. In a clock-face network, the departure board of a hub tells you more than a single point on a line.
• Using product names as a search term. Without a specific train number, you won’t get a definite result.
• Assuming coverage. Hardly any source documents which area it covers. Test it beforehand with a working you already know.
• Querying cross-border traffic with only one source. That’s the most common reason for seemingly vanished trains, as the look at German border hubs in the trainspotter guide for Aachen and cross-border traffic also shows.
• Downplaying safety. Track areas and operational installations are off limits in Switzerland too. The legal basics for the DACH region are set out in the article on whether trainspotting is legal.
• Not logging sightings. Vehicle and formation data isn’t in any enquiry – if you don’t note it, you lose it. How this can be combined with other modes of transport is described in the overview of live tracking for trains and buses.

What spotters from Germany should bring with them

The adjustment is smaller than many expect. The tools are the same, only the emphasis shifts: less live querying, more clock-face understanding. If you’ve previously spotted in Germany, you can largely carry over your routine – the trainspotter guide for Germany describes the basics that also hold beyond the border. Essentially three things are new: thinking in hubs, the second data source for cross-border traffic, and the willingness to document formations yourself.

Comparing numbering with the Austrian network is more useful than it sounds: once you understand the logic of the ÖBB tracking number, you’ll immediately recognise the shared European base structure.

Conclusion

Train tracking in Switzerland is less a matter of the right map than a matter of the right mental model. The clock-face pattern supplies the structure, the train number gives you access to the individual working, the actual time gives you the reliable figure – and at the border you simply need a second source. If you work this way, you’ll be at the hub at the right minute and won’t be puzzled by trains that suddenly disappear from the display.