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 MAT.

Download availability

2025-10-12
100%
2025-10-13
100%
2025-10-14
100%
2025-10-15
100%
2025-10-16
100%
2025-10-17
100%
2025-10-18
100%
2025-10-19
100%
2025-10-20
100%
2025-10-21
100%
2025-10-22
100%
2025-10-23
100%
2025-10-24
100%
2025-10-25
100%
2025-10-26
100%
2025-10-27
100%
2025-10-28
100%
2025-10-29
100%
2025-10-30
100%
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%
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

54 errors, 159 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-10 at 08:00 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 54 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 3690770 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3690645 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3684074 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3684067 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3690617 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 51 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 3690770 does not have a vehicle_id
  • trip_id 3690645 does not have a vehicle_id
  • trip_id 3684074 does not have a vehicle_id
  • trip_id 3684067 does not have a vehicle_id
  • trip_id 3690766 does not have a vehicle_id

schedule_relationship not populated W009 108 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 3690770 stop_id 1090 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 3690770 does not have a schedule_relationship
  • trip_id 3690645 stop_id 1554 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 3690645 does not have a schedule_relationship
  • trip_id 3684074 stop_id 1440 (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 1 225 32 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2 450 32 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 926 31 times (97 % of validations)
E012 No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp 45 1 times (3 % of validations)

GTFS-RT feed content

Entities

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

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