Resource details
Avance retard à un arrêt
This resource file is part of the dataset Réseau urbain TBK.
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
❌90 errors, 21 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-04 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt route_id does not exist in GTFS data E004 77 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 5f0efab961de832d70f03fd1 route_id 222-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f28f161de832d70f1414b route_id 211-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f28a061de832da97c0b7f route_id 1-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f269e61de832d70f134c3 route_id 300-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f080b6b43f0854b56c48d64 route_id 7-652 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 3 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 21454436 stop_sequence 29 arrival_time 07:58:14 (1764831494) is equal to previous stop arrival_time 07:58:14 (1764831494) - times must increase between two sequential stops
- trip_id 21454904 stop_sequence 11 arrival_time 07:32:01 (1764829921) is less than previous stop arrival_time 07:35:29 (1764830129) - times must increase between two sequential stops
- trip_id 21454904 stop_sequence 11 departure_time 07:34:40 (1764830080) is less than previous stop arrival_time 07:35:29 (1764830129) - times must increase between two sequential stops
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 21454904 stop_sequence 10 departure_time 07:31:48 (1764829908) is less than the same stop arrival_time 07:35:29 (1764830129) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 9 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 21454887 stop_sequence 1 doesn't have arrival or departure
- trip_id 21454887 stop_sequence 2 doesn't have arrival or departure
- trip_id 21454436 stop_sequence 22 doesn't have arrival or departure
- trip_id 21454436 stop_sequence 23 doesn't have arrival or departure
- trip_id 21454436 stop_sequence 24 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 21 errors
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 21454904 is in TripUpdates but not in VehiclePositions feed
- trip_id 21454947 is in TripUpdates but not in VehiclePositions feed
- trip_id 21455117 is in TripUpdates but not in VehiclePositions feed
- trip_id 21455041 is in TripUpdates but not in VehiclePositions feed
- trip_id 21454436 is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 613 | 25 times (83 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 954 | 22 times (73 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 432 | 21 times (70 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 128 | 19 times (63 % 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. | 61 | 19 times (63 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 9 | 7 times (23 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 3 | 3 times (10 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 6 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-04 at 21:00 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-04 at 21:00 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764878435"
}
}