Resource details

File name: Mises à jour des trajets en temps réel GTFS-RT
Format: gtfs-rt

Les mises à jour des trajets vous informent des fluctuations d’horaires.
Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.

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

Download availability

2026-06-30
100%
2026-07-01
100%
2026-07-02
100%
2026-07-03
100%
2026-07-04
100%
2026-07-05
100%
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
100%
2026-07-13
100%
2026-07-14
100%
2026-07-15
100%
2026-07-16
100%
2026-07-17
100%
2026-07-18
100%
2026-07-19
100%
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
100%
2026-07-27
100%
2026-07-28
100%
2026-07-29
100%
2026-07-30
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

1,780 errors, 5,447 warnings

Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.

Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-30 at 09:06 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 24 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id 18203938 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18203886 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18203668 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18203659 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18203907 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 39 errors

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

Sample errors
  • route_id JDP does not exist in the GTFS data routes.txt
  • route_id JDP does not exist in the GTFS data routes.txt
  • route_id NAV does not exist in the GTFS data routes.txt
  • route_id NAV does not exist in the GTFS data routes.txt
  • route_id NAV does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 17879884 stop_id P AMIS_1 does not exist in GTFS data stops.txt
  • trip_id 17879903 stop_id P AMIS_3 does not exist in GTFS data stops.txt
  • trip_id 17859242 stop_id FIC_LIB2 does not exist in GTFS data stops.txt
  • trip_id 17859240 stop_id FIC_LIB2 does not exist in GTFS data stops.txt
  • trip_id 17858979 stop_id FIC_LIB2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 74 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 17894599 stop_sequence 4 arrival_time 09:10:24 (1785395424) is less than previous stop arrival_time 09:10:28 (1785395428) - times must increase between two sequential stops
  • trip_id 17894599 stop_sequence 4 arrival_time 09:10:24 (1785395424) is less than previous stop departure_time 09:10:28 (1785395428) - times must increase between two sequential stops
  • trip_id 17894599 stop_sequence 4 departure_time 09:10:24 (1785395424) is less than previous stop departure_time 09:10:28 (1785395428) - times must increase between two sequential stops
  • trip_id 17894599 stop_sequence 4 departure_time 09:10:24 (1785395424) is less than previous stop arrival_time 09:10:28 (1785395428) - times must increase between two sequential stops
  • trip_id 17902130 stop_sequence 2 arrival_time 09:07:42 (1785395262) is less than previous stop arrival_time 09:07:44 (1785395264) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 1 error

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 17857561 stop_sequence 0 departure_time 00:02:31 (1785362551) is less than the same stop arrival_time 23:55:47 (1785448547) - departure time must be equal to or greater than arrival time

GTFS-rt stop_sequence not found in GTFS data E051 1,354 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors
  • GTFS-rt trip_id 17879521 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 17879884 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 17890641 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 17879514 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 18192548 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 1,378 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 17879521 does not have a timestamp
  • trip_id 17879884 does not have a timestamp
  • trip_id 17890641 does not have a timestamp
  • trip_id 17879514 does not have a timestamp
  • trip_id 18192548 does not have a timestamp

vehicle_id not populated W002 1,313 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 17879521 does not have a vehicle_id
  • trip_id 17879884 does not have a vehicle_id
  • trip_id 17890641 does not have a vehicle_id
  • trip_id 17879514 does not have a vehicle_id
  • trip_id 18192548 does not have a vehicle_id

schedule_relationship not populated W009 2,756 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 17879521 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 17879521 does not have a schedule_relationship
  • trip_id 17879884 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 17879884 does not have a schedule_relationship
  • trip_id 17890641 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
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 4,315 30 times (100 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 1,148 30 times (100 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 5,094 30 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 13,964 30 times (100 % of validations)
W001 Timestamps should be populated for all elements 38,851 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 37,051 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 77,702 30 times (100 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 34,536 29 times (97 % 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. 48 21 times (70 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 4,193 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-07-31 at 00:32 Europe/Paris.

trip_updates (4) 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-07-31 at 00:32 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "trip:17901968", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1785450762" }, "departure": { "time": "1785450762" }, "stopId": "ST_JJ", "stopSequence": 0 } ], "trip": { "routeId": "17", "tripId": "17901968" }, "vehicle": { "id": "268436070" } } }, { "id": "trip:18192678", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1785450656" }, "departure": { "time": "1785450656" }, "stopId": "DE_RO_2", "stopSequence": 0 }, { "arrival": { "time": "1785450676" }, "departure": { "time": "1785450676" }, "stopId": "ECOLES_2", "stopSequence": 1 }, { "arrival": { "time": "1785450737" }, "departure": { "time": "1785450737" }, "stopId": "TECHNO_1", "stopSequence": 2 } ], "trip": { "routeId": "02", "tripId": "18192678" }, "vehicle": { "id": "268435628" } } }, { "id": "trip:18192557", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1785450719" }, "departure": { "time": "1785450719" }, "stopId": "OCEAN2_1", "stopSequence": 0 } ], "trip": { "routeId": "03", "tripId": "18192557" } } }, { "id": "trip:18192674", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1785450770" }, "departure": { "time": "1785450770" }, "stopId": "KENNED_6", "stopSequence": 0 }, { "arrival": { "time": "1785450937" }, "departure": { "time": "1785450937" }, "stopId": "RAMPES_1", "stopSequence": 1 } ], "trip": { "routeId": "02", "tripId": "18192674" }, "vehicle": { "id": "268435913" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1785450774" } }