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-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
95.3%
2025-12-25
99.3%
2025-12-26
98.6%
2025-12-27
100%
2025-12-28
99.8%
2025-12-29
97.8%
2025-12-30
98.5%
2025-12-31
99.5%
2026-01-01
100%
2026-01-02
95.3%
2026-01-03
100%
2026-01-04
99.5%
2026-01-05
98.1%
2026-01-06
99.6%
2026-01-07
97.6%
2026-01-08
97.4%
2026-01-09
96%
2026-01-10
99.5%
2026-01-11
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-11 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 405 | 23 times (77 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 365 | 23 times (77 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 364 | 23 times (77 % of validations) |
| W001 | Timestamps should be populated for all elements | 180 | 23 times (77 % 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. | 70 | 15 times (50 % of validations) |
| E052 | Each vehicle should have a unique ID | 19 | 9 times (30 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 7 | 6 times (20 % 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. | 6 | 5 times (17 % 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 | 9 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-12 at 00:14 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-12 at 00:14 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768173268"
}
}