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-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%
2026-02-13
100%
2026-02-14
100%
2026-02-15
99.6%
2026-02-16
100%
2026-02-17
100%
2026-02-18
100%
2026-02-19
99.4%
2026-02-20
100%
2026-02-21
99.4%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
99.3%
2026-03-03
100%
2026-03-04
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

1 error

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

Errors

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 error

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-251920390 stop_sequence 7 has stop_id 4012 but GTFS stop_sequence 7 has stop_id 4234 - stop_ids should be the same
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
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 658 18 times (64 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 22 12 times (43 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 22 12 times (43 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 22 12 times (43 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 51 5 times (18 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 5,594 4 times (14 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 48 2 times (7 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 340 2 times (7 % 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. 14 2 times (7 % of validations)
W001 Timestamps should be populated for all elements 1,395 2 times (7 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1,072 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-05 at 00:00 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-03-05 at 00:00 Europe/Paris. You can look at the GTFS-RT documentation.

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