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
❌168 errors, 176 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-19 at 08: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 11 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 1-712441882-22.1-LM_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712376336-14-L______ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712638494-14-L______ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712310789-14-L______ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-709361666-14-L______ does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 156 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-691666964 stop_sequence 22 arrival_time 08:13:31 (1768806811) is equal to previous stop arrival_time 08:13:31 (1768806811) - times must increase between two sequential stops
- trip_id 1-691666964 stop_sequence 22 arrival_time 08:13:31 (1768806811) is equal to previous stop departure_time 08:13:31 (1768806811) - times must increase between two sequential stops
- trip_id 1-691666964 stop_sequence 22 departure_time 08:13:31 (1768806811) is equal to previous stop departure_time 08:13:31 (1768806811) - times must increase between two sequential stops
- trip_id 1-691666964 stop_sequence 22 departure_time 08:13:31 (1768806811) is equal to previous stop arrival_time 08:13:31 (1768806811) - times must increase between two sequential stops
- trip_id 1-691470340 stop_sequence 12 arrival_time 08:10:01 (1768806601) is equal to previous stop arrival_time 08:10:01 (1768806601) - 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 1-724762669 stop_sequence 9 departure_time 08:01:00 (1768806060) is less than the same stop arrival_time 08:01:32 (1768806092) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 93 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-691666964 does not have a timestamp
- trip_id 1-744882182 does not have a timestamp
- trip_id 1-712638495 does not have a timestamp
- trip_id 1-691470340 does not have a timestamp
- trip_id 1-712441882-22.1-LM_____ does not have a timestamp
vehicle_id not populated W002 83 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-712376336-14-L______ does not have a vehicle_id
- trip_id 1-712638494-14-L______ does not have a vehicle_id
- trip_id 1-712310789-14-L______ does not have a vehicle_id
- trip_id 1-709361666-14-L______ does not have a vehicle_id
- trip_id 1-691470359 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,720 | 21 times (70 % of validations) |
| W001 | Timestamps should be populated for all elements | 1,564 | 21 times (70 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,397 | 21 times (70 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 100 | 10 times (33 % 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. | 5 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-19 at 21:03 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-19 at 21:03 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768852998"
}
}