Loading the map…
TMB arrivals are forecasts, and their markers are positions estimated by this app. FGC's square markers start from the position published by Geotren at each query; between stations we estimate their progress to the next published stop using the scheduled time of the section, and we label it “Estimated movement”. A train published at a station stays there.
We match service codes between stations and calculate forecast times for each section. At terminals we link the arrival with the return trip to represent the stop and the departure towards the next station. If a terminal's departure times are missing, we estimate its first section using the times of the same route in the opposite direction, when available. We interpolate the movement along the TMB alignment. On metro lines we bring the countdown forward by 40 seconds relative to the published time. We show “Arriving” for 12 seconds and “At platform” for 28 seconds, until that time, and “Departing” for the 15 seconds after the stop. These are estimated phases; actual stops, accelerations and forecast changes may differ from the animation.
Select a station to see up to six trains per line, with both directions ordered by arrival. Arrivals stay visible during the stop and the departure. These arrivals are TMB forecasts, also for services we cannot place on the map. On L9 and L10, if forecasts are missing for a station and direction, we show TMB times labelled Scheduled timetable. On these branches we also simulate trains by linking the timetables of consecutive stations, with the same stops and phases. Their markers have a dashed border and their card says “Scheduled timetable”. Timetables do not identify physical trains: the routes are approximate. If there are real forecasts for a line and direction, they take priority. Map coverage is partial: we only show services we can place with the available data. The dots in the legend show which lines have forecasts in the current query. We query TMB roughly every 25 seconds and FGC every minute while you visit the page, and we discard TMB data older than two minutes. Geotren publishes the FGC dataset at a different pace: we accept up to four minutes since its publication, provided we downloaded it within the last two minutes. The age of the dataset appears next to the FGC status.
FM is the Montjuïc funicular, between Paral·lel and Parc de Montjuïc. Its arrivals depend on the forecasts published by TMB; if they are unavailable, we keep the route and the stations.
FGC includes Barcelona–Vallès, Llobregat–Anoia, Lleida–La Pobla, the Montserrat and Núria rack railways, the Vallvidrera, Gelida, Sant Joan and Santa Cova funiculars, and the Cement Train. Tourist services without downloadable timetables link to FGC's official information. When you select a train you can check the series and the per-car occupancy published by FGC. Missing data is shown as “No data”. Station cards show up to four upcoming departures, combining official timetables with GTFS Realtime forecasts. Each time is labelled “Scheduled” or “Real time” and shows the published track. Arrivals that terminate there can be found under “Terminating arrivals”. We download the timetable once a day; forecasts and positions have independent sources and expiry times. Geotren does not publish the orientation of the cars on the platform; we do not infer it. Services with a Geotren code that has no exact match in the GTFS keep their name and published position, without being assigned the route of another line. The timestamps of the TMB query and of the FGC dataset do not indicate the last physical observation of each train.
Renfe includes the 19 Rodalies and regional lines of Catalonia, with stations and routes from the official GTFS. Shared corridors are drawn only once and separate at the junctions. The cards show the scheduled departures and delays published by Renfe, according to the stops of each service. Circular markers show the GPS positions published by Renfe every 20 seconds; select one to see the destination, status and track when available. The card includes upcoming stops and arrival times, distinguishing published forecasts, delay-based estimates and scheduled times. We estimate progress between queries when the GPS and the next arrival are compatible with the route. Trains reported as stopped stay still. The projection continues until the expected arrival at the next stop, and positions are removed two minutes after their observation or the publication of the dataset. Check the current timetables and disruptions before you travel.
TRAM includes T1–T6, with routes and stops from the official Trambaix and Trambesòs GTFS. We query TRAM OpenData every 30 seconds to show vehicles, occupancy and arrival times. Its diamond markers move along the route in an estimated way, linking the published position with the upcoming arrivals. If there is no compatible position, we simulate the trip using the times of consecutive stations and indicate it on its card and with a dashed border. We allow 30 seconds for each stop and correct the route at every query. The locations in the animation are approximate. Published times may match the scheduled timetable: we do not infer entry or exit phases. We discard data after two minutes without a valid query. The age shows when the API was queried; TRAM does not provide the observation time of each vehicle. Separate routes are drawn without joining them; the cards point out those breaks.
TMB and AMB buses show when turned on with the bus button or when searching for a stop or line. Stops, routes and variants come from TMB Transit and official AMB Mobilitat GTFS, including published night bus lines. When you press a stop we query iBus and AMB GTFS-RT, depending on coverage, every 30 seconds while its sheet is open. Each source keeps its own age and expiry. Bus positions are not drawn and the planner remains rail-only.
