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, 17 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-24 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt route_id does not exist in GTFS data E004 69 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 5f0f269e61de832d70f134c3 route_id 300-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f080b9f43f0854b19776f1b route_id K-652 does not exist in the GTFS data routes.txt
- vehicle_id 5f0f290e61de832dc80ca991 route_id 212-652 does not exist in the GTFS data routes.txt
- vehicle_id e9563d7b24213ff9 route_id 290-652 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 11 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 21455112 stop_sequence 27 arrival_time 07:43:03 (1763966583) is less than previous stop departure_time 08:04:40 (1763967880) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 28 arrival_time 07:45:30 (1763966730) is less than previous stop departure_time 08:11:40 (1763968300) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 29 arrival_time 07:46:49 (1763966809) is less than previous stop departure_time 08:14:22 (1763968462) - times must increase between two sequential stops
- trip_id 21455112 stop_sequence 30 arrival_time 07:51:54 (1763967114) is less than previous stop departure_time 08:16:13 (1763968573) - times must increase between two sequential stops
- trip_id 21454443 stop_sequence 26 arrival_time 07:30:11 (1763965811) is less than previous stop departure_time 07:30:17 (1763965817) - 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 21454443 stop_sequence 27 departure_time 07:32:29 (1763965949) is less than the same stop arrival_time 07:32:32 (1763965952) - departure time must be equal to or greater than arrival time
- trip_id 21454904 stop_sequence 10 departure_time 07:32:48 (1763965968) is less than the same stop arrival_time 07:35:31 (1763966131) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 8 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 3 doesn't have arrival or departure
- trip_id 21454443 stop_sequence 14 doesn't have arrival or departure
- trip_id 21454443 stop_sequence 20 doesn't have arrival or departure
- trip_id 21454947 stop_sequence 18 doesn't have arrival or departure
- trip_id 21454947 stop_sequence 19 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 17 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 | 1 205 | 23 times (77 % 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 | 332 | 20 times (67 % 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 | 766 | 18 times (60 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 91 | 13 times (43 % 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. | 34 | 13 times (43 % 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. | 10 | 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 | 6 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-24 at 20:36 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-24 at 20:36 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764012995"
}
}