Resource details
This resource file is part of the dataset Réseau urbain Rezo.
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
⚠️1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-21 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 968 min 40 sec old which is greater than the recommended age of 65 seconds
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 | 148 | 27 times (90 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 296 | 27 times (90 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 12 | 12 times (40 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 4 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-20 at 16: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 2025-12-20 at 16:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1766242971"
}
}