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
❌30 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-14 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 30 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-319160344 stop_sequence 44 has stop_id 591 but GTFS stop_sequence 44 has stop_id 564 - stop_ids should be the same
- GTFS-rt trip_id 2-319160321 stop_sequence 16 has stop_id 606 but GTFS stop_sequence 16 has stop_id 432 - stop_ids should be the same
- GTFS-rt trip_id 2-319160321 stop_sequence 17 has stop_id 512 but GTFS stop_sequence 17 has stop_id 566 - stop_ids should be the same
- GTFS-rt trip_id 2-319160321 stop_sequence 18 has stop_id 494 but GTFS stop_sequence 18 has stop_id 606 - stop_ids should be the same
- GTFS-rt trip_id 2-319160321 stop_sequence 19 has stop_id 583 but GTFS stop_sequence 19 has stop_id 512 - stop_ids should be the same
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 47,769 | 19 times (68 % of validations) |
| W001 | Timestamps should be populated for all elements | 11,256 | 19 times (68 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 8,789 | 19 times (68 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 683 | 17 times (61 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 334 | 17 times (61 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,401 | 17 times (61 % 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. | 99 | 16 times (57 % 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,191 | 15 times (54 % 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 | 100 | 10 times (36 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 5 | 3 times (11 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 5 | 3 times (11 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 5 | 3 times (11 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 1 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-14 at 20:27 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-02-14 at 20:27 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "38",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1771097159"
},
"departure": {
"time": "1771097159"
},
"stopId": "377",
"stopSequence": 33
},
{
"arrival": {
"time": "1771097219"
},
"departure": {
"time": "1771097219"
},
"stopId": "629",
"stopSequence": 34
}
],
"timestamp": "1771097251",
"trip": {
"directionId": 1,
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260214",
"tripId": "2-19202086"
},
"vehicle": {
"id": "38",
"label": "97178",
"licensePlate": "BS 213 FJ"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771097251"
}
}