gtfs-rt Transport open dataset - GTFS-RT MOVE for Réseau urbain Move

Resource details

File name: GTFS-RT MOVE

Format: gtfs-rt

Flux temps réel du réseau MOVE

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

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

❌7 errors, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-15 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors

trip_id TGV-02-17_2 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
trip_id TGV-01-17_2 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
trip_id TGV-01-18_0 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 3 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id TGV-02-17_2 stop_sequence 1 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 1 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same
GTFS-rt trip_id TGV-01-17_2 stop_sequence 9 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 9 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same
GTFS-rt trip_id TGV-01-18_0 stop_sequence 9 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 9 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same

VehiclePosition and TripUpdate ID pairing mismatch E047 1 error

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Sample errors

trip_id TGV-02-17_2 and vehicle_id 5f6b208cf07eca4f072db425 pairing in VehiclePositions does not match trip_id TGV-01-18_0 and vehicle_id 5f6b208cf07eca4f072db425 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Warnings

ID in one feed missing from the other W003 2 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors

trip_id TGV-01-17_2 is in TripUpdates but not in VehiclePositions feed
trip_id TGV-01-18_0 is in TripUpdates but not in VehiclePositions feed

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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	325	30 times (100 % 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	304	30 times (100 % of validations)
W003	a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed	222	30 times (100 % of validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	58	24 times (80 % of validations)
E043	If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided	122	16 times (53 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	47	11 times (37 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	40	9 times (30 % 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.	11	6 times (20 % 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.	4	4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-16 at 02:40 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2026-03-16 at 02:40 Europe/Paris.

NOUVELLE FICHE HORAIRE à partir du 02 mars Modified service

Suite à des modifications d'horaires de trains, plusieurs services de la NAVETTE TGV sont modifiés : le service de 17h02 au départ de la GARE TER est avancé à 16h57 pour une arrivée à 17h19 à la GARE TGV (changement depuis le 16 février) le service de 17h48 au départ de la GARE TER est avancé à 17h40 pour une arrivée à 17h58 à la GARE TGV (changement à partir du 02 mars) le service de 20h20 au départ de la GARE TGV est décalé à 20h29 pour une arrivée à 20h50 à la GARE TER du lundi au jeudi (changement jusqu'au 02 avril) Veuillez cliquer ICI pour visualiser la nouvelle fiche horaire.

Between 2026-02-27 at 01:00 Europe/Paris and 2026-04-03 at 01:59 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-16 at 02:40 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "alert": {
        "activePeriod": [
          {
            "end": "1775174340",
            "start": "1772150400"
          }
        ],
        "cause": "OTHER_CAUSE",
        "descriptionText": {
          "translation": [
            {
              "text": "Suite à des modifications d'horaires de trains, plusieurs services de la NAVETTE TGV sont modifiés :\n\nle service de 17h02 au départ de la GARE TER est avancé à 16h57 pour une arrivée à 17h19 à la GARE TGV (changement depuis le 16 février)\nle service de 17h48 au départ de la GARE TER est avancé à 17h40 pour une arrivée à 17h58 à la GARE TGV (changement à partir du 02 mars)\nle service de 20h20 au départ de la GARE TGV est décalé à 20h29 pour une arrivée à 20h50 à la GARE TER du lundi au jeudi (changement jusqu'au 02 avril)\n\nVeuillez cliquer ICI pour visualiser la nouvelle fiche horaire."
            }
          ]
        },
        "effect": "MODIFIED_SERVICE",
        "headerText": {
          "translation": [
            {
              "text": "NOUVELLE FICHE HORAIRE à partir du 02 mars"
            }
          ]
        },
        "informedEntity": [
          {
            "routeId": "NAVETTE TGV"
          }
        ]
      },
      "id": "alert:699f0802ff36229af5c0c089"
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1773625234"
  }
}