Resource details
This resource file is part of the dataset Réseau urbain Kicéo.
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
❌3,052 errors, 1,193 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-04 at 08:17 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 24 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:b63ae62c-dd08-4c0a-b966-8df89fe347b1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:54c6fce1-2edd-4c29-b936-efb19a9d04fb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:1267fcef-9e99-44f6-bfa8-33b9e7d96560:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 24 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id BSAScol61137 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- route_id AVBLigne608 does not exist in the GTFS data routes.txt
- route_id MorioLigne602 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 172 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_id bre_vannes_2024_2025.17961 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_id bre_vannes_2024_2025.21335 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_id bre_vannes_2024_2025.17959 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_id bre_vannes_2024_2025.18097 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_id bre_vannes_2024_2025.18051 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2,826 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 2-336134203 stop_sequence 46 arrival_time 07:16:42 (1770185802) is less than previous stop arrival_time 08:19:01 (1770189541) - times must increase between two sequential stops
- trip_id 2-336134203 stop_sequence 46 arrival_time 07:16:42 (1770185802) is less than previous stop departure_time 08:19:01 (1770189541) - times must increase between two sequential stops
- trip_id 2-121765904 stop_sequence 34 arrival_time 08:25:59 (1770189959) is equal to previous stop arrival_time 08:25:59 (1770189959) - times must increase between two sequential stops
- trip_id 2-121765904 stop_sequence 34 arrival_time 08:25:59 (1770189959) is equal to previous stop departure_time 08:25:59 (1770189959) - times must increase between two sequential stops
- trip_id 2-121765904 stop_sequence 34 departure_time 08:25:59 (1770189959) is equal to previous stop departure_time 08:25:59 (1770189959) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 6 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 2-73203738 stop_sequence 21 departure_time 08:15:13 (1770189313) is less than the same stop arrival_time 08:16:36 (1770189396) - departure time must be equal to or greater than arrival time
- trip_id 2-52887560 stop_sequence 25 departure_time 08:16:47 (1770189407) is less than the same stop arrival_time 08:17:07 (1770189427) - departure time must be equal to or greater than arrival time
- trip_id 2-34144359 stop_sequence 14 departure_time 08:16:12 (1770189372) is less than the same stop arrival_time 08:16:35 (1770189395) - departure time must be equal to or greater than arrival time
- trip_id chouette:VehicleJourney:6dc9bb81-7329-4ab1-8016-db64eb16ced0:LOC stop_sequence 3 departure_time 08:16:13 (1770189373) is less than the same stop arrival_time 08:16:28 (1770189388) - departure time must be equal to or greater than arrival time
- trip_id 22-3172532227-AFF-6-__CJV__ stop_sequence 4 departure_time 08:15:59 (1770189359) is less than the same stop arrival_time 08:16:44 (1770189404) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 678 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 22-453050369 does not have a timestamp
- trip_id 2-336134203 does not have a timestamp
- trip_id 22-2248343553 does not have a timestamp
- trip_id 2-251854853 does not have a timestamp
- trip_id 2-73203735 does not have a timestamp
vehicle_id not populated W002 515 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-336134171 does not have a vehicle_id
- trip_id 2-34144340 does not have a vehicle_id
- trip_id 2-33620052 does not have a vehicle_id
- trip_id 2-34144339 does not have a vehicle_id
- trip_id 2-33620051 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 15,831 | 27 times (93 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 12,394 | 27 times (93 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 818 | 25 times (86 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 469 | 25 times (86 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3,341 | 25 times (86 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 67,736 | 25 times (86 % 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. | 148 | 23 times (79 % of validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 1,358 | 14 times (48 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 130 | 13 times (45 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-05 at 05:20 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-02-05 at 05:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770265257"
}
}