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,984 errors, 1,274 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-03 at 08:02 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: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:57b1958c-0975-40c3-8ee8-6107567ce2cd:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:1ab68529-c117-4693-a98a-4a4de751be95:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:aaa13cdd-af52-4aae-9f1a-224f4c8404f6:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:b4c75824-d6d6-40be-a33b-9b0675a2b79d: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 BSAScol61133 does not exist in the GTFS data routes.txt
- route_id CAT56Scol60374 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
- route_id MorioLigne602 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 168 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,760 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-121765929 stop_sequence 34 arrival_time 08:17:10 (1770103030) is equal to previous stop arrival_time 08:17:10 (1770103030) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 arrival_time 08:17:10 (1770103030) is equal to previous stop departure_time 08:17:10 (1770103030) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:17:10 (1770103030) is equal to previous stop departure_time 08:17:10 (1770103030) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:17:10 (1770103030) is equal to previous stop arrival_time 08:17:10 (1770103030) - times must increase between two sequential stops
- trip_id 2-135987242 stop_sequence 21 arrival_time 08:03:51 (1770102231) is equal to previous stop arrival_time 08:03:51 (1770102231) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 8 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-52756522 stop_sequence 25 departure_time 08:01:19 (1770102079) is less than the same stop arrival_time 08:01:30 (1770102090) - departure time must be equal to or greater than arrival time
- trip_id 22-2382430209 stop_sequence 8 departure_time 07:59:41 (1770101981) is less than the same stop arrival_time 08:00:01 (1770102001) - departure time must be equal to or greater than arrival time
- trip_id 22-2298544129 stop_sequence 10 departure_time 08:01:39 (1770102099) is less than the same stop arrival_time 08:01:40 (1770102100) - departure time must be equal to or greater than arrival time
- trip_id 22-2298544129 stop_sequence 11 departure_time 08:01:39 (1770102099) is less than the same stop arrival_time 08:01:41 (1770102101) - departure time must be equal to or greater than arrival time
- trip_id 2-319160383 stop_sequence 8 departure_time 08:01:18 (1770102078) is less than the same stop arrival_time 08:01:25 (1770102085) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 717 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 22-1140916301 does not have a timestamp
- trip_id 2-5671092225 does not have a timestamp
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
- trip_id 2-73203743 does not have a timestamp
- trip_id chouette:VehicleJourney:57b1958c-0975-40c3-8ee8-6107567ce2cd:LOC does not have a timestamp
vehicle_id not populated W002 557 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 22-1291911169 does not have a vehicle_id
- trip_id 2-17236065 does not have a vehicle_id
- trip_id 2-19202121 does not have a vehicle_id
- trip_id 2-17236054 does not have a vehicle_id
- trip_id 2-19202120 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,731 | 27 times (93 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 12,367 | 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 | 813 | 25 times (86 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 464 | 25 times (86 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3,281 | 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,574 | 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. | 145 | 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-04 at 04:18 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-04 at 04:18 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770175082"
}
}