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

2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
99.4%
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%
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

⚠️17 warnings

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

Warnings

timestamp not populated W001 9 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 2-369623053 does not have a timestamp
  • trip_id 2-369754128 does not have a timestamp
  • trip_id 2-369754126 does not have a timestamp
  • trip_id 2-369623054 does not have a timestamp
  • trip_id 2-369754127 does not have a timestamp

vehicle_id not populated W002 8 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 2-369754128 does not have a vehicle_id
  • trip_id 2-369754126 does not have a vehicle_id
  • trip_id 2-369623054 does not have a vehicle_id
  • trip_id 2-369754127 does not have a vehicle_id
  • trip_id 2-369623055 does not have a vehicle_id
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 12,105 25 times (83 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 9,903 25 times (83 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 996 23 times (77 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 332 23 times (77 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2,215 23 times (77 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 58,943 23 times (77 % 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. 93 21 times (70 % 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 72 9 times (30 % 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 422 5 times (17 % of validations)

GTFS-RT feed content

Entities

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

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