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
❌57 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-31 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 3 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 2-135921680 stop_sequence [14, 15, 16, 18, 18] is not strictly sorted by increasing stop_sequence
- trip_id 2-185663505 stop_sequence [27, 27] is not strictly sorted by increasing stop_sequence
- trip_id 2-319160389 stop_sequence [2, 3, 4, 5, 6, 7, 8, 10, 10] is not strictly sorted by increasing stop_sequence
Sequential stop_time_updates have the same stop_sequence E036 3 errors
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id 2-135921680 has repeating stop_sequence 18 - stop_sequence must increase for each stop_time_update
- trip_id 2-185663505 has repeating stop_sequence 27 - stop_sequence must increase for each stop_time_update
- trip_id 2-319160389 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 48 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-251854852 stop_sequence 5 has stop_id 4009 but GTFS stop_sequence 5 has stop_id 6464 - stop_ids should be the same
- GTFS-rt trip_id 2-251854852 stop_sequence 7 has stop_id 4234 but GTFS stop_sequence 7 has stop_id 4012 - stop_ids should be the same
- GTFS-rt trip_id 2-319160376 stop_sequence 32 has stop_id 572 but GTFS stop_sequence 32 has stop_id 382 - stop_ids should be the same
- GTFS-rt trip_id 2-319160376 stop_sequence 33 has stop_id 479 but GTFS stop_sequence 33 has stop_id 428 - stop_ids should be the same
- GTFS-rt trip_id 2-319160376 stop_sequence 34 has stop_id 638 but GTFS stop_sequence 34 has stop_id 572 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 3 errors
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-135921680 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-185663505 contains stop_sequence 27 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-319160389 contains stop_sequence 10 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 | 79 | 15 times (54 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 15 | 14 times (50 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 8 | 3 times (11 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 8 | 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 | 8 | 3 times (11 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-01 at 00:53 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-01 at 00:53 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1774997627"
}
}