Resource details

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

Avance retard à un arrêt

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

Download availability

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

169 errors, 18 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-17 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors
  • vehicle_id 5f0efa8b61de832d70f03ef4 route_id 222-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f0f29e061de832d61873c85 route_id 221-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f0f27f861de832d848b0444 route_id 250-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f080b8843f0854ae642aae1 route_id K-652 does not exist in the GTFS data routes.txt
  • vehicle_id 5f0f26e461de832da97c05a7 route_id 8-652 does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 3 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 21454443 stop_sequence 31 arrival_time 07:37:14 (1763361434) is less than previous stop arrival_time 07:37:28 (1763361448) - times must increase between two sequential stops
  • trip_id 21454443 stop_sequence 31 arrival_time 07:37:14 (1763361434) is less than previous stop departure_time 07:37:28 (1763361448) - times must increase between two sequential stops
  • trip_id 21454971 stop_sequence 11 arrival_time 07:30:59 (1763361059) is less than previous stop departure_time 07:31:10 (1763361070) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 2 errors

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.

Sample errors
  • trip_id 21454947 stop_sequence 25 departure_time 07:37:13 (1763361433) is less than the same stop arrival_time 07:41:57 (1763361717) - departure time must be equal to or greater than arrival time
  • trip_id 21454858 stop_sequence 28 departure_time 07:47:24 (1763362044) is less than the same stop arrival_time 07:48:42 (1763362122) - departure time must be equal to or greater than arrival time

stop_time_update doesn't have arrival or departure E043 92 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 21454952 stop_sequence 1 doesn't have arrival or departure
  • trip_id 21454952 stop_sequence 2 doesn't have arrival or departure
  • trip_id 21454952 stop_sequence 11 doesn't have arrival or departure
  • trip_id 21454998 stop_sequence 2 doesn't have arrival or departure
  • trip_id 21455129 stop_sequence 15 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 18 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 21454904 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21454947 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21455117 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21454961 is in TripUpdates but not in VehiclePositions feed
  • trip_id 21455041 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 903 23 times (77 % 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 276 21 times (70 % 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 673 13 times (43 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 79 11 times (37 % 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. 30 10 times (33 % 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. 8 5 times (17 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 2 2 times (7 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 6 2 times (7 % of validations)

GTFS-RT feed content

Entities

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

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