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
❌120 errors, 16 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-18 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt route_id does not exist in GTFS data E004 68 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 5f0f290e61de832dc80ca991 route_id 212-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f080b8843f0854ae642aae1 route_id K-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f28d461de832d70f140b5 route_id 2-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 5f0f28a061de832da97c0b7f route_id 1-652 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 5 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 21455033 stop_sequence 2 arrival_time 07:44:22 (1763448262) is less than previous stop departure_time 07:44:27 (1763448267) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 27 arrival_time 07:42:19 (1763448139) is less than previous stop departure_time 08:04:10 (1763449450) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 28 arrival_time 07:44:55 (1763448295) is less than previous stop departure_time 08:11:10 (1763449870) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 30 arrival_time 07:50:43 (1763448643) is less than previous stop arrival_time 08:15:43 (1763450143) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 30 arrival_time 07:50:43 (1763448643) is less than previous stop departure_time 08:15:43 (1763450143) - times must increase between two sequential stops
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 5f080b5e43f0854ae642aa24 trip_id 21455048 at (47.872116,-3.5529938) 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 46 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 21454442 stop_sequence 30 doesn't have arrival or departure
- trip_id 21454442 stop_sequence 31 doesn't have arrival or departure
- trip_id 21454420 stop_sequence 8 doesn't have arrival or departure
- trip_id 21454440 stop_sequence 4 doesn't have arrival or departure
- trip_id 21454440 stop_sequence 6 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 16 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 21454406 is in TripUpdates but not in VehiclePositions feed
- trip_id 21454890 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 | 971 | 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 | 292 | 22 times (73 % 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 | 719 | 14 times (47 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 84 | 12 times (40 % 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. | 30 | 10 times (33 % 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 | 6 times (20 % 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-18 at 21:43 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-18 at 21:43 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1763498595"
}
}