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-10-27
99.1%
2025-10-28
99.5%
2025-10-29
97.4%
2025-10-30
98.9%
2025-10-31
98.2%
2025-11-01
100%
2025-11-02
100%
2025-11-03
97.7%
2025-11-04
98.9%
2025-11-05
99%
2025-11-06
96.8%
2025-11-07
96.4%
2025-11-08
100%
2025-11-09
100%
2025-11-10
99.4%
2025-11-11
100%
2025-11-12
98.6%
2025-11-13
99.5%
2025-11-14
99.1%
2025-11-15
99.4%
2025-11-16
100%
2025-11-17
96.8%
2025-11-18
98.6%
2025-11-19
97%
2025-11-20
93.4%
2025-11-21
99.4%
2025-11-22
100%
2025-11-23
100%
2025-11-24
99.5%
2025-11-25
97.9%
2025-11-26
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

76 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-25 at 08:03 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 22 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 366 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 183 trip_id chouette:VehicleJourney:9cc13582-74f4-4e03-9e7c-e24969614839:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 168 trip_id ext:12069 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 244 trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC 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 22 errors

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

Sample errors
  • vehicle_id 366 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 183 route_id MAURYScol60927 does not exist in the GTFS data routes.txt
  • vehicle_id 168 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 166 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 244 route_id BSAScol61137 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 366 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 183 stop_id bre_vannes_2024_2025.18829 does not exist in GTFS data stops.txt
  • vehicle_id 168 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 166 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 244 stop_id bre_vannes_2024_2025.18093 does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 7 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 353 trip_id 22-2432761857 at (47.695244,-2.553286) 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.71764,-2.887934) 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 65 trip_id 2-73203730 at (47.713528,-2.763398) 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 250 trip_id 22-6157369345 at (47.741917,-2.686469) 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-7-LM_____ at (47.627068,-2.83085) 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 598180 has vehicle.id 297 which is used by more than one vehicle in the feed
  • entity ID 598139 has vehicle.id 97 which is used by more than one vehicle in the feed
  • entity ID 597876 has vehicle.id 334 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 5 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 247 does not have a timestamp
  • vehicle_id 21 does not have a timestamp
  • vehicle_id 381 does not have a timestamp
  • vehicle_id 27 does not have a timestamp
  • vehicle_id 85 does not have a timestamp

vehicle speed is unrealistic W004 1 error

vehicle.position.speed has an unrealistic speed that may be incorrect

Sample errors
  • vehicle.id 252 speed of 26.38889 m/s (59.03 mph) is unrealistic
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 607 21 times (72 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 370 21 times (72 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 370 21 times (72 % of validations)
W001 Timestamps should be populated for all elements 158 21 times (72 % 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. 103 19 times (66 % of validations)
E052 Each vehicle should have a unique ID 25 13 times (45 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 13 11 times (38 % 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 6 times (21 % 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 1 1 times (3 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 6 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-26 at 02:39 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-11-26 at 02:39 Europe/Paris. You can look at the GTFS-RT documentation.

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