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
❌118 errors, 19 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-27 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt route_id does not exist in GTFS data E004 79 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 5f0f29e061de832d61873c85 route_id 221-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 5f0f292061de832d9695cb0b route_id 213-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f080b9443f0854b6554ba4a route_id K-652 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 14 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 21454443 stop_sequence 25 arrival_time 07:31:42 (1764225102) is less than previous stop arrival_time 07:51:28 (1764226288) - times must increase between two sequential stops
- trip_id 21454443 stop_sequence 25 departure_time 07:33:07 (1764225187) is less than previous stop arrival_time 07:51:28 (1764226288) - times must increase between two sequential stops
- trip_id 21454443 stop_sequence 26 arrival_time 07:33:05 (1764225185) is less than previous stop departure_time 07:33:07 (1764225187) - times must increase between two sequential stops
- trip_id 21454904 stop_sequence 11 arrival_time 07:31:37 (1764225097) is less than previous stop arrival_time 07:34:45 (1764225285) - times must increase between two sequential stops
- trip_id 21454904 stop_sequence 11 arrival_time 07:31:37 (1764225097) is less than previous stop departure_time 07:31:48 (1764225108) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 7 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 21454443 stop_sequence 24 departure_time 07:30:53 (1764225053) is less than the same stop arrival_time 07:51:28 (1764226288) - departure time must be equal to or greater than arrival time
- trip_id 21454443 stop_sequence 29 departure_time 07:38:34 (1764225514) is less than the same stop arrival_time 07:38:40 (1764225520) - departure time must be equal to or greater than arrival time
- trip_id 21454443 stop_sequence 30 departure_time 07:40:45 (1764225645) is less than the same stop arrival_time 07:41:13 (1764225673) - departure time must be equal to or greater than arrival time
- trip_id 21454443 stop_sequence 31 departure_time 07:41:36 (1764225696) is less than the same stop arrival_time 07:41:58 (1764225718) - departure time must be equal to or greater than arrival time
- trip_id 21454443 stop_sequence 32 departure_time 07:42:20 (1764225740) is less than the same stop arrival_time 07:42:36 (1764225756) - 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 5f0f271a61de832db9874274 trip_id 21455142 at (47.96537,-3.5014656) 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 17 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 21454440 stop_sequence 1 doesn't have arrival or departure
- trip_id 21454440 stop_sequence 4 doesn't have arrival or departure
- trip_id 21454952 stop_sequence 3 doesn't have arrival or departure
- trip_id 21454952 stop_sequence 4 doesn't have arrival or departure
- trip_id 21454952 stop_sequence 5 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 19 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 400 | 24 times (80 % 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 | 379 | 21 times (70 % 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 | 916 | 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. | 112 | 16 times (53 % 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. | 43 | 16 times (53 % 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. | 11 | 8 times (27 % 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 | 6 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-27 at 20:48 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-11-27 at 20:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764272936"
}
}