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

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

9 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-13 at 09:13 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors
  • trip_id LA-02-03_0_2 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
  • trip_id LA-01-03_0_2 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 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 LA-01-05_0_2 stop_sequence 1 arrival_time 08:47:24 (1776062844) is less than previous stop arrival_time 08:49:22 (1776062962) - times must increase between two sequential stops
  • trip_id LA-01-05_0_2 stop_sequence 1 arrival_time 08:47:24 (1776062844) is less than previous stop departure_time 08:49:57 (1776062997) - times must increase between two sequential stops
  • trip_id LA-01-05_0_2 stop_sequence 1 departure_time 08:47:24 (1776062844) is less than previous stop departure_time 08:49:57 (1776062997) - times must increase between two sequential stops
  • trip_id LA-01-05_0_2 stop_sequence 1 departure_time 08:47:24 (1776062844) is less than previous stop arrival_time 08:49:22 (1776062962) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 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 LA-02-03_0_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 LA-01-03_0_2 stop_sequence 23 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 23 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 LA-02-04_0_2 and vehicle_id 5f6b207af07eca4ec325afdc pairing in VehiclePositions does not match trip_id LA-01-02_0_3 and vehicle_id 5f6b207af07eca4ec325afdc 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 6 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 LA-01-04_0_2 is in TripUpdates but not in VehiclePositions feed
  • trip_id LA-02-03_0_2 is in TripUpdates but not in VehiclePositions feed
  • trip_id LA-01-02_0_3 is in TripUpdates but not in VehiclePositions feed
  • trip_id LA-01-03_0_2 is in TripUpdates but not in VehiclePositions feed
  • trip_id LA-02-02_0_2 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 395 26 times (87 % 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 384 26 times (87 % 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 257 26 times (87 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 78 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 120 17 times (57 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 52 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. 6 5 times (17 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 26 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-13 at 11:05 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-04-13 at 11:05 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "vehicle:5f6b208cf07eca4f072db425", "vehicle": { "currentStatus": "STOPPED_AT", "currentStopSequence": 7, "position": { "latitude": 47.79497146606445, "longitude": 1.0629831552505493 }, "stopId": "VENDOME - ST MICHEL", "timestamp": "1776071116", "trip": { "routeId": "LIGNE A", "scheduleRelationship": "SCHEDULED", "tripId": "LA-01-07_0_2" }, "vehicle": { "id": "5f6b208cf07eca4f072db425", "label": "603", "licensePlate": "FS108QN" } } }, { "id": "trip:LA-01-07_0_2", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1776069531" }, "departure": { "time": "1776070557" }, "stopId": "VENDOME - ZI SUD", "stopSequence": 0 }, { "arrival": { "time": "1776070644" }, "departure": { "time": "1776070649" }, "stopId": "VENDOME - EIFFEL", "stopSequence": 1 }, { "arrival": { "time": "1776070698" }, "departure": { "time": "1776070707" }, "stopId": "VENDOME - ROUTE DE BLOIS", "stopSequence": 2 }, { "arrival": { "time": "1776070756" }, "departure": { "time": "1776070793" }, "stopId": "VENDOME - OFFENBACH", "stopSequence": 3 }, { "arrival": { "time": "1776070864" }, "departure": { "time": "1776070877" }, "stopId": "VENDOME - ST LUBIN", "stopSequence": 4 }, { "arrival": { "time": "1776070937" }, "departure": { "time": "1776071008" }, "stopId": "VENDOME - ST GEORGES", "stopSequence": 5 }, { "arrival": { "time": "1776071049" }, "departure": { "time": "1776071077" }, "stopId": "VENDOME - HOPITAL", "stopSequence": 6 }, { "arrival": { "time": "1776071104" }, "stopId": "VENDOME - ST MICHEL", "stopSequence": 7 }, { "arrival": { "time": "1776071180" }, "departure": { "time": "1776071180" }, "stopId": "VENDOME - KENNEDY", "stopSequence": 8 }, { "arrival": { "time": "1776071240" }, "departure": { "time": "1776071240" }, "stopId": "VENDOME - GERARD YVON", "stopSequence": 9 }, { "arrival": { "time": "1776071300" }, "departure": { "time": "1776071300" }, "stopId": "VENDOME - ST VENANT", "stopSequence": 10 }, { "arrival": { "time": "1776071480" }, "departure": { "time": "1776071480" }, "stopId": "VENDOME - GARE TER", "stopSequence": 11 }, { "arrival": { "time": "1776071600" }, "departure": { "time": "1776071600" }, "stopId": "VENDOME - CIMETIERE NORD", "stopSequence": 12 }, { "arrival": { "time": "1776071660" }, "departure": { "time": "1776071660" }, "stopId": "VENDOME - BRANLY", "stopSequence": 13 }, { "arrival": { "time": "1776071720" }, "departure": { "time": "1776071720" }, "stopId": "VENDOME - DANAN", "stopSequence": 14 }, { "arrival": { "time": "1776071780" }, "departure": { "time": "1776071780" }, "stopId": "VENDOME - LYCEE RONSARD", "stopSequence": 15 }, { "arrival": { "time": "1776071840" }, "departure": { "time": "1776071840" }, "stopId": "VENDOME - EUROPE", "stopSequence": 16 }, { "arrival": { "time": "1776071900" }, "departure": { "time": "1776071900" }, "stopId": "VENDOME - JEAN MOULIN", "stopSequence": 17 }, { "arrival": { "time": "1776071960" }, "departure": { "time": "1776071960" }, "stopId": "VENDOME - JOUHAUX", "stopSequence": 18 }, { "arrival": { "time": "1776072020" }, "departure": { "time": "1776072020" }, "stopId": "VENDOME - INDUSTRIE", "stopSequence": 19 }, { "arrival": { "time": "1776072080" }, "departure": { "time": "1776072080" }, "stopId": "VENDOME - ST MARC", "stopSequence": 20 }, { "arrival": { "time": "1776072200" }, "departure": { "time": "1776072200" }, "stopId": "VENDOME - 4 TILLEULS", "stopSequence": 21 } ], "timestamp": "1776071116", "trip": { "routeId": "LIGNE A", "scheduleRelationship": "SCHEDULED", "tripId": "LA-01-07_0_2" }, "vehicle": { "id": "5f6b208cf07eca4f072db425", "label": "603", "licensePlate": "FS108QN" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1776071121" } }