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 037 errors, 1 237 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-17 at 08:04 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 25 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:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527: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: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
GTFS-rt route_id does not exist in GTFS data E004 21 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id BSAScol61133 does not exist in the GTFS data routes.txt
- route_id MAURYLigne609 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- route_id BSAScol61137 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 151 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.21335 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.17963 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.21337 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.17969 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id keoskol.11214710 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2 837 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:11:30 (1765951890) is less than previous stop arrival_time 08:19:34 (1765955974) - times must increase between two sequential stops
- trip_id 2-336134203 stop_sequence 46 arrival_time 07:11:30 (1765951890) is less than previous stop departure_time 08:19:34 (1765955974) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:12:57 (1765955577) is equal to previous stop arrival_time 08:12:57 (1765955577) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:12:57 (1765955577) is equal to previous stop departure_time 08:12:57 (1765955577) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 departure_time 08:12:57 (1765955577) is equal to previous stop departure_time 08:12:57 (1765955577) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 3 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-288161794 stop_sequence 8 departure_time 08:04:03 (1765955043) is less than the same stop arrival_time 08:04:26 (1765955066) - departure time must be equal to or greater than arrival time
- trip_id 22-1912668161 stop_sequence 4 departure_time 08:02:45 (1765954965) is less than the same stop arrival_time 08:03:56 (1765955036) - departure time must be equal to or greater than arrival time
- trip_id 22-1912668161 stop_sequence 5 departure_time 08:03:45 (1765955025) is less than the same stop arrival_time 08:03:57 (1765955037) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 696 errors
Timestamps should be populated for all elements
Sample errors
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
- trip_id 22-2936209409 does not have a timestamp
- trip_id 2-319160397-V627A-LMCJV__ does not have a timestamp
- trip_id 22-486604801 does not have a timestamp
- trip_id 2-73138204 does not have a timestamp
vehicle_id not populated W002 541 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 22-2198274049 does not have a vehicle_id
- trip_id 2-73138213-V74A-LMCJV__ does not have a vehicle_id
- trip_id 2-73203751-V74A-LMCJV__ does not have a vehicle_id
- trip_id 2-73138211-V74A-LMCJV__ does not have a vehicle_id
- trip_id 2-73203749-V74A-LMCJV__ 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 975 | 28 times (93 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 12 234 | 27 times (90 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 588 | 26 times (87 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 544 | 26 times (87 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 4 007 | 26 times (87 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 66 082 | 26 times (87 % 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. | 147 | 25 times (83 % 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 | 6 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-17 at 22:36 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 2025-12-17 at 22:36 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766007363"
}
}