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
❌3 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-09 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 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 6565111708778496:6 stop_sequence 38 arrival_time 08:14:17 (1765264457) is less than previous stop departure_time 08:14:50 (1765264490) - times must increase between two sequential stops
- trip_id 6565111708778496:6 stop_sequence 39 arrival_time 08:15:08 (1765264508) is less than previous stop departure_time 08:15:13 (1765264513) - times must increase between two sequential stops
Vehicle position far from trip shape E029 1 error
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.
Sample errors
- vehicle.id zenbus:Vehicle:830250002:LOC trip_id 4707845984485376:8 at (48.728928,7.71564) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
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 |
|---|---|---|---|
| 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. | 29 | 19 times (66 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 22 | 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 | 22 | 16 times (55 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 19 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-10 at 00:38 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 2025-12-10 at 00:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765323485"
}
}