gtfs-rt Transport open dataset - GTFS RT Horaires temps réel réseau ALEOP Pays de la Loire for Réseau interurbain 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éseau interurbain 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,242 errors, 122 warnings

Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-01 at 09:00 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 122 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::SN859503FERRE_8593804 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN859500FERRE_8593806 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN858407FERRE_8554470 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN858408FERRE_8554469 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id FR:ServiceJourney::SN858307FERRE_8554507 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 122 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 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 02 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 998 errors

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

Sample errors

trip_id FR:ServiceJourney::SN859503FERRE_8593804 stop_id SNCF:87481598 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859503FERRE_8593804 stop_id SNCF:87590828 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859503FERRE_8593804 stop_id SNCF:87590364 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859503FERRE_8593804 stop_id SNCF:87481564 does not exist in GTFS data stops.txt
trip_id FR:ServiceJourney::SN859503FERRE_8593804 stop_id SNCF:87590356 does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 122 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id FR:ServiceJourney::SN859503FERRE_8593804 does not have a vehicle_id
trip_id FR:ServiceJourney::SN859500FERRE_8593806 does not have a vehicle_id
trip_id FR:ServiceJourney::SN858407FERRE_8554470 does not have a vehicle_id
trip_id FR:ServiceJourney::SN858408FERRE_8554469 does not have a vehicle_id
trip_id FR:ServiceJourney::SN858307FERRE_8554507 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,799	28 times (97 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	3,799	28 times (97 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	31,298	28 times (97 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3,814	28 times (97 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	345	18 times (62 % 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.	42	18 times (62 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-02 at 00:45 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 2026-04-02 at 00:45 Europe/Paris. You can look at the GTFS-RT documentation.


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