Resource details
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
Learn more
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
❌19 errors, 17 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-08 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 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 3-15770648590 stop_sequence 2 arrival_time 07:25:45 (1783488345) is less than previous stop arrival_time 08:18:28 (1783491508) - times must increase between two sequential stops
- trip_id 3-15770648590 stop_sequence 2 arrival_time 07:25:45 (1783488345) is less than previous stop departure_time 08:18:28 (1783491508) - times must increase between two sequential stops
- trip_id 3-15770648590 stop_sequence 2 departure_time 07:25:45 (1783488345) is less than previous stop departure_time 08:18:28 (1783491508) - times must increase between two sequential stops
- trip_id 3-15770648590 stop_sequence 2 departure_time 07:25:45 (1783488345) is less than previous stop arrival_time 08:18:28 (1783491508) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 15 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 3-15787425813 stop_sequence 8 doesn't have arrival or departure
- trip_id 3-15770648591 stop_sequence 2 doesn't have arrival or departure
- trip_id 3-15770648591 stop_sequence 3 doesn't have arrival or departure
- trip_id 3-15787622404 stop_sequence 1 doesn't have arrival or departure
- trip_id 3-15787622404 stop_sequence 2 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 17 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-15787622404 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-15770648589 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-15787556874 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-15787425812 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-15787425813 is in TripUpdates but not in VehiclePositions feed
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 | 280 | 22 times (73 % 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 | 98 | 18 times (60 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 188 | 11 times (37 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 12 | 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) |
| E052 | Each vehicle should have a unique ID | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-08 at 23:20 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-07-08 at 23:20 Europe/Paris.
Deviation samedi 11 juillet Detour
En raison du triathlon du Mans le samedi 11/07, l'arrêt "Le Mans, Espal" ne sera pas desservi et reporté à l'arrêt "Le Mans, Lycée Sud".
Between 2026-07-08 at 00:00 Europe/Paris and 2026-07-11 at 23:59 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-07-08 at 23:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"end": "1783807140",
"start": "1783461600"
}
],
"cause": "DEMONSTRATION",
"descriptionText": {
"translation": [
{
"text": "En raison du triathlon du Mans le samedi 11/07, l'arrêt \"Le Mans, Espal\" ne sera pas desservi et reporté à l'arrêt \"Le Mans, Lycée Sud\"."
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"text": "Deviation samedi 11 juillet "
}
]
},
"informedEntity": [
{
"routeId": "942"
}
]
},
"id": "alert:6a4e60a3fdc6a32d35e681e5"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1783545620"
}
}