transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: GTFS-RT TripUpdate
Format: gtfs-rt
Download

Avance retard à un arrêt

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

Download availability

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

❌24 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-13 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors
  • vehicle_id 5f080bc543f0854b07bdbfb7 route_id K-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f080b7643f0854b07bdbec8 route_id K-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f080b6b43f0854b56c48d64 route_id 7-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5ee373a0f4e5a2422d241f1c route_id K-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f0f271a61de832db9874274 route_id 182-652 does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 2 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 21455042 stop_sequence 20 arrival_time 08:59:55 (1760338795) is less than previous stop departure_time 09:09:30 (1760339370) - times must increase between two sequential stops
  • trip_id 21455042 stop_sequence 21 arrival_time 09:05:57 (1760339157) is less than previous stop departure_time 09:13:30 (1760339610) - times must increase between two sequential stops

stop_time_update doesn't have arrival or departure E043 2 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id 21455042 stop_sequence 1 doesn't have arrival or departure
  • trip_id 21455041 stop_sequence 1 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 10 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 21454419 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21455139 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21455038 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21454407 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21454406 is in TripUpdates but not in VehiclePositions feed
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
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 466 25 times (83 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 246 25 times (83 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 123 18 times (60 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 38 15 times (50 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 6 5 times (17 % 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. 5 5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-10-14 at 04:46 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-10-14 at 04:46 Europe/Paris. You can look at the GTFS-RT documentation.

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