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,168 errors, 1,234 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-14 at 08:01 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:3df567e2-4557-4e9c-ac99-3b7cb8a00726: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:b4c75824-d6d6-40be-a33b-9b0675a2b79d: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
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 CAT56Scol60375 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 MAURYLigne609 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 180 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,817 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:14:52 (1768374892) is equal to previous stop arrival_time 08:14:52 (1768374892) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 arrival_time 08:14:52 (1768374892) is equal to previous stop departure_time 08:14:52 (1768374892) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:14:52 (1768374892) is equal to previous stop departure_time 08:14:52 (1768374892) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:14:52 (1768374892) is equal to previous stop arrival_time 08:14:52 (1768374892) - times must increase between two sequential stops
- trip_id 2-135987242 stop_sequence 21 arrival_time 08:01:00 (1768374060) is equal to previous stop departure_time 08:01:00 (1768374060) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 10 errors
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
Sample errors
- GTFS-rt trip_id 2-5671092818 start_time is 13:15:00 and GTFS initial arrival_time is 13:20:00 - times do not match
- GTFS-rt trip_id 2-5671027272 start_time is 11:22:00 and GTFS initial arrival_time is 11:32:00 - times do not match
- GTFS-rt trip_id 2-5671092439 start_time is 11:50:00 and GTFS initial arrival_time is 12:00:00 - times do not match
- GTFS-rt trip_id 2-5671026900 start_time is 12:20:00 and GTFS initial arrival_time is 12:35:00 - times do not match
- GTFS-rt trip_id 2-5671092232 start_time is 17:30:00 and GTFS initial arrival_time is 17:25:00 - times do not match
stop_time_update departure time is before arrival time E025 9 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-19202096 stop_sequence 25 departure_time 08:00:59 (1768374059) is less than the same stop arrival_time 08:01:10 (1768374070) - departure time must be equal to or greater than arrival time
- trip_id 2-85852245 stop_sequence 17 departure_time 07:59:23 (1768373963) is less than the same stop arrival_time 08:00:52 (1768374052) - departure time must be equal to or greater than arrival time
- trip_id 2-85852245 stop_sequence 18 departure_time 08:00:23 (1768374023) is less than the same stop arrival_time 08:00:53 (1768374053) - departure time must be equal to or greater than arrival time
- trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_sequence 11 departure_time 08:01:03 (1768374063) is less than the same stop arrival_time 08:01:06 (1768374066) - departure time must be equal to or greater than arrival time
- trip_id 2-288097130 stop_sequence 8 departure_time 08:00:05 (1768374005) is less than the same stop arrival_time 08:00:36 (1768374036) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 104 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 2-5671092227 stop_sequence 7 has stop_id 4359 but GTFS stop_sequence 7 has stop_id 6816 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 8 has stop_id 4360 but GTFS stop_sequence 8 has stop_id 4359 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 9 has stop_id 4419 but GTFS stop_sequence 9 has stop_id 4360 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 10 has stop_id 4347 but GTFS stop_sequence 10 has stop_id 4419 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 11 has stop_id 4350 but GTFS stop_sequence 11 has stop_id 4347 - stop_ids should be the same
Warnings
timestamp not populated W001 692 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 chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not have a timestamp
- trip_id 2-17236052 does not have a timestamp
- trip_id 2-319160397 does not have a timestamp
- trip_id 2-288161794 does not have a timestamp
vehicle_id not populated W002 542 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 22-2718105601 does not have a vehicle_id
- trip_id 22-2047016961 does not have a vehicle_id
- trip_id 22-2751660033 does not have a vehicle_id
- trip_id 2-218562647 does not have a vehicle_id
- trip_id 2-218497031 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,235 | 29 times (85 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11,171 | 29 times (85 % 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,166 | 28 times (82 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 486 | 28 times (82 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3,471 | 28 times (82 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 66,769 | 28 times (82 % 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. | 119 | 26 times (76 % 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 | 61 | 8 times (24 % 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 | 217 | 4 times (12 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-14 at 21:40 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-14 at 21:40 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768423222"
}
}