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-08-18
93.9%
2025-08-19
100%
2025-08-20
100%
2025-08-21
100%
2025-08-22
100%
2025-08-23
100%
2025-08-24
100%
2025-08-25
100%
2025-08-26
100%
2025-08-27
100%
2025-08-28
100%
2025-08-29
100%
2025-08-30
100%
2025-08-31
100%
2025-09-01
100%
2025-09-02
100%
2025-09-03
100%
2025-09-04
100%
2025-09-05
100%
2025-09-06
99.4%
2025-09-07
100%
2025-09-08
100%
2025-09-09
100%
2025-09-10
53.2%
2025-09-11
70.2%
2025-09-12
79.7%
2025-09-13
17%
2025-09-14
79.5%
2025-09-15
89.5%
2025-09-16
0.5%
2025-09-17
0%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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-09-15 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 128 | 21 times (78 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 256 | 21 times (78 % of validations) |
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 22 | 18 times (67 % of validations) |
E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 22 | 18 times (67 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 22 | 18 times (67 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 22 | 18 times (67 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 12 | 12 times (44 % 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 | 4 times (15 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 6 | 1 times (4 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 | 1 times (4 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 9 | 1 times (4 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.