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 :

TripUpdate
VehiclePosition
Alert

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

Download availability

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

1 error, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-22 at 14:08 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

VehiclePosition and TripUpdate ID pairing mismatch E047 1 error

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Sample errors
  • trip_id 3-15888416772 and vehicle_id 673f40548578248c62a9b21b pairing in VehiclePositions does not match trip_id 3-15888351234 and vehicle_id 673f40548578248c62a9b21b pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Warnings

ID in one feed missing from the other W003 6 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 3-15888351234 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3-15888089089 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3-15888154625 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3-15888416770 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3-15888351238 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 325 22 times (71 % 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. 124 21 times (68 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 71 21 times (68 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 174 18 times (58 % 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. 1 1 times (3 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-07-23 at 03:35 Europe/Paris.

service_alerts (3) 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 2025-07-23 at 03:35 Europe/Paris.

Le Mans/ESPAL RUE DE HONGRIE - Arrêt déplacé Stop moved

En raison de travaux, l'arrêt Le Mans/ESPAL RUE DE HONGRIE est transféré à l'arrêt Terminus Tram ESPAL Rue de l'Esterel.

Between 2025-04-22 at 02:30 Europe/Paris and 2026-01-01 at 00:59 Europe/Paris

Ligne 22GO : retards à prévoir en raison des travaux sur le pont-rail de Belle-Fontaine - Du 21 juillet au 01 août Unknown effect

Between 2025-07-10 at 17:52 Europe/Paris and 2025-08-02 at 01:59 Europe/Paris

Ligne 25GO : Saint-Biez-en-Belin/VENUS - reporté devant "La Cagette" sur l'axe principal de la D32 - Travaux du 21 juillet au 03 août 2025 Stop moved

Between 2025-07-11 at 19:28 Europe/Paris and 2025-08-04 at 01:59 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-07-23 at 03:35 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "activePeriod": [ { "end": "1767225540", "start": "1745281800" } ], "cause": "CONSTRUCTION", "descriptionText": { "translation": [ { "text": "En raison de travaux, l'arrêt Le Mans/ESPAL RUE DE HONGRIE est transféré à l'arrêt Terminus Tram ESPAL Rue de l'Esterel." } ] }, "effect": "STOP_MOVED", "headerText": { "translation": [ { "text": "Le Mans/ESPAL RUE DE HONGRIE - Arrêt déplacé" } ] }, "informedEntity": [ { "routeId": "943" }, { "stopId": "7548" }, { "stopId": "7549" }, { "routeId": "942" } ] }, "id": "alert:67acacbd859895174c675c15" }, { "alert": { "activePeriod": [ { "end": "1754092740", "start": "1752162720" } ], "cause": "CONSTRUCTION", "headerText": { "translation": [ { "text": "Ligne 22GO : retards à prévoir en raison des travaux sur le pont-rail de Belle-Fontaine - Du 21 juillet au 01 août" } ] }, "informedEntity": [ { "routeId": "945" } ] }, "id": "alert:686fc4f0fbf64693aee05655" }, { "alert": { "activePeriod": [ { "end": "1754265540", "start": "1752254880" } ], "cause": "CONSTRUCTION", "effect": "STOP_MOVED", "headerText": { "translation": [ { "text": "Ligne 25GO : Saint-Biez-en-Belin/VENUS - reporté devant \"La Cagette\" sur l'axe principal de la D32 - Travaux du 21 juillet au 03 août 2025" } ] }, "informedEntity": [ { "routeId": "941" }, { "stopId": "1464" } ] }, "id": "alert:68712d639bfd113eaa120b3d" } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1753234531" } }