Resource details

File name: GTFS RT Position véhicules 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 : Position des véhicules

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

Download availability

2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
100%
2026-01-16
100%
2026-01-17
100%
2026-01-18
100%
2026-01-19
100%
2026-01-20
100%
2026-01-21
100%
2026-01-22
100%
2026-01-23
100%
2026-01-24
100%
2026-01-25
100%
2026-01-26
100%
2026-01-27
100%
2026-01-28
100%
2026-01-29
100%
2026-01-30
100%
2026-01-31
100%
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

⚠️92 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-30 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

schedule_relationship not populated W009 92 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 2614086202 does not have a schedule_relationship
  • trip_id 2630587810 does not have a schedule_relationship
  • trip_id 2612913007 does not have a schedule_relationship
  • trip_id 2629524301 does not have a schedule_relationship
  • trip_id 2630470308 does not have a schedule_relationship
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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1,611 14 times (100 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 26 10 times (71 % of validations)
E052 Each vehicle should have a unique ID 85 10 times (71 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-31 at 01:20 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-31 at 01:20 Europe/Paris. You can look at the GTFS-RT documentation.

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