Resource details
Les spécifications du format GTFS-RT sont disponibles ici : https://developers.google.com/transit/gtfs-realtime/
This resource file is part of the dataset Réseau urbain Ritmo.
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, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-10 at 09:02 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 4747448571396096:11 stop_sequence 23 arrival_time 09:10:31 (1789024231) is less than previous stop departure_time 09:15:00 (1789024500) - times must increase between two sequential stops
- trip_id 4747448571396096:11 stop_sequence 23 departure_time 09:13:20 (1789024400) is less than previous stop departure_time 09:15:00 (1789024500) - times must increase between two sequential stops
- trip_id 4747448571396096:11 stop_sequence 24 arrival_time 09:11:16 (1789024276) is less than previous stop departure_time 09:13:20 (1789024400) - times must increase between two sequential stops
- trip_id 4747448571396096:11 stop_sequence 25 arrival_time 09:12:02 (1789024322) is less than previous stop departure_time 09:14:13 (1789024453) - times must increase between two sequential stops
- trip_id 4747448571396096:11 stop_sequence 26 arrival_time 09:12:50 (1789024370) is less than previous stop departure_time 09:15:36 (1789024536) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4747448571396096:9 does not have a vehicle_id
ID in one feed missing from the other W003 1 error
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 4747448571396096:9 is in TripUpdates but not in VehiclePositions feed
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. | 1,845 | 24 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 26 | 16 times (55 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 26 | 16 times (55 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 7 | 7 times (24 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-11 at 00:48 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-09-11 at 00:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1789080530"
}
}