Resource details
GTFS-RT sur le territoire de la Métropole Européenne de Lille :
- mises à jour des trajets : retards, annulations et itinéraires modifiés
- alertes de service : arrêt déplacé et événements imprévus affectant une station, un itinéraire ou l’ensemble du réseau
- position du véhicule : informations sur les véhicules, y compris leur localisation et la densité du trafic
This resource file is part of the dataset Réseau urbain ilévia.
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
❌54 errors, 252 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-25 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 5493680 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 53 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 5467119 stop_sequence 12 departure_time 09:08:37 (1784963317) is less than previous stop departure_time 09:09:01 (1784963341) - times must increase between two sequential stops
- trip_id 5467338 stop_sequence 22 departure_time 09:11:01 (1784963461) is less than previous stop departure_time 09:11:19 (1784963479) - times must increase between two sequential stops
- trip_id 5467344 stop_sequence 29 departure_time 09:16:19 (1784963779) is less than previous stop departure_time 09:16:20 (1784963780) - times must increase between two sequential stops
- trip_id 5467344 stop_sequence 39 departure_time 09:26:45 (1784964405) is less than previous stop departure_time 09:27:04 (1784964424) - times must increase between two sequential stops
- trip_id 5467358 stop_sequence 9 departure_time 09:08:51 (1784963331) is less than previous stop departure_time 09:09:11 (1784963351) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 252 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5466468 does not have a vehicle_id
- trip_id 5466498 does not have a vehicle_id
- trip_id 5466529 does not have a vehicle_id
- trip_id 5466554 does not have a vehicle_id
- trip_id 5467119 does not have a vehicle_id
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1,358 | 30 times (97 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 7,759 | 30 times (97 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-26 at 02:22 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-07-26 at 02:22 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785025350"
}
}