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
❌2,889 errors, 703 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-10 at 08:11 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 7 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:110285b0-a061-467e-a681-25e4aaf45af4: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
- trip_id chouette:VehicleJourney:b06d0e1d-00b1-4f2f-bcd9-10ed2d719f04:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:b705ed83-6c28-4cc1-b505-5597ff7f05fa:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ext:12069 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 7 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id MorioLigne602 does not exist in the GTFS data routes.txt
- route_id MorioLigne602 does not exist in the GTFS data routes.txt
- route_id MAURYLigne609 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 48 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC stop_id chouette:StopArea:60d1d43f-333f-40d5-84d8-10c7f0738473:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC stop_id K0671 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC stop_id chouette:StopArea:80b96852-8a75-4549-abbc-56e32fb43823:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC stop_id chouette:StopArea:5274d04c-73b7-4a46-b5cb-b1ef774b03bd:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC stop_id chouette:StopArea:2b3ddbd2-6c81-48c1-ae43-0b35901be04d:LOC 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-117571588 stop_sequence 15 arrival_time 07:33:00 (1768026780) is equal to previous stop arrival_time 07:33:00 (1768026780) - times must increase between two sequential stops
- trip_id 2-117571588 stop_sequence 15 arrival_time 07:33:00 (1768026780) is equal to previous stop departure_time 07:33:00 (1768026780) - times must increase between two sequential stops
- trip_id 2-117571588 stop_sequence 15 departure_time 07:33:00 (1768026780) is equal to previous stop departure_time 07:33:00 (1768026780) - times must increase between two sequential stops
- trip_id 2-117571588 stop_sequence 15 departure_time 07:33:00 (1768026780) is equal to previous stop arrival_time 07:33:00 (1768026780) - times must increase between two sequential stops
- trip_id 2-117571588 stop_sequence 27 arrival_time 07:49:00 (1768027740) is equal to previous stop arrival_time 07:49:00 (1768027740) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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-17235995 stop_sequence 9 departure_time 08:11:10 (1768029070) is less than the same stop arrival_time 08:11:26 (1768029086) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 378 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 2-117571588 does not have a timestamp
- trip_id 2-336134150 does not have a timestamp
- trip_id 2-319160344 does not have a timestamp
- trip_id 2-251854853 does not have a timestamp
- trip_id 2-17039373 does not have a timestamp
vehicle_id not populated W002 325 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-19202127 does not have a vehicle_id
- trip_id 2-17235990 does not have a vehicle_id
- trip_id 2-19202070 does not have a vehicle_id
- trip_id 2-117637128 does not have a vehicle_id
- trip_id 2-119472136 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 | 14,647 | 31 times (89 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11,504 | 31 times (89 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1,186 | 29 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 498 | 29 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3,536 | 29 times (83 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 69,405 | 29 times (83 % 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. | 121 | 27 times (77 % 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 | 41 | 6 times (17 % 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 | 9 | 2 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-11 at 06:55 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-01-11 at 06:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768110902"
}
}