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-04-05 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 6 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 2-386334721 stop_sequence [2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 12] is not strictly sorted by increasing stop_sequence
- trip_id 2-369754126 stop_sequence [14, 14] is not strictly sorted by increasing stop_sequence
- trip_id 2-5771821057 stop_sequence [6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 33, 34, 35, 35] is not strictly sorted by increasing stop_sequence
- trip_id 2-369623054 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 13, 13] is not strictly sorted by increasing stop_sequence
- trip_id 2-386465794 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 9] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 32 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-386334721 stop_sequence 14 arrival_time 09:25:17 (1775373917) is less than previous stop arrival_time 09:31:17 (1775374277) - times must increase between two sequential stops
- trip_id 2-386334721 stop_sequence 14 arrival_time 09:25:17 (1775373917) is less than previous stop departure_time 09:31:17 (1775374277) - times must increase between two sequential stops
- trip_id 2-386334721 stop_sequence 14 departure_time 09:25:17 (1775373917) is less than previous stop departure_time 09:31:17 (1775374277) - times must increase between two sequential stops
- trip_id 2-386334721 stop_sequence 14 departure_time 09:25:17 (1775373917) is less than previous stop arrival_time 09:31:17 (1775374277) - times must increase between two sequential stops
- trip_id 2-386334721 stop_sequence 16 arrival_time 09:26:17 (1775373977) is less than previous stop arrival_time 09:33:17 (1775374397) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_sequence E036 6 errors
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id 2-386334721 has repeating stop_sequence 12 - stop_sequence must increase for each stop_time_update
- trip_id 2-369754126 has repeating stop_sequence 14 - stop_sequence must increase for each stop_time_update
- trip_id 2-5771821057 has repeating stop_sequence 35 - stop_sequence must increase for each stop_time_update
- trip_id 2-369623054 has repeating stop_sequence 13 - stop_sequence must increase for each stop_time_update
- trip_id 2-386465794 has repeating stop_sequence 9 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 7 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-369754126 stop_sequence 14 has stop_id 494 but GTFS stop_sequence 14 has stop_id 461 - stop_ids should be the same
- GTFS-rt trip_id 2-5771821057 stop_sequence 33 has stop_id 485 but GTFS stop_sequence 33 has stop_id 603 - stop_ids should be the same
- GTFS-rt trip_id 2-5771821057 stop_sequence 34 has stop_id 487 but GTFS stop_sequence 34 has stop_id 565 - stop_ids should be the same
- GTFS-rt trip_id 2-369623054 stop_sequence 13 has stop_id 462 but GTFS stop_sequence 13 has stop_id 603 - stop_ids should be the same
- GTFS-rt trip_id 2-386465794 stop_sequence 6 has stop_id 518 but GTFS stop_sequence 6 has stop_id 572 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 6 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-386334721 contains stop_sequence 12 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-369754126 contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-5771821057 contains stop_sequence 35 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-369623054 contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-386465794 contains stop_sequence 9 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 | 102 | 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 | 10 | 10 times (38 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 30 | 6 times (23 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 30 | 6 times (23 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 30 | 6 times (23 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 72 | 4 times (15 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-05 at 21:31 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-05 at 21:31 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775417500"
}
}