Resource details

File name: Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Kicéo.

Download availability

2026-01-13
99.6%
2026-01-14
100%
2026-01-15
100%
2026-01-16
100%
2026-01-17
100%
2026-01-18
100%
2026-01-19
100%
2026-01-20
100%
2026-01-21
100%
2026-01-22
100%
2026-01-23
100%
2026-01-24
100%
2026-01-25
100%
2026-01-26
100%
2026-01-27
100%
2026-01-28
100%
2026-01-29
100%
2026-01-30
100%
2026-01-31
100%
2026-02-01
100%
2026-02-02
99.5%
2026-02-03
100%
2026-02-04
100%
2026-02-05
100%
2026-02-06
100%
2026-02-07
99.4%
2026-02-08
100%
2026-02-09
100%
2026-02-10
100%
2026-02-11
100%
2026-02-12
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

45 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-11 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 2 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors
  • trip_id 2-319160383 stop_sequence [10, 10] is not strictly sorted by increasing stop_sequence
  • trip_id 2-336396289 stop_sequence [30, 31, 31] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 4 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-336396289 stop_sequence 31 arrival_time 08:02:35 (1770793355) is less than previous stop arrival_time 08:04:35 (1770793475) - times must increase between two sequential stops
  • trip_id 2-336396289 stop_sequence 31 arrival_time 08:02:35 (1770793355) is less than previous stop departure_time 08:04:35 (1770793475) - times must increase between two sequential stops
  • trip_id 2-336396289 stop_sequence 31 departure_time 08:02:35 (1770793355) is less than previous stop departure_time 08:04:35 (1770793475) - times must increase between two sequential stops
  • trip_id 2-336396289 stop_sequence 31 departure_time 08:02:35 (1770793355) is less than previous stop arrival_time 08:04:35 (1770793475) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 2 errors

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors
  • trip_id 2-319160383 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
  • trip_id 2-336396289 has repeating stop_sequence 31 - stop_sequence must increase for each stop_time_update

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 35 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-319160387 stop_sequence 19 has stop_id 583 but GTFS stop_sequence 19 has stop_id 512 - stop_ids should be the same
  • GTFS-rt trip_id 2-319160387 stop_sequence 20 has stop_id 620 but GTFS stop_sequence 20 has stop_id 494 - stop_ids should be the same
  • GTFS-rt trip_id 2-319160387 stop_sequence 21 has stop_id 490 but GTFS stop_sequence 21 has stop_id 583 - stop_ids should be the same
  • GTFS-rt trip_id 2-319160387 stop_sequence 22 has stop_id 635 but GTFS stop_sequence 22 has stop_id 620 - stop_ids should be the same
  • GTFS-rt trip_id 2-319160387 stop_sequence 23 has stop_id 439 but GTFS stop_sequence 23 has stop_id 490 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 2 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-319160383 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 2-336396289 contains stop_sequence 31 that does not exist in GTFS stop_times.txt for this trip
Validate this GTFS-RT now

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
W001 Timestamps should be populated for all elements 13,429 22 times (79 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 10,478 22 times (79 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 56,207 21 times (75 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 748 20 times (71 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 399 20 times (71 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2,876 20 times (71 % 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. 125 19 times (68 % 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,388 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 130 13 times (46 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 3 2 times (7 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 3 2 times (7 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 3 2 times (7 % 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-12 at 02:31 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-02-12 at 02:31 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1770859898" } }