Resource details

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

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • TripUpdate

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

Download availability

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

112 errors, 130 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 111 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 1-691666966 stop_sequence 22 arrival_time 09:10:12 (1775027412) is equal to previous stop departure_time 09:10:12 (1775027412) - times must increase between two sequential stops
  • trip_id 1-691666966 stop_sequence 22 departure_time 09:10:12 (1775027412) is equal to previous stop departure_time 09:10:12 (1775027412) - times must increase between two sequential stops
  • trip_id 1-691470341 stop_sequence 12 departure_time 09:10:19 (1775027419) is equal to previous stop departure_time 09:10:19 (1775027419) - times must increase between two sequential stops
  • trip_id 1-724762628 stop_sequence 17 arrival_time 09:14:19 (1775027659) is equal to previous stop arrival_time 09:14:19 (1775027659) - times must increase between two sequential stops
  • trip_id 1-724762628 stop_sequence 17 arrival_time 09:14:19 (1775027659) is equal to previous stop departure_time 09:14:19 (1775027659) - 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 1-691470341 stop_sequence 12 departure_time 09:10:19 (1775027419) is less than the same stop arrival_time 09:10:37 (1775027437) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 70 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-691666966 does not have a timestamp
  • trip_id 1-691470341 does not have a timestamp
  • trip_id 1-712376334 does not have a timestamp
  • trip_id 1-712704027 does not have a timestamp
  • trip_id 1-729219110 does not have a timestamp

vehicle_id not populated W002 60 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-729153542 does not have a vehicle_id
  • trip_id 1-729219111 does not have a vehicle_id
  • trip_id 1-729219109 does not have a vehicle_id
  • trip_id 1-724762633 does not have a vehicle_id
  • trip_id 1-724762631 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
W001 Timestamps should be populated for all elements 1,977 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1,744 24 times (80 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3,423 22 times (73 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 119 19 times (63 % 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. 4 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-01 at 21:38 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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-04-01 at 21:38 Europe/Paris. You can look at the GTFS-RT documentation.

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