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,988 errors, 1,243 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-22 at 08:09 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 26 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:b291fc00-a717-4ec7-8aae-8fa660ab5c32: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: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
- trip_id chouette:VehicleJourney:1267fcef-9e99-44f6-bfa8-33b9e7d96560: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 25 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id AVBScol60830 does not exist in the GTFS data routes.txt
- route_id MAURYLigne609 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
- route_id AVBLigne608 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 189 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC stop_id bre_vannes_2024_2025.18645 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC stop_id okina.11510 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC stop_id bre_vannes_2024_2025.17591 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:3f3655e5-ddc5-410d-a66a-ee3f0279b35c:LOC does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:5b4834b3-bdf7-402b-b6b3-d6e1db89d36f:LOC does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2,742 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:15 (1769066055) is equal to previous stop arrival_time 08:14:15 (1769066055) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 arrival_time 08:14:15 (1769066055) is equal to previous stop departure_time 08:14:15 (1769066055) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:14:15 (1769066055) is equal to previous stop departure_time 08:14:15 (1769066055) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:14:15 (1769066055) is equal to previous stop arrival_time 08:14:15 (1769066055) - times must increase between two sequential stops
- trip_id 2-51118090 stop_sequence 32 arrival_time 08:20:27 (1769066427) is equal to previous stop arrival_time 08:20:27 (1769066427) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 6 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 stop_sequence 43 departure_time 08:08:24 (1769065704) is less than the same stop arrival_time 08:08:28 (1769065708) - departure time must be equal to or greater than arrival time
- trip_id chouette:VehicleJourney:b63ae62c-dd08-4c0a-b966-8df89fe347b1:LOC stop_sequence 3 departure_time 08:07:44 (1769065664) is less than the same stop arrival_time 08:08:10 (1769065690) - departure time must be equal to or greater than arrival time
- trip_id 2-17039420 stop_sequence 16 departure_time 08:07:44 (1769065664) is less than the same stop arrival_time 08:08:27 (1769065707) - departure time must be equal to or greater than arrival time
- trip_id 2-19202114 stop_sequence 13 departure_time 08:08:10 (1769065690) is less than the same stop arrival_time 08:08:12 (1769065692) - departure time must be equal to or greater than arrival time
- trip_id 2-285671428 stop_sequence 4 departure_time 08:06:37 (1769065597) is less than the same stop arrival_time 08:08:17 (1769065697) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 708 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 2-73203743 does not have a timestamp
- trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC does not have a timestamp
- trip_id 2-319160397 does not have a timestamp
- trip_id 22-486604801 does not have a timestamp
- trip_id 2-288161794 does not have a timestamp
vehicle_id not populated W002 535 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-34144428 does not have a vehicle_id
- trip_id 2-33620137 does not have a vehicle_id
- trip_id 2-34144427 does not have a vehicle_id
- trip_id 2-33620136 does not have a vehicle_id
- trip_id 2-34144426 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 | 13,510 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 10,863 | 25 times (83 % 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,055 | 24 times (80 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 394 | 24 times (80 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,722 | 24 times (80 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 61,931 | 24 times (80 % 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. | 115 | 22 times (73 % 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 | 102 | 12 times (40 % 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 | 734 | 8 times (27 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-22 at 22:56 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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-22 at 22:56 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "668192",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1769083200"
},
"stopId": "STP-DK",
"stopSequence": 1
},
{
"arrival": {
"time": "1769083500"
},
"departure": {
"time": "1769083500"
},
"stopId": "STP-Hbf",
"stopSequence": 2
},
{
"arrival": {
"time": "1769083800"
},
"departure": {
"time": "1769083800"
},
"stopId": "STP-BB",
"stopSequence": 3
},
{
"arrival": {
"time": "1769084100"
},
"departure": {
"time": "1769084100"
},
"stopId": "STP-TESTSENE",
"stopSequence": 4
},
{
"arrival": {
"time": "1769084400"
},
"departure": {
"time": "1769084400"
},
"stopId": "STP-TESTTHEIX",
"stopSequence": 5
},
{
"arrival": {
"time": "1769084700"
},
"departure": {
"time": "1769084700"
},
"stopId": "STP-TESTELVEN",
"stopSequence": 6
},
{
"arrival": {
"time": "1769085000"
},
"stopId": "STP-TESTARR",
"stopSequence": 7
}
],
"trip": {
"directionId": 0,
"routeId": "DFL",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260122",
"startTime": "13:00:00",
"tripId": "ext:10872"
},
"vehicle": {
"id": "647",
"label": "Test Matawan Axio4",
"licensePlate": "00-MAT-00"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769118979"
}
}