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

2026-01-08
97.4%
2026-01-09
96%
2026-01-10
99.5%
2026-01-11
100%
2026-01-12
95.5%
2026-01-13
99.5%
2026-01-14
93.8%
2026-01-15
97.1%
2026-01-16
98.7%
2026-01-17
100%
2026-01-18
100%
2026-01-19
91.6%
2026-01-20
95%
2026-01-21
96.9%
2026-01-22
92.6%
2026-01-23
98.5%
2026-01-24
97.2%
2026-01-25
100%
2026-01-26
96.1%
2026-01-27
98.5%
2026-01-28
98.1%
2026-01-29
98%
2026-01-30
97.8%
2026-01-31
99.7%
2026-02-01
100%
2026-02-02
97.4%
2026-02-03
98.1%
2026-02-04
99.6%
2026-02-05
100%
2026-02-06
100%
2026-02-07
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

2 errors

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

Errors

Vehicle position far from trip shape E029 2 errors

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.

Sample errors
  • vehicle.id 9 trip_id 2-288817154 at (47.657265,-2.745784) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 43 trip_id 2-121700400 at (47.64769,-2.765085) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
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 413 20 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 374 20 times (80 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 374 20 times (80 % 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. 121 20 times (80 % of validations)
W001 Timestamps should be populated for all elements 141 20 times (80 % of validations)
E052 Each vehicle should have a unique ID 26 18 times (72 % 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. 11 10 times (40 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 9 6 times (24 % of validations)

GTFS-RT feed content

Entities

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

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