Resource details
Flux temps réel du réseau MOVE
This resource file is part of the dataset Réseau urbain Move.
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
❌12 errors, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-21 at 08:07 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-01-17_1 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-01-18_2 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-02-16_0 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
stop_time_update doesn't have arrival or departure E043 6 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id TGV-01-17_1 stop_sequence 5 doesn't have arrival or departure
- trip_id TGV-01-17_1 stop_sequence 6 doesn't have arrival or departure
- trip_id TGV-01-18_2 stop_sequence 5 doesn't have arrival or departure
- trip_id TGV-01-18_2 stop_sequence 6 doesn't have arrival or departure
- trip_id TGV-02-16_0 stop_sequence 4 doesn't have arrival or departure
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-01-17_1 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_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-02-16_0 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
Warnings
ID in one feed missing from the other W003 1 error
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_1 is in TripUpdates but not in VehiclePositions feed
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 | 415 | 29 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 | 398 | 29 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 | 243 | 29 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. | 83 | 23 times (79 % 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 | 70 | 11 times (38 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 51 | 8 times (28 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 21 | 6 times (21 % 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. | 5 | 5 times (17 % 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. | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-22 at 01:27 Europe/Paris.
service_alerts (3) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-02-22 at 01:27 Europe/Paris.
NAVETTE TGV - Modification service à compter du 16 février 2026 Modified service
À compter du 16 FÉVRIER 2026, le service de 17h02 au départ de la Gare TER est avancé à 16H57. Vous trouverez ICI la nouvelle fiche horaire.
Between 2026-02-06 at 01:00 Europe/Paris and 2026-03-16 at 00:59 Europe/Paris
Modifications de services dues aux conditions climatiques Detour
En raison des conditions climatiques actuelles, une déviation est mise en place pour la NAVETTE TGV du lundi 16 février jusqu'au dimanche 22 février inclus : l'arrêt CROIX BLANCHE est transféré à l'arrêt KENNEDY l'arrêt ZI NORD est transféré à l'arrêt JOUHAUX
Between 2026-02-16 at 01:00 Europe/Paris and 2026-02-23 at 00:59 Europe/Paris
Nouvelle fiche horaire à compter du lundi 02 mars Additional service
Une nouvelle fiche horaire est mise en place à compter du lundi 02 mars. Sur le service de 13:02 au départ de la Mairie de Montoire pour Vendôme, 3 nouveaux arrêts seront desservis : arrêt VILLIERS-Avenue Colin à 13:23 arrêt VILLIERS-La Poste à 13:25 arrêt VILLIERS-Groupe scolaire à 13:26 Veuillez cliquer ICI pour consulter la fiche horaire.
Between 2026-02-18 at 01:00 Europe/Paris and 2026-03-10 at 00:59 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-02-22 at 01:27 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"end": "1773619140",
"start": "1770336000"
}
],
"cause": "OTHER_CAUSE",
"descriptionText": {
"translation": [
{
"text": "À compter du 16 FÉVRIER 2026, le service de 17h02 au départ de la Gare TER est avancé à 16H57.\n\nVous trouverez ICI la nouvelle fiche horaire."
}
]
},
"effect": "MODIFIED_SERVICE",
"headerText": {
"translation": [
{
"text": "NAVETTE TGV - Modification service à compter du 16 février 2026"
}
]
},
"informedEntity": [
{
"routeId": "NAVETTE TGV"
}
]
},
"id": "alert:69860517b43d113a8606f428"
},
{
"alert": {
"activePeriod": [
{
"end": "1771804740",
"start": "1771200000"
}
],
"cause": "WEATHER",
"descriptionText": {
"translation": [
{
"text": "En raison des conditions climatiques actuelles, une déviation est mise en place pour la NAVETTE TGV du lundi 16 février jusqu'au dimanche 22 février inclus :\n\nl'arrêt CROIX BLANCHE est transféré à l'arrêt KENNEDY\nl'arrêt ZI NORD est transféré à l'arrêt JOUHAUX"
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"text": "Modifications de services dues aux conditions climatiques"
}
]
},
"informedEntity": [
{
"routeId": "NAVETTE TGV"
},
{
"stopId": "VENDOME - CROIX BLANCHE"
},
{
"stopId": "VENDOME - ZI NORD"
}
]
},
"id": "alert:69931a6533566e95d7c0d3ec"
},
{
"alert": {
"activePeriod": [
{
"end": "1773100740",
"start": "1771372800"
}
],
"cause": "OTHER_CAUSE",
"descriptionText": {
"translation": [
{
"text": "Une nouvelle fiche horaire est mise en place à compter du lundi 02 mars.\n\nSur le service de 13:02 au départ de la Mairie de Montoire pour Vendôme, 3 nouveaux arrêts seront desservis :\n\narrêt VILLIERS-Avenue Colin à 13:23\narrêt VILLIERS-La Poste à 13:25\narrêt VILLIERS-Groupe scolaire à 13:26\n\nVeuillez cliquer ICI pour consulter la fiche horaire."
}
]
},
"effect": "ADDITIONAL_SERVICE",
"headerText": {
"translation": [
{
"text": "Nouvelle fiche horaire à compter du lundi 02 mars"
}
]
},
"informedEntity": [
{
"routeId": "LIGNE M"
}
]
},
"id": "alert:699595b20b617235093dc8f6"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771720049"
}
}