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
❌77 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-09 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 77 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 5217762675785728:6 stop_sequence 35 arrival_time 08:10:48 (1770621048) is less than previous stop departure_time 08:15:00 (1770621300) - times must increase between two sequential stops
- trip_id 5217762675785728:6 stop_sequence 35 departure_time 08:13:29 (1770621209) is less than previous stop departure_time 08:15:00 (1770621300) - times must increase between two sequential stops
- trip_id 5217762675785728:6 stop_sequence 36 arrival_time 08:11:29 (1770621089) is less than previous stop departure_time 08:13:29 (1770621209) - times must increase between two sequential stops
- trip_id 5217762675785728:6 stop_sequence 37 arrival_time 08:12:16 (1770621136) is less than previous stop departure_time 08:14:19 (1770621259) - times must increase between two sequential stops
- trip_id 5217762675785728:6 stop_sequence 38 arrival_time 08:13:07 (1770621187) is less than previous stop departure_time 08:14:43 (1770621283) - 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 6009590169731072:2 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 6009590169731072:2 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 |
|---|---|---|---|
| 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. | 14 | 13 times (45 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 19 | 13 times (45 % 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 | 19 | 13 times (45 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 355 | 8 times (28 % 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-09 at 21:55 Europe/Paris.
vehicle_positions (1) trip_updates (1) service_alerts (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-09 at 21:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "zenbus:Vehicle:642300001:LOC",
"vehicle": {
"currentStatus": "STOPPED_AT",
"currentStopSequence": 21,
"position": {
"latitude": 48.81979751586914,
"longitude": 7.806632041931152
},
"stopId": "zenbus:StopPoint:SP:5471403928190976:LOC",
"timestamp": "1770666776",
"trip": {
"routeId": "zenbus:Line:756890009:LOC",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260209",
"startTime": "20:29:00",
"tripId": "6488877775716352:40"
},
"vehicle": {
"id": "zenbus:Vehicle:642300001:LOC"
}
}
},
{
"id": "20260209:5907884043927552:40",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1770670489"
},
"departure": {
"time": "1770670499"
},
"stopId": "zenbus:StopPoint:SP:659220084:LOC",
"stopSequence": 22
}
],
"timestamp": "1770670400",
"trip": {
"routeId": "zenbus:Line:756890009:LOC",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260209",
"startTime": "20:29:00",
"tripId": "6488877775716352:40"
},
"vehicle": {
"id": "zenbus:Vehicle:642300001:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770670501"
}
}