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-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%
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.5%
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

97 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-30 at 08:02 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 42 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 163 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 39 trip_id 2-33620095-M2B-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 69 trip_id 2-121700380-V762A-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 87 trip_id 2-52756515-M13A-___JV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 82 trip_id 2-168689686-M10A-LMCJV__ 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 23 errors

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

Sample errors
  • vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 164 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 357 route_id MorioLigne602 does not exist in the GTFS data routes.txt
  • vehicle_id 247 route_id BSALigne611 does not exist in the GTFS data routes.txt
  • vehicle_id 248 route_id BSALigne611 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 163 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 164 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 357 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
  • vehicle_id 247 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
  • vehicle_id 248 stop_id chouette:StopArea:f22729a5-ff01-4cb2-817c-129545525489:LOC does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 1 error

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.

Sample errors
  • vehicle.id 422 at (47.55018,-2.470433) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Vehicle position far from trip shape E029 5 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 218 trip_id 22-2852192257 at (47.776485,-2.676317) 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 333 trip_id 22-1325465601 at (47.700005,-2.769825) 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 298 trip_id 22-3172532227-AFF-6-__CJV__ at (47.627464,-2.830287) 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 97 trip_id 22-3070296065 at (47.717575,-2.887986) 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 320 trip_id 22-2130903041 at (47.600067,-2.664118) 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 is not unique E052 3 errors

Each vehicle should have a unique ID

Sample errors
  • entity ID 679021 has vehicle.id 97 which is used by more than one vehicle in the feed
  • entity ID 679083 has vehicle.id 97 which is used by more than one vehicle in the feed
  • entity ID 679047 has vehicle.id 320 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 10 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 579 does not have a timestamp
  • vehicle_id 87 does not have a timestamp
  • vehicle_id 21 does not have a timestamp
  • vehicle_id 35 does not have a timestamp
  • vehicle_id 247 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 396 21 times (81 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 358 21 times (81 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 358 21 times (81 % of validations)
W001 Timestamps should be populated for all elements 140 21 times (81 % 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. 100 18 times (69 % of validations)
E052 Each vehicle should have a unique ID 22 15 times (58 % 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. 9 8 times (31 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 6 4 times (15 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-30 at 21:25 Europe/Paris.

vehicle_positions (5) 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-01-30 at 21:25 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "680337", "vehicle": { "currentStopSequence": 2, "position": { "bearing": 291.0, "latitude": 47.69870376586914, "longitude": -2.7626359462738037, "speed": 5.0 }, "stopId": "STP-ARRIVEE", "timestamp": "1769800327", "trip": { "directionId": 0, "routeId": "MOBICEO", "scheduleRelationship": "UNSCHEDULED", "startDate": "20260130", "startTime": "10:00:00", "tripId": "ext:12069" }, "vehicle": { "id": "366", "label": "GX-711-NR", "licensePlate": "GX-711-NR" } } }, { "id": "678934", "vehicle": { "currentStopSequence": 4, "position": { "bearing": 139.0, "latitude": 47.50365447998047, "longitude": -2.8368959426879883, "speed": 4.722222328186035 }, "stopId": "123", "timestamp": "1769804699", "trip": { "directionId": 1, "routeId": "17", "scheduleRelationship": "SCHEDULED", "startDate": "20260130", "startTime": "21:10:00", "tripId": "2-286589118" }, "vehicle": { "id": "120", "label": "23803", "licensePlate": "DT 119 VJ" } } }, { "id": "679742", "vehicle": { "currentStopSequence": 5, "position": { "bearing": 177.0, "latitude": 47.6580696105957, "longitude": -2.759830951690674, "speed": 5.833333492279053 }, "stopId": "603", "timestamp": "1769804664", "trip": { "directionId": 0, "routeId": "21", "scheduleRelationship": "SCHEDULED", "startDate": "20260130", "startTime": "21:20:00", "tripId": "2-353042439" }, "vehicle": { "id": "71", "label": "97210", "licensePlate": "FC 194 MS" } } }, { "id": "679738", "vehicle": { "currentStopSequence": 17, "position": { "latitude": 47.525856018066406, "longitude": -2.8447670936584473, "speed": 0.0 }, "stopId": "122", "timestamp": "1769804681", "trip": { "directionId": 0, "routeId": "17", "scheduleRelationship": "SCHEDULED", "startDate": "20260130", "startTime": "20:30:00", "tripId": "2-288555209" }, "vehicle": { "id": "342", "label": "40348", "licensePlate": "GT 747 CM" } } }, { "id": "679741", "vehicle": { "currentStopSequence": 8, "position": { "bearing": 201.0, "latitude": 47.65618133544922, "longitude": -2.759830951690674, "speed": 3.8888888359069824 }, "stopId": "603", "timestamp": "1769804680", "trip": { "directionId": 0, "routeId": "21", "scheduleRelationship": "SCHEDULED", "startDate": "20260130", "startTime": "21:10:00", "tripId": "2-352976903" }, "vehicle": { "id": "64", "label": "97203", "licensePlate": "EA 888 WS" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1769804718" } }