Resource details

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

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

Download availability

2025-11-24
99.5%
2025-11-25
97.9%
2025-11-26
99.8%
2025-11-27
99.9%
2025-11-28
99.9%
2025-11-29
100%
2025-11-30
100%
2025-12-01
96.5%
2025-12-02
99.8%
2025-12-03
99.8%
2025-12-04
98.5%
2025-12-05
97.9%
2025-12-06
100%
2025-12-07
99.5%
2025-12-08
99.2%
2025-12-09
98.7%
2025-12-10
98.8%
2025-12-11
96.7%
2025-12-12
99.5%
2025-12-13
99.2%
2025-12-14
99.4%
2025-12-15
98.8%
2025-12-16
99.4%
2025-12-17
99.5%
2025-12-18
98.6%
2025-12-19
97.4%
2025-12-20
99.3%
2025-12-21
100%
2025-12-22
94.6%
2025-12-23
95.1%
2025-12-24
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

62 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-23 at 17:17 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 24 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 66 trip_id 2-52690955 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 166 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 375 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 167 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 163 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 19 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • vehicle_id 166 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 375 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 167 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 170 route_id MOBICEO does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 19 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • vehicle_id 166 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 375 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 167 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 163 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 170 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt

Warnings

timestamp not populated W001 10 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 65 does not have a timestamp
  • vehicle_id 264 does not have a timestamp
  • vehicle_id 61 does not have a timestamp
  • vehicle_id 51 does not have a timestamp
  • vehicle_id 359 does not have a timestamp
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 517 26 times (87 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 511 26 times (87 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 511 26 times (87 % of validations)
W001 Timestamps should be populated for all elements 181 26 times (87 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 143 21 times (70 % of validations)
E052 Each vehicle should have a unique ID 36 16 times (53 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 16 13 times (43 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 16 12 times (40 % 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 3 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-24 at 05:46 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-24 at 05:46 Europe/Paris. You can look at the GTFS-RT documentation.

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