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

41 errors, 107 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 40 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-729219125 stop_sequence 3 arrival_time 13:03:32 (1777719812) is equal to previous stop arrival_time 13:03:32 (1777719812) - times must increase between two sequential stops
  • trip_id 1-729219125 stop_sequence 3 arrival_time 13:03:32 (1777719812) is equal to previous stop departure_time 13:03:32 (1777719812) - times must increase between two sequential stops
  • trip_id 1-729219125 stop_sequence 3 departure_time 13:03:32 (1777719812) is equal to previous stop departure_time 13:03:32 (1777719812) - times must increase between two sequential stops
  • trip_id 1-729219125 stop_sequence 3 departure_time 13:03:32 (1777719812) is equal to previous stop arrival_time 13:03:32 (1777719812) - times must increase between two sequential stops
  • trip_id 1-729219078 stop_sequence 3 arrival_time 12:06:32 (1777716392) is equal to previous stop arrival_time 12:06:32 (1777716392) - 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-763232263 stop_sequence 3 departure_time 09:08:53 (1777705733) is less than the same stop arrival_time 09:08:54 (1777705734) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 56 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-695533582 does not have a timestamp
  • trip_id 1-712704006 does not have a timestamp
  • trip_id 1-775880720 does not have a timestamp
  • trip_id 1-729350157 does not have a timestamp
  • trip_id 1-763232263 does not have a timestamp

vehicle_id not populated W002 51 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-712507407 does not have a vehicle_id
  • trip_id 1-712638491 does not have a vehicle_id
  • trip_id 1-712441871 does not have a vehicle_id
  • trip_id 1-712704003 does not have a vehicle_id
  • trip_id 1-712441875 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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2,169 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 1,515 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1,337 24 times (80 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 21 7 times (23 % 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-05-02 at 22:20 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-05-02 at 22:20 Europe/Paris. You can look at the GTFS-RT documentation.

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