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
❌164 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-13 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 14 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 2-336134209 stop_sequence [23, 23] is not strictly sorted by increasing stop_sequence
- trip_id 2-336134184 stop_sequence [8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 23, 23] is not strictly sorted by increasing stop_sequence
- trip_id 2-319160375 stop_sequence [23, 23] is not strictly sorted by increasing stop_sequence
- trip_id 2-6140723212 stop_sequence [1, 2, 3, 4, 5, 5] is not strictly sorted by increasing stop_sequence
- trip_id 2-319160383 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 23, 23] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 84 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-336134209 stop_sequence 24 arrival_time 09:11:09 (1776064269) is less than previous stop arrival_time 09:18:08 (1776064688) - times must increase between two sequential stops
- trip_id 2-336134209 stop_sequence 24 arrival_time 09:11:09 (1776064269) is less than previous stop departure_time 09:18:08 (1776064688) - times must increase between two sequential stops
- trip_id 2-336134209 stop_sequence 24 departure_time 09:11:09 (1776064269) is less than previous stop departure_time 09:18:08 (1776064688) - times must increase between two sequential stops
- trip_id 2-336134209 stop_sequence 24 departure_time 09:11:09 (1776064269) is less than previous stop arrival_time 09:18:08 (1776064688) - times must increase between two sequential stops
- trip_id 2-336134184 stop_sequence 24 arrival_time 09:31:15 (1776065475) is less than previous stop arrival_time 09:38:14 (1776065894) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_sequence E036 14 errors
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id 2-336134209 has repeating stop_sequence 23 - stop_sequence must increase for each stop_time_update
- trip_id 2-336134184 has repeating stop_sequence 23 - stop_sequence must increase for each stop_time_update
- trip_id 2-319160375 has repeating stop_sequence 23 - stop_sequence must increase for each stop_time_update
- trip_id 2-6140723212 has repeating stop_sequence 5 - stop_sequence must increase for each stop_time_update
- trip_id 2-319160383 has repeating stop_sequence 23 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 38 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-336134209 stop_sequence 23 has stop_id 584 but GTFS stop_sequence 23 has stop_id 438 - stop_ids should be the same
- GTFS-rt trip_id 2-319160376 stop_sequence 33 has stop_id 359 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 4227 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 14 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-336134209 contains stop_sequence 23 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-336134184 contains stop_sequence 23 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-319160375 contains stop_sequence 23 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-6140723212 contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-319160383 contains stop_sequence 23 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 | 152 | 15 times (60 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 56 | 11 times (44 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 56 | 11 times (44 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 56 | 11 times (44 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 212 | 8 times (32 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 6 | 6 times (24 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-14 at 02:16 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-14 at 02:16 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1776125786"
}
}