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
❌115 errors, 26 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-08 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt route_id does not exist in GTFS data E004 92 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 5f0f29c261de832d848b0a99 route_id 10-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f29cb61de832da97c0fa3 route_id 150-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f292061de832d9695cb0b route_id 211-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f28bc61de832d618738ad route_id 2-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f27ab61de832d618735a8 route_id 160-652 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 7 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 21455152 stop_sequence 9 arrival_time 08:07:38 (1765177658) is less than previous stop arrival_time 08:15:20 (1765178120) - times must increase between two sequential stops
- trip_id 21455152 stop_sequence 9 arrival_time 08:07:38 (1765177658) is less than previous stop departure_time 08:15:20 (1765178120) - times must increase between two sequential stops
- trip_id 21454921 stop_sequence 15 arrival_time 07:50:27 (1765176627) is less than previous stop departure_time 08:09:20 (1765177760) - times must increase between two sequential stops
- trip_id 21454921 stop_sequence 16 arrival_time 07:54:25 (1765176865) is less than previous stop departure_time 08:11:20 (1765177880) - times must increase between two sequential stops
- trip_id 21454436 stop_sequence 29 arrival_time 08:02:22 (1765177342) is equal to previous stop departure_time 08:02:22 (1765177342) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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 21454907 stop_sequence 1 departure_time 08:02:20 (1765177340) is less than the same stop arrival_time 08:02:25 (1765177345) - departure time must be equal to or greater than arrival time
- trip_id 21454904 stop_sequence 10 departure_time 07:31:18 (1765175478) is less than the same stop arrival_time 07:35:44 (1765175744) - departure time must be equal to or greater than arrival time
Vehicle position far from trip shape E029 1 error
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.
Sample errors
- vehicle.id 5f0f29cb61de832da97c0fa3 trip_id 21455126 at (47.866817,-3.6159937) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
stop_time_update doesn't have arrival or departure E043 12 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 21454921 stop_sequence 2 doesn't have arrival or departure
- trip_id 21454921 stop_sequence 3 doesn't have arrival or departure
- trip_id 21454894 stop_sequence 1 doesn't have arrival or departure
- trip_id 21454947 stop_sequence 1 doesn't have arrival or departure
- trip_id 21454947 stop_sequence 2 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 21742036 and vehicle_id 5f0f27ab61de832d618735a8 pairing in VehiclePositions does not match trip_id 21454844 and vehicle_id 5f0f27ab61de832d618735a8 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 26 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 21455125 is in TripUpdates but not in VehiclePositions feed
- trip_id 21455129 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 538 | 24 times (80 % 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 | 860 | 21 times (70 % 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 | 407 | 20 times (67 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 108 | 18 times (60 % 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. | 60 | 18 times (60 % 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. | 7 | 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. | 2 | 2 times (7 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-08 at 21:30 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-08 at 21:30 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765225808"
}
}