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,336 errors, 1,313 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-29 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 192 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:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- 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 2-73203743-V426B-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2-319160397-V627A-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2-17236052-V17A-LMCJV__ 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 23 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- route_id BSAScol61133 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
- route_id CAT56Ligne604 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:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:413a86f6-9498-468f-a2e8-77f5c0a9642b:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:c7278b07-f2fa-40a0-a19f-b93e0f1b1651:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:d2c53593-28a8-4ebb-bed3-91cee01b4496:LOC does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2,832 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-M574A-LMCJV__ stop_sequence 34 arrival_time 08:14:22 (1769670862) is equal to previous stop arrival_time 08:14:22 (1769670862) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:14:22 (1769670862) is equal to previous stop departure_time 08:14:22 (1769670862) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 departure_time 08:14:22 (1769670862) is equal to previous stop departure_time 08:14:22 (1769670862) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 departure_time 08:14:22 (1769670862) is equal to previous stop arrival_time 08:14:22 (1769670862) - times must increase between two sequential stops
- trip_id 2-51118090 stop_sequence 32 arrival_time 08:09:00 (1769670540) is equal to previous stop arrival_time 08:09:00 (1769670540) - 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 7 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-319160397-V627A-LMCJV__ stop_sequence 41 departure_time 08:03:12 (1769670192) is less than the same stop arrival_time 08:03:14 (1769670194) - departure time must be equal to or greater than arrival time
- trip_id 2-19202096 stop_sequence 27 departure_time 08:02:59 (1769670179) is less than the same stop arrival_time 08:03:07 (1769670187) - departure time must be equal to or greater than arrival time
- trip_id 2-85983288 stop_sequence 16 departure_time 08:02:46 (1769670166) is less than the same stop arrival_time 08:03:13 (1769670193) - departure time must be equal to or greater than arrival time
- trip_id 2-336134202 stop_sequence 17 departure_time 08:02:49 (1769670169) is less than the same stop arrival_time 08:02:50 (1769670170) - departure time must be equal to or greater than arrival time
- trip_id 2-288097130 stop_sequence 8 departure_time 08:02:38 (1769670158) is less than the same stop arrival_time 08:03:13 (1769670193) - 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 741 errors
Timestamps should be populated for all elements
Sample errors
- trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC does not have a timestamp
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
- trip_id 2-73203743-V426B-LMCJV__ does not have a timestamp
- trip_id 22-2936209409 does not have a timestamp
- trip_id 22-989921281 does not have a timestamp
vehicle_id not populated W002 572 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-288489477 does not have a vehicle_id
- trip_id 2-286196422 does not have a vehicle_id
- trip_id 2-288228284 does not have a vehicle_id
- trip_id 2-287835064 does not have a vehicle_id
- trip_id 2-286457934 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,652 | 26 times (90 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11,607 | 26 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 | 603 | 24 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 430 | 24 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3,041 | 24 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. | 64,156 | 24 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. | 132 | 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,254 | 13 times (45 % 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 | 120 | 12 times (41 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-30 at 04:01 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-30 at 04:01 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769742072"
}
}