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
❌525 errors, 41 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-19 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 16 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 933-37607 stop_id BJMEDIA3 does not exist in GTFS data stops.txt
- trip_id 927-38855 stop_id BJMEDIA3 does not exist in GTFS data stops.txt
- trip_id 932-38857 stop_id BJMEDIA3 does not exist in GTFS data stops.txt
- trip_id 925-36336 stop_id BJMEDIA3 does not exist in GTFS data stops.txt
- trip_id 927-38844 stop_id BJMEDIA3 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 136 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 1145-38362 stop_sequence 5 arrival_time 09:16:40 (1758266200) is equal to previous stop arrival_time 09:16:40 (1758266200) - times must increase between two sequential stops
- trip_id 1145-38362 stop_sequence 5 arrival_time 09:16:40 (1758266200) is equal to previous stop departure_time 09:16:40 (1758266200) - times must increase between two sequential stops
- trip_id 1145-38362 stop_sequence 5 departure_time 09:16:40 (1758266200) is equal to previous stop departure_time 09:16:40 (1758266200) - times must increase between two sequential stops
- trip_id 1145-38362 stop_sequence 5 departure_time 09:16:40 (1758266200) is equal to previous stop arrival_time 09:16:40 (1758266200) - times must increase between two sequential stops
- trip_id 1145-38362 stop_sequence 13 arrival_time 09:28:40 (1758266920) is equal to previous stop arrival_time 09:28:40 (1758266920) - 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 668f9b480ca0aead54276bac trip_id 927-38844 at (45.582893,5.3186183) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
stop_time_update doesn't have arrival or departure E043 16 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 8_0_21 stop_sequence 5 doesn't have arrival or departure
- trip_id 8_0_21 stop_sequence 6 doesn't have arrival or departure
- trip_id 8_0_21 stop_sequence 7 doesn't have arrival or departure
- trip_id 1139-38708 stop_sequence 23 doesn't have arrival or departure
- trip_id 1147-38748 stop_sequence 0 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 356 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 926-36247 stop_sequence 22 has stop_id BJPOSTE2 but GTFS stop_sequence 22 has stop_id BJGARE1 - stop_ids should be the same
- GTFS-rt trip_id 926-36247 stop_sequence 23 has stop_id BJLYCEE2 but GTFS stop_sequence 23 has stop_id BJPOSTE2 - stop_ids should be the same
- GTFS-rt trip_id 926-36247 stop_sequence 24 has stop_id BJMEDIA2 but GTFS stop_sequence 24 has stop_id BJLYCEE2 - stop_ids should be the same
- GTFS-rt trip_id 926-36247 stop_sequence 25 has stop_id BJFOLAT2 but GTFS stop_sequence 25 has stop_id BJPMICH2 - stop_ids should be the same
- GTFS-rt trip_id 926-36247 stop_sequence 26 has stop_id BJEPARG1 but GTFS stop_sequence 26 has stop_id BJFOLAT2 - stop_ids should be the same
Warnings
ID in one feed missing from the other W003 41 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 1145-38386 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 925-36245 is in TripUpdates but not in VehiclePositions feed
- trip_id 926-36247 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. | 4 297 | 27 times (87 % 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 | 1 161 | 27 times (87 % 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 | 9 453 | 27 times (87 % 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 | 1 278 | 27 times (87 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 270 | 23 times (74 % 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. | 46 | 13 times (42 % 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 (23 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 9 | 2 times (6 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-20 at 01:25 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-09-20 at 01:25 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758324326"
}
}