Resource details
This resource file is part of the dataset Réseau urbain TUB.
Download availability
Learn more
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
❌1 error, 22 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-17 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 3-326107155 stop_sequence 17 departure_time 07:56:00 (1763362560) is less than the same stop arrival_time 07:56:04 (1763362564) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 7 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 3-304906479 does not have a vehicle_id
- trip_id 3-838926338 does not have a vehicle_id
- trip_id 3-282263554 does not have a vehicle_id
- trip_id 3-299040772 does not have a vehicle_id
- trip_id 3-304972014 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 1 min 42 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 14 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 3-304906479 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3-304906479 does not have a schedule_relationship
- trip_id 3-838926338 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3-838926338 does not have a schedule_relationship
- trip_id 3-282263554 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 | 200 | 24 times (80 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 400 | 24 times (80 % 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. | 9 | 7 times (23 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 6 | 6 times (20 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 8 | 4 times (13 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 8 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-17 at 21:33 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-11-17 at 21:33 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1763411584"
}
}