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
❌42 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-02 at 08:08 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 14 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 165 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 248 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
- vehicle_id 422 trip_id chouette:VehicleJourney:4d6bfd87-d222-4b79-81e5-90add421e643:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 247 trip_id chouette:VehicleJourney:6b533049-31d6-49ac-94d8-d19b16877df4:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 358 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
GTFS-rt route_id does not exist in GTFS data E004 14 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 165 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 248 route_id BSALigne611 does not exist in the GTFS data routes.txt
- vehicle_id 422 route_id AVBLigne608 does not exist in the GTFS data routes.txt
- vehicle_id 247 route_id BSALigne611 does not exist in the GTFS data routes.txt
- vehicle_id 358 route_id MorioLigne602 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 14 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 165 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- vehicle_id 248 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
- vehicle_id 422 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
- vehicle_id 247 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
- vehicle_id 358 stop_id chouette:StopArea:2b3ddbd2-6c81-48c1-ae43-0b35901be04d:LOC does not exist in GTFS data stops.txt
Warnings
timestamp not populated W001 7 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 81 does not have a timestamp
- vehicle_id 41 does not have a timestamp
- vehicle_id 35 does not have a timestamp
- vehicle_id 49 does not have a timestamp
- vehicle_id 92 does not have a timestamp
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 471 | 24 times (80 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 431 | 24 times (80 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 430 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 188 | 24 times (80 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 109 | 17 times (57 % of validations) |
| E052 | Each vehicle should have a unique ID | 26 | 12 times (40 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 11 | 10 times (33 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 11 | 9 times (30 % 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 | 9 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-03 at 02:50 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-03 at 02:50 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767405009"
}
}