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 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-08 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 1 error
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 2-185663505 stop_sequence [27, 27] is not strictly sorted by increasing stop_sequence
Sequential stop_time_updates have the same stop_sequence E036 1 error
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id 2-185663505 has repeating stop_sequence 27 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_sequence not found in GTFS data E051 1 error
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id 2-185663505 contains stop_sequence 27 that does not exist in GTFS stop_times.txt for this trip
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 |
|---|---|---|---|
| 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 | 105 | 15 times (58 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 9 | 9 times (35 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 33 | 8 times (31 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 33 | 8 times (31 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 33 | 8 times (31 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 76 | 5 times (19 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-08 at 23:55 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-04-08 at 23:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775685333"
}
}