Resource details
This resource file is part of the dataset Réseau urbain Mouvéo.
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
❌3,164 errors, 389 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:07 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 5 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 TAD_1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_3 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_6 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 5 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id TAD_1 does not exist in the GTFS data routes.txt
- route_id TAD_3 does not exist in the GTFS data routes.txt
- route_id TAD_4 does not exist in the GTFS data routes.txt
- route_id TAD_5 does not exist in the GTFS data routes.txt
- route_id TAD_6 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 2,235 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id TAD_1 stop_id ASO1 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO2 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO3 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO4 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO5 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 919 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 TAD_1 stop_sequence 17 arrival_time 08:40:37 (1775025637) is less than previous stop departure_time 08:40:44 (1775025644) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 18 arrival_time 08:40:38 (1775025638) is less than previous stop departure_time 08:40:45 (1775025645) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 19 arrival_time 08:40:39 (1775025639) is less than previous stop departure_time 08:40:46 (1775025646) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 20 arrival_time 08:40:40 (1775025640) is less than previous stop departure_time 08:40:47 (1775025647) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 21 arrival_time 08:40:41 (1775025641) is less than previous stop departure_time 08:40:48 (1775025648) - times must increase between two sequential stops
Warnings
timestamp not populated W001 203 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TAD_1 does not have a timestamp
- trip_id TAD_3 does not have a timestamp
- trip_id TAD_4 does not have a timestamp
- trip_id TAD_5 does not have a timestamp
- trip_id TAD_6 does not have a timestamp
vehicle_id not populated W002 186 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4_R_16:40_(geo3797) does not have a vehicle_id
- trip_id 4_R_15:10_(geo3796) does not have a vehicle_id
- trip_id 4_R_13:40_(geo3795) does not have a vehicle_id
- trip_id 4_R_12:10_(geo3794) does not have a vehicle_id
- trip_id 4_R_10:40_(geo3793) 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 49 | 5 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 49 | 5 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 10,100 | 5 times (83 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3,263 | 5 times (83 % of validations) |
| W001 | Timestamps should be populated for all elements | 1,045 | 5 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 940 | 5 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. | 9 | 3 times (50 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-02 at 02:30 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-04-02 at 02:30 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775089822"
}
}