Resource details
Données temps-réel du réseau RUBAN suivant la structure GTFS-RT au format Protocol Buffers.
This resource file is part of the dataset Réseau urbain Ruban.
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
❌278 errors, 29 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-06 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 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 692eb419854524dd276e1744 trip_id TEST-19 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 692eb419854524dd276e1744 route_id TEST1 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 199 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 932-38857 stop_sequence 9 arrival_time 08:06:20 (1767683180) is equal to previous stop arrival_time 08:06:20 (1767683180) - times must increase between two sequential stops
- trip_id 932-38857 stop_sequence 9 arrival_time 08:06:20 (1767683180) is equal to previous stop departure_time 08:06:20 (1767683180) - times must increase between two sequential stops
- trip_id 932-38857 stop_sequence 9 departure_time 08:06:20 (1767683180) is equal to previous stop departure_time 08:06:20 (1767683180) - times must increase between two sequential stops
- trip_id 932-38857 stop_sequence 9 departure_time 08:06:20 (1767683180) is equal to previous stop arrival_time 08:06:20 (1767683180) - times must increase between two sequential stops
- trip_id 932-38857 stop_sequence 19 arrival_time 08:20:20 (1767684020) is equal to previous stop arrival_time 08:20:20 (1767684020) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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 1137-38315 stop_sequence 0 departure_time 04:56:49 (1767671809) is less than the same stop arrival_time 05:10:38 (1767672638) - departure time must be equal to or greater than arrival time
- trip_id 924-38029 stop_sequence 0 departure_time 07:59:22 (1767682762) is less than the same stop arrival_time 08:01:05 (1767682865) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 73 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 935-38027 stop_sequence 0 doesn't have arrival or departure
- trip_id 935-38027 stop_sequence 1 doesn't have arrival or departure
- trip_id 935-38027 stop_sequence 2 doesn't have arrival or departure
- trip_id 935-38027 stop_sequence 3 doesn't have arrival or departure
- trip_id 935-38027 stop_sequence 4 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 2 errors
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 3-1 and vehicle_id 6929c96df112f41d2c6811a3 pairing in VehiclePositions does not match trip_id 42317{MOZAS_3}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 6929c96df112f41d2c6811a3 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 42133{1141_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 68dba0cd7ea32b9cf17ad3f0 pairing in VehiclePositions does not match trip_id 42013{1021_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 68dba0cd7ea32b9cf17ad3f0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 28 errors
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 1137-38326 is in TripUpdates but not in VehiclePositions feed
- trip_id 1139-38708 is in TripUpdates but not in VehiclePositions feed
- trip_id 935-38027 is in TripUpdates but not in VehiclePositions feed
- trip_id 924-38056 is in TripUpdates but not in VehiclePositions feed
- trip_id 1136-38765 is in TripUpdates but not in VehiclePositions feed
schedule_relationship not populated W009 1 error
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TEST-19 does not have a schedule_relationship
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. | 3,686 | 24 times (80 % 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 | 686 | 24 times (80 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 756 | 23 times (77 % of validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 4,473 | 23 times (77 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 22 | 12 times (40 % 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. | 24 | 9 times (30 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 | 4 times (13 % 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. | 3 | 3 times (10 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 | 1 times (3 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-07 at 02:26 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-01-07 at 02:26 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767749194"
}
}