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-11-21
97.9%
2025-11-22
98.7%
2025-11-23
97.3%
2025-11-24
97.4%
2025-11-25
93.3%
2025-11-26
98.7%
2025-11-27
98.1%
2025-11-28
98.1%
2025-11-29
98.8%
2025-11-30
98%
2025-12-01
97.9%
2025-12-02
98.1%
2025-12-03
98.8%
2025-12-04
87.7%
2025-12-05
96.1%
2025-12-06
98.7%
2025-12-07
97%
2025-12-08
96.3%
2025-12-09
96.6%
2025-12-10
96.9%
2025-12-11
83.8%
2025-12-12
93.5%
2025-12-13
98.3%
2025-12-14
97%
2025-12-15
87.9%
2025-12-16
90.4%
2025-12-17
87.5%
2025-12-18
83.7%
2025-12-19
94.2%
2025-12-20
98.4%
2025-12-21
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-20 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 255 | 22 times (71 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 158 | 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 | 37 | 13 times (42 % 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. | 57 | 9 times (29 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 2 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-21 at 04:50 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 2025-12-21 at 04:50 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766289022"
}
}