Resource details

File name: Horaires temps réel des lignes du réseau TUB
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain TUB.

Download availability

2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
100%
2025-04-03
100%
2025-04-04
100%
2025-04-05
100%
2025-04-06
100%
2025-04-07
100%
2025-04-08
100%
2025-04-09
100%
2025-04-10
100%
2025-04-11
100%
2025-04-12
100%
2025-04-13
100%
2025-04-14
100%
2025-04-15
100%
2025-04-16
100%
2025-04-17
100%
2025-04-18
100%
2025-04-19
100%
2025-04-20
100%
2025-04-21
100%
2025-04-22
100%
2025-04-23
100%
2025-04-24
100%
2025-04-25
100%
2025-04-26
100%
2025-04-27
100%
Learn more
We test this resource download availability every hour by making an HTTP HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.

For SIRI and SIRI Lite feeds, we perform a GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-27 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.

Validate this GTFS-RT now

Previous validations

Here is a recap of all the error types encountered over the last 30 days.

Error ID Description Errors count Number of occurences
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 161 23 times (77 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 322 23 times (77 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 25 22 times (73 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 25 22 times (73 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 25 22 times (73 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 25 22 times (73 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 9 9 times (30 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 4 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-27 at 09:10 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-27 at 09:10 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1745737852" } }