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

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

⚠️21 warnings

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

Warnings

timestamp not populated W001 11 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-712507408 does not have a timestamp
  • trip_id 1-712507407 does not have a timestamp
  • trip_id 1-712638491 does not have a timestamp
  • trip_id 1-712441871 does not have a timestamp
  • trip_id 1-712704003 does not have a timestamp

vehicle_id not populated W002 10 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
W001 Timestamps should be populated for all elements 1 752 22 times (73 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 547 22 times (73 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3 201 21 times (70 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 185 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. 6 6 times (20 % of validations)

GTFS-RT feed content

Entities

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

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