gtfs-rt Transport open dataset - Horaires temps-réel au format GTFS-RT for Réseau urbain Zest

Resource details

File name: Horaires temps-réel au format GTFS-RT

Format: gtfs-rt

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

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

❌120 errors, 77 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-22 at 09:02 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 77 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 474 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 337 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 284 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 509 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 59 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 9 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id 11B does not exist in the GTFS data routes.txt
route_id 11A does not exist in the GTFS data routes.txt
route_id 11A does not exist in the GTFS data routes.txt
route_id NE does not exist in the GTFS data routes.txt
route_id NE does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id 59 stop_id MCAJEX1 does not exist in GTFS data stops.txt
trip_id 495 stop_id RCMMASS2 does not exist in GTFS data stops.txt
trip_id 495 stop_id RCMTORR4 does not exist in GTFS data stops.txt
trip_id 356 stop_id MCAJEX1 does not exist in GTFS data stops.txt
trip_id 17 stop_id FONRDB2 does not exist in GTFS data stops.txt

Sequential stop_time_updates have the same stop_id E037 11 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors

trip_id 284 has repeating stop_id MENMGRO1 at stop_sequence 15 - sequential stop_ids should be different
trip_id 59 has repeating stop_id MCAPSDE1 at stop_sequence 25 - sequential stop_ids should be different
trip_id 395 has repeating stop_id MENMGRO1 at stop_sequence 15 - sequential stop_ids should be different
trip_id 17 has repeating stop_id BREBRGS2 at stop_sequence 10 - sequential stop_ids should be different
trip_id 604 has repeating stop_id MENMGRO1 at stop_sequence 15 - sequential stop_ids should be different

Warnings

vehicle_id not populated W002 77 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 474 does not have a vehicle_id
trip_id 337 does not have a vehicle_id
trip_id 284 does not have a vehicle_id
trip_id 509 does not have a vehicle_id
trip_id 59 does not have a vehicle_id

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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 083	30 times (94 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	1 660	23 times (72 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	209	23 times (72 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	467	23 times (72 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	216	23 times (72 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	3	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-23 at 03:37 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-09-23 at 03:37 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1758591431"
  }
}