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
❌2 errors, 10 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-09 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 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 39-15854927875 stop_sequence 10 arrival_time 07:45:26 (1770619526) is less than previous stop arrival_time 08:13:10 (1770621190) - times must increase between two sequential stops
- trip_id 39-15854927875 stop_sequence 10 arrival_time 07:45:26 (1770619526) is less than previous stop departure_time 08:13:10 (1770621190) - times must increase between two sequential stops
Warnings
ID in one feed missing from the other W003 10 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 39-15787425818 is in TripUpdates but not in VehiclePositions feed
- trip_id 39-15787491349 is in TripUpdates but not in VehiclePositions feed
- trip_id 39-15854927877 is in TripUpdates but not in VehiclePositions feed
- trip_id 39-15787622405 is in TripUpdates but not in VehiclePositions feed
- trip_id 39-15837757457 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 | 227 | 19 times (66 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 123 | 18 times (62 % 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 | 24 | 12 times (41 % 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 | 5 times (17 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 10 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-09 at 23:58 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-02-09 at 23:58 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770677926"
}
}