Resource details
Heures de passage en temps réel aux points d’arrêts des lignes du réseaux de transport ZOU! Express, au format GTFS-RT (Real Time)
This resource file is part of the dataset Réseau interurbain Express ZOU !.
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
❌2 errors, 47 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-29 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 1 error
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 6902|20190124|6 stop_sequence 1 arrival_time 06:04:56 (1769663096) is equal to previous stop departure_time 06:04:56 (1769663096) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 49A501|20240701|3 stop_sequence 6 departure_time 08:01:58 (1769670118) is less than the same stop arrival_time 08:02:04 (1769670124) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 47 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 6711|20190130|2 does not have a timestamp
- trip_id 6026|20240901|1 does not have a timestamp
- trip_id 6902|20190124|6 does not have a timestamp
- trip_id 6928|20230901|18 does not have a timestamp
- trip_id 76R1|20251214|2 does not have a timestamp
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 993 | 25 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 190 | 20 times (80 % 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. | 22 | 14 times (56 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-30 at 03:02 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-30 at 03:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769738539"
}
}