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 901 errors, 1 186 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-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:cb277215-b8ef-4848-8f33-16880fd56527:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:67309930-e07e-49b6-afc5-46c916cff303:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- 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
GTFS-rt route_id does not exist in GTFS data E004 20 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 MAURYLigne609 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
- route_id BSAScol61137 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 145 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 707 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-336134203 stop_sequence 46 arrival_time 07:18:07 (1764742687) is less than previous stop arrival_time 08:18:48 (1764746328) - times must increase between two sequential stops
- trip_id 2-336134203 stop_sequence 46 arrival_time 07:18:07 (1764742687) is less than previous stop departure_time 08:18:48 (1764746328) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:15:01 (1764746101) is equal to previous stop arrival_time 08:15:01 (1764746101) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:15:01 (1764746101) is equal to previous stop departure_time 08:15:01 (1764746101) - times must increase between two sequential stops
- trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 departure_time 08:15:01 (1764746101) is equal to previous stop departure_time 08:15:01 (1764746101) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 5 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-336396289-M3626A-LMCJV__ stop_sequence 32 departure_time 08:01:55 (1764745315) is less than the same stop arrival_time 08:02:02 (1764745322) - departure time must be equal to or greater than arrival time
- trip_id 2-85983985 stop_sequence 16 departure_time 08:00:41 (1764745241) is less than the same stop arrival_time 08:01:21 (1764745281) - departure time must be equal to or greater than arrival time
- trip_id 2-121241698 stop_sequence 16 departure_time 08:01:42 (1764745302) is less than the same stop arrival_time 08:02:09 (1764745329) - departure time must be equal to or greater than arrival time
- trip_id 2-73203738-V426A-LMCJV__ stop_sequence 13 departure_time 08:01:50 (1764745310) is less than the same stop arrival_time 08:01:53 (1764745313) - departure time must be equal to or greater than arrival time
- trip_id 22-2147549185 stop_sequence 3 departure_time 08:01:30 (1764745290) is less than the same stop arrival_time 08:02:14 (1764745334) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 666 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 22-1610678273 does not have a timestamp
- trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
- trip_id 2-319160397-V627A-LMCJV__ does not have a timestamp
- trip_id 22-486604801 does not have a timestamp
- trip_id 2-169279495 does not have a timestamp
vehicle_id not populated W002 520 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 22-2214658049 does not have a vehicle_id
- trip_id 22-2617311233 does not have a vehicle_id
- trip_id 2-19202090 does not have a vehicle_id
- trip_id 2-17236042 does not have a vehicle_id
- trip_id 2-185466898 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 911 | 27 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11 592 | 26 times (84 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 467 | 24 times (77 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 466 | 24 times (77 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 173 | 24 times (77 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 61 888 | 24 times (77 % 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. | 140 | 24 times (77 % 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 | 170 | 11 times (35 % 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 | 1 | 1 times (3 % 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 2025-12-03 at 21:46 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 2025-12-03 at 21:46 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764794787"
}
}