Tracking Trains Without an App: Live Tracking Right in Your Browser

Updated: August 2026 – Tracking trains without an app isn’t a stopgap; in many situations it’s the more practical route: a full phone, a work device with no installation rights, someone else’s laptop or simply no desire for yet another icon. This guide shows which web routes there are, where they reach their limits and how to get the convenience of an app without installing one, using a home-screen shortcut.

Tracking trains without an app: does it really work?

Yes – completely. All the data a tracking app displays comes from timetable and real-time interfaces, and the same interfaces also feed web services. Whether you call up a journey in an app or in the browser makes no difference to the data source: train number, route, stops and delay forecast are identical if the same source is behind them.

The difference lies elsewhere, namely in how the access route behaves. A web page only lives while it’s open. It can’t notify you while your screen is off, it keeps nothing offline, and it has only limited access to the camera and location. For the question “where is my train right now?”, that’s irrelevant. For everything that comes after, it isn’t. The overview of live tracking for trains and buses puts the general landscape of tools in context.

Which web routes there are – and what they can do

Not every web service answers the same question. This overview groups the types by purpose, not by provider.

Type	What you see there	Strength in the browser	Typical weakness on mobile
Departure and arrival board	Next departures from a station, delay, platform	Very fast, very data-efficient	No spatial overview
Operator journey planner	A specific journey with stops and forecast	Level of detail, disruption notices	Many steps on a small screen
Regional transport association planner	Local services in the association’s area	Dense regional data, good information on replacement services	Ends at the association’s boundary
Map and radar view	Journeys as symbols on the map	Spatial overview at a glance	High data and battery usage
Disruption and engineering works pages	Current restrictions on a line	Context the live map doesn’t provide	Often text-heavy and rarely optimised for mobile
Community and sighting sites	What others have actually seen	Vehicle-based rather than just journey-based	Depends on whether anyone has reported

For the regional level, it’s worth looking at the guide on how to find live departures from regional transport associations. And if you’re mainly interested in the map view, the comparison of the best train radar tools and maps helps you choose.

Why the data chain matters more than the interface

A pretty map without a reliable source is worthless, whereas a plain table with clean real-time data is extremely useful. So check with every web service: does it say where the data comes from? Is there a full legal notice (Impressum)? How often does the page visibly update? This exact checking logic is covered in detail in the article on Zugradar-24-style services and their alternatives.

What the browser does differently on a phone

Three technical differences explain almost every moment of frustration with mobile browser tracking.

• No background operation: If you lock the screen or switch apps, the page freezes. When you return, you may see an outdated state without being told.
• No notifications: You only find out about a change in delay if you check yourself. For passengers on the platform that’s manageable; for planning photos at a spot, it’s a nuisance.
• Higher usage with maps: Every zoom level and every pan loads new map tiles. Over a long session, that adds up far more than a pure text query.

Browser or app? The honest comparison

Home-screen shortcut: the app that isn’t one

The best compromise between browser and app costs you thirty seconds of setup. You put the website on your home screen as an icon and from then on launch it with a single tap – no installation, no store, no significant storage requirement.

If you take the browser route permanently, the guide to trainspotting tools and hotspots online has more places to go, and the article on the trainspotter website shows how a good web resource should be built.

Keeping data usage and battery under control

On a long outing, the problem isn’t the quality of the data but the battery. Browser tracking is no special case here, but it’s easy to manage once you know what really draws power and data.

The biggest consumer is the map view. Every zoom level loads new tiles, so does every pan, and the display keeps the screen permanently bright. If you leave a map open for hours, you’ll notice it both in your data allowance and in your remaining battery. A departure board, by contrast, essentially transmits text and is therefore orders of magnitude more frugal.

The second-biggest consumer is automatic reloading. Some pages refresh themselves at short intervals. That’s handy on the platform and annoying on a four-hour outing. If you have the choice, only turn on automatic refreshing when you’re really waiting for a particular journey.

Three habits reliably help:

• Close tabs instead of collecting them. Open map tabs start working again as soon as you switch back, and then reload everything.
• Check once before the outing instead of ten times on the way. The timetable rarely changes; the forecast only does shortly before the journey.
• Reduce screen brightness. With a map in sunlight, that’s the single biggest lever of all.

If you’re regularly out for long periods, you won’t get by without a power bank anyway – the browser makes things neither better nor worse than an app, it just gives you fewer ways to limit consumption.

When the app is still the better choice

For comparing the app side, it’s worth looking at the guide to the trainspotter app and its features. And if you want to know in principle what using it costs: you’ll find an overview on the pricing page.

What to watch out for with browser tracking

• Check how current it is, don’t assume. Many pages show no timestamp. Reload before you base a decision on a display.
• Note the train number rather than remembering a symbol. When you close the tab, the selection is gone. The number remains. How to carry on working with it is shown in the guide on how to follow a moving train.
• Check the disruption situation separately. Live maps show journeys, not causes. For engineering works and diversions you need a separate source, such as the guide to the DB Streckenagent for disruptions and diversions.
• Keep an eye on data usage. A permanently open map view is the biggest consumer on a spotting outing.
• Don’t rely on displays when it matters. If the page hasn’t moved for minutes, that’s no proof that the train is standing still.
• Only share your location when necessary. For a simple departure query, entering the station manually is enough – that saves battery and avoids unnecessary permissions.

Conclusion

Tracking trains without an app works completely, as long as it’s about the journey itself: departure, delay, route, approximate position. The browser only loses out where background operation, notifications and documentation begin. If you separate the two sensibly – browser for quick checks, app for everything that should last – you get the best of both worlds without cluttering up your phone.