Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
This resource file is part of the dataset Réseau urbain SURF.
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
❌108 errors, 131 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-29 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 108 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 1-724762628 stop_sequence 17 arrival_time 09:13:48 (1777446828) is equal to previous stop arrival_time 09:13:48 (1777446828) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 arrival_time 09:13:48 (1777446828) is equal to previous stop departure_time 09:13:48 (1777446828) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 departure_time 09:13:48 (1777446828) is equal to previous stop departure_time 09:13:48 (1777446828) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 departure_time 09:13:48 (1777446828) is equal to previous stop arrival_time 09:13:48 (1777446828) - times must increase between two sequential stops
- trip_id 1-729153542 stop_sequence 3 arrival_time 12:04:00 (1777457040) is equal to previous stop arrival_time 12:04:00 (1777457040) - times must increase between two sequential stops
Warnings
timestamp not populated W001 70 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-691666966 does not have a timestamp
- trip_id 1-691470341 does not have a timestamp
- trip_id 1-712376334 does not have a timestamp
- trip_id 1-712704027 does not have a timestamp
- trip_id 1-744882177 does not have a timestamp
vehicle_id not populated W002 61 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-712376337 does not have a vehicle_id
- trip_id 1-712638493 does not have a vehicle_id
- trip_id 1-712441881 does not have a vehicle_id
- trip_id 1-712704026 does not have a vehicle_id
- trip_id 1-712441860 does not have a vehicle_id
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2,356 | 25 times (83 % of validations) |
| W001 | Timestamps should be populated for all elements | 1,604 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,412 | 25 times (83 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 24 | 8 times (27 % 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-04-29 at 22:45 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-04-29 at 22:45 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1777495543"
}
}