Resource details

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

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

  • VehiclePosition
  • TripUpdate
  • ServiceAlert

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

Download availability

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

48 errors, 19 warnings

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

Errors

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 48 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id 3889813-26H-__LVE-L-Ma-Me-02 stop_sequence 13 has stop_id 1224 but GTFS stop_sequence 13 has stop_id 1447 - stop_ids should be the same
  • GTFS-rt trip_id 3889813-26H-__LVE-L-Ma-Me-02 stop_sequence 14 has stop_id 1496 but GTFS stop_sequence 14 has stop_id 1101 - stop_ids should be the same
  • GTFS-rt trip_id 3889813-26H-__LVE-L-Ma-Me-02 stop_sequence 15 has stop_id 1592 but GTFS stop_sequence 15 has stop_id 1224 - stop_ids should be the same
  • GTFS-rt trip_id 3889813-26H-__LVE-L-Ma-Me-02 stop_sequence 16 has stop_id 1436 but GTFS stop_sequence 16 has stop_id 1496 - stop_ids should be the same
  • GTFS-rt trip_id 3889813-26H-__LVE-L-Ma-Me-02 stop_sequence 17 has stop_id 1182 but GTFS stop_sequence 17 has stop_id 1592 - stop_ids should be the same

Warnings

ID in one feed missing from the other W003 19 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 3890040-26H-__LVE-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3889840-26H-__LVE-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3889972-26H-__LVE-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3980121-26H-__LVE-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3980029-26H-__LVE-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
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
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 459 27 times (100 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 677 17 times (63 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 8 5 times (19 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 6 3 times (11 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 2 2 times (7 % of validations)
E041 Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update 1 1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-08-05 at 02:09 Europe/Paris.

service_alerts (1) vehicle_positions (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2026-08-05 at 02:09 Europe/Paris.

Stop moved

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-08-05 at 02:09 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "activePeriod": [ { "end": "1785880799", "start": "1785708000" }, { "end": "1785880799", "start": "1785448800" } ], "cause": "CONSTRUCTION", "descriptionText": { "translation": [ { "language": "fr", "text": "En raison des travaux rue de la Croix Désilles, les arrêts suivants sont reportés du lundi 3 août au mardi 4 août, sur la ligne 3 :\n- L'arrêt Cap Sud est reporté à l'arrêt Henri Lemarié \n- L'arrêt Campus est reporté à l'arrêt IUT\n\nMerci de votre compréhension.\n\nRéseau MAT" } ] }, "effect": "STOP_MOVED", "headerText": { "translation": [ { "language": "fr", "text": "Ligne 3 - Arrêts reportés du lundi 3 août au mardi 4 août" } ] }, "informedEntity": [ { "agencyId": "MAT", "routeId": "3", "stopId": "1100" }, { "agencyId": "MAT", "routeId": "3", "stopId": "1101" }, { "agencyId": "MAT", "routeId": "3", "stopId": "1447" }, { "agencyId": "MAT", "routeId": "3", "stopId": "1448" } ] }, "id": "11" } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1785888599" } }