gtfs-rt Transport open dataset - GTFS RT Horaires temps réel réseau ALEOP Pays de la Loire for Réseaux interurbains Aléop - Pays de la Loire

Resource details

File name: GTFS RT Horaires temps réel réseau ALEOP Pays de la Loire

Format: gtfs-rt

Flux GTFS RT du réseau Aléop Pays de la Loire : Horaires temps réel

This resource file is part of the dataset Réseaux interurbains Aléop - Pays de la Loire.

Download availability

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 823 errors, 176 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-27 at 08:10 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 176 errors

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 FR:ServiceJourney::SN859500FERRE_6317700 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN858407FERRE_6317878 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN858408FERRE_6317877 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN857691FERRE_6318016 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN859073FERRE_6324680 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 176 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id T1 does not exist in the GTFS data routes.txt
route_id 01b does not exist in the GTFS data routes.txt
route_id 01b does not exist in the GTFS data routes.txt
route_id 22 does not exist in the GTFS data routes.txt
route_id 14 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 431 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id FR:ServiceJourney::SN859500FERRE_6317700 stop_id SNCF:87481002 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859500FERRE_6317700 stop_id SNCF:87590331 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859500FERRE_6317700 stop_id SNCF:87590349 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859500FERRE_6317700 stop_id SNCF:87590356 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859500FERRE_6317700 stop_id SNCF:87481564 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 35 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 312|26290016:T6|7:57:00 stop_sequence 16 arrival_time 08:24:40 (1761549880) is equal to previous stop arrival_time 08:24:40 (1761549880) - times must increase between two sequential stops
trip_id 312|26290016:T6|7:57:00 stop_sequence 16 arrival_time 08:24:40 (1761549880) is equal to previous stop departure_time 08:24:40 (1761549880) - times must increase between two sequential stops
trip_id 312|26290016:T6|7:57:00 stop_sequence 16 departure_time 08:24:40 (1761549880) is equal to previous stop departure_time 08:24:40 (1761549880) - times must increase between two sequential stops
trip_id 312|26290016:T6|7:57:00 stop_sequence 16 departure_time 08:24:40 (1761549880) is equal to previous stop arrival_time 08:24:40 (1761549880) - times must increase between two sequential stops
trip_id 312|26288524:T26|6:57:00 stop_sequence 34 arrival_time 08:11:00 (1761549060) is equal to previous stop arrival_time 08:11:00 (1761549060) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 5 errors

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.

Sample errors

trip_id 07|25819342:T1|8:10:00 stop_sequence 1 departure_time 08:10:21 (1761549021) is less than the same stop arrival_time 08:10:23 (1761549023) - departure time must be equal to or greater than arrival time
trip_id 415|26048747:T2|7:10:00 stop_sequence 17 departure_time 07:58:30 (1761548310) is less than the same stop arrival_time 08:05:19 (1761548719) - departure time must be equal to or greater than arrival time
trip_id FR:ServiceJourney::SN858798FERRE_6317855 stop_sequence 5 departure_time 07:36:00 (1761546960) is less than the same stop arrival_time 07:38:00 (1761547080) - departure time must be equal to or greater than arrival time
trip_id FR:ServiceJourney::SN857280FERRE_6318123 stop_sequence 8 departure_time 07:19:00 (1761545940) is less than the same stop arrival_time 07:45:00 (1761547500) - departure time must be equal to or greater than arrival time
trip_id FR:ServiceJourney::SN859797FERRE_6317582 stop_sequence 3 departure_time 07:57:00 (1761548220) is less than the same stop arrival_time 08:01:00 (1761548460) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 176 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id FR:ServiceJourney::SN859500FERRE_6317700 does not have a vehicle_id
trip_id FR:ServiceJourney::SN858407FERRE_6317878 does not have a vehicle_id
trip_id FR:ServiceJourney::SN858408FERRE_6317877 does not have a vehicle_id
trip_id FR:ServiceJourney::SN857691FERRE_6318016 does not have a vehicle_id
trip_id FR:ServiceJourney::SN859073FERRE_6324680 does not have a vehicle_id

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	3 132	30 times (100 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	3 132	30 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	25 380	30 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 154	30 times (100 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	687	25 times (83 % 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.	56	25 times (83 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-10-27 at 23:38 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-10-27 at 23:38 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1761604733"
  }
}