gtfs-rt Transport open dataset - GTFS RT Mouveo 2 for Réseau urbain Mouvéo

Resource details

File name: GTFS RT Mouveo 2

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Mouvéo.

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

❌16 errors, 3 warnings

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

vehicle_id 411 trip_id TAD_5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 5 trip_id TAD_4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 315 trip_id TAD_6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 316 trip_id TAD_1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 409 trip_id TAD_3 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

vehicle_id 411 route_id TAD_5 does not exist in the GTFS data routes.txt
vehicle_id 5 route_id TAD_4 does not exist in the GTFS data routes.txt
vehicle_id 315 route_id TAD_6 does not exist in the GTFS data routes.txt
vehicle_id 316 route_id TAD_1 does not exist in the GTFS data routes.txt
vehicle_id 409 route_id TAD_3 does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id 411 stop_id ASO437 does not exist in GTFS data stops.txt
vehicle_id 5 stop_id ASO436 does not exist in GTFS data stops.txt
vehicle_id 315 stop_id ASO330 does not exist in GTFS data stops.txt
vehicle_id 316 stop_id ASO322 does not exist in GTFS data stops.txt
vehicle_id 409 stop_id ASO443 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 1 error

The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.

Sample errors

vehicle.id 315 at (50.788,2.162809) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Warnings

timestamp not populated W001 3 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 318 does not have a timestamp
vehicle_id 322 does not have a timestamp
vehicle_id 324 does not have a timestamp

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	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	46	5 times (83 % of validations)
E028	The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.	12	4 times (67 % of validations)
W001	Timestamps should be populated for all elements	8	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.

vehicle_positions

Decoded 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": "1775089827"
  }
}