Resource details

File name: Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt

Le message TripUpdate au format GTFS-RT est disponibles dans ce flux.

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

Download availability

2026-07-05
93.7%
2026-07-06
100%
2026-07-07
100%
2026-07-08
100%
2026-07-09
100%
2026-07-10
100%
2026-07-11
100%
2026-07-12
94.4%
2026-07-13
100%
2026-07-14
94.3%
2026-07-15
100%
2026-07-16
100%
2026-07-17
100%
2026-07-18
100%
2026-07-19
93.8%
2026-07-20
100%
2026-07-21
100%
2026-07-22
100%
2026-07-23
100%
2026-07-24
100%
2026-07-25
100%
2026-07-26
94.2%
2026-07-27
100%
2026-07-28
99.5%
2026-07-29
100%
2026-07-30
99.4%
2026-07-31
100%
2026-08-01
100%
2026-08-02
94%
2026-08-03
100%
2026-08-04
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

15 errors, 4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-04 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_updates have the same stop_id E037 2 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 15-25624587 has repeating stop_id 6248 at stop_sequence 11 - sequential stop_ids should be different
  • trip_id 15-25952266 has repeating stop_id 6248 at stop_sequence 7 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 13 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id 15-25624587 stop_sequence 11 has stop_id 6248 but GTFS stop_sequence 11 has stop_id 9632 - stop_ids should be the same
  • GTFS-rt trip_id 15-25624587 stop_sequence 12 has stop_id 9632 but GTFS stop_sequence 12 has stop_id 9633 - stop_ids should be the same
  • GTFS-rt trip_id 15-25624587 stop_sequence 13 has stop_id 9633 but GTFS stop_sequence 13 has stop_id 9634 - stop_ids should be the same
  • GTFS-rt trip_id 15-25624587 stop_sequence 14 has stop_id 9634 but GTFS stop_sequence 14 has stop_id 8772 - stop_ids should be the same
  • GTFS-rt trip_id 15-25624587 stop_sequence 15 has stop_id 8772 but GTFS stop_sequence 15 has stop_id 8774 - stop_ids should be the same

Warnings

vehicle_id not populated W002 4 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 15-710737929 does not have a vehicle_id
  • trip_id 15-727121931 does not have a vehicle_id
  • trip_id 15-25624587 does not have a vehicle_id
  • trip_id 15-25952266 does not have a vehicle_id
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
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 124 23 times (77 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 846 23 times (77 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 161 23 times (77 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-08-05 at 01:35 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-08-05 at 01:35 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "31", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": 0, "time": "1785840720", "uncertainty": 0 }, "departure": { "delay": 300, "time": "1785841020", "uncertainty": 0 }, "stopId": "6848", "stopSequence": 1 }, { "arrival": { "delay": 240, "time": "1785841080", "uncertainty": 0 }, "departure": { "delay": 245, "time": "1785841085", "uncertainty": 0 }, "stopId": "6851", "stopSequence": 2 }, { "arrival": { "delay": 240, "time": "1785841260", "uncertainty": 0 }, "departure": { "delay": 245, "time": "1785841265", "uncertainty": 0 }, "stopId": "15641", "stopSequence": 3 }, { "arrival": { "delay": 120, "time": "1785841560", "uncertainty": 0 }, "departure": { "delay": 125, "time": "1785841565", "uncertainty": 0 }, "stopId": "19561", "stopSequence": 4 }, { "arrival": { "delay": 120, "time": "1785841980", "uncertainty": 0 }, "departure": { "delay": 125, "time": "1785841985", "uncertainty": 0 }, "stopId": "18503", "stopSequence": 5 }, { "arrival": { "delay": 180, "time": "1785842100", "uncertainty": 0 }, "departure": { "delay": 185, "time": "1785842105", "uncertainty": 0 }, "stopId": "7892", "stopSequence": 6 }, { "arrival": { "delay": 180, "time": "1785842400", "uncertainty": 0 }, "departure": { "delay": 185, "time": "1785842405", "uncertainty": 0 }, "stopId": "9013", "stopSequence": 7 }, { "arrival": { "delay": 180, "time": "1785843180", "uncertainty": 100 }, "stopId": "6248", "stopSequence": 8 } ], "timestamp": "1785843255", "trip": { "routeId": "42", "scheduleRelationship": "SCHEDULED", "tripId": "15-711327747" }, "vehicle": {} } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1785886545" } }