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
❌84 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-16 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 84 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 5433988945543168:8 stop_sequence 23 arrival_time 08:27:18 (1771226838) is less than previous stop departure_time 08:30:00 (1771227000) - times must increase between two sequential stops
- trip_id 5433988945543168:8 stop_sequence 23 departure_time 08:29:14 (1771226954) is less than previous stop departure_time 08:30:00 (1771227000) - times must increase between two sequential stops
- trip_id 5433988945543168:8 stop_sequence 24 arrival_time 08:28:12 (1771226892) is less than previous stop departure_time 08:29:14 (1771226954) - times must increase between two sequential stops
- trip_id 5433988945543168:8 stop_sequence 25 arrival_time 08:29:06 (1771226946) is less than previous stop departure_time 08:30:11 (1771227011) - times must increase between two sequential stops
- trip_id 5433988945543168:8 stop_sequence 26 arrival_time 08:30:03 (1771227003) is less than previous stop departure_time 08:31:08 (1771227068) - times must increase between two sequential stops
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. | 824 | 13 times (45 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 17 | 12 times (41 % 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 | 17 | 12 times (41 % 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. | 11 | 10 times (34 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-17 at 04:07 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-02-17 at 04:07 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771297645"
}
}