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
❌453 errors, 32 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-02 at 08:08 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 196 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 1048-36381 stop_sequence 3 arrival_time 08:10:00 (1767337800) is equal to previous stop arrival_time 08:10:00 (1767337800) - times must increase between two sequential stops
- trip_id 1048-36381 stop_sequence 3 arrival_time 08:10:00 (1767337800) is equal to previous stop departure_time 08:10:00 (1767337800) - times must increase between two sequential stops
- trip_id 1048-36381 stop_sequence 3 departure_time 08:10:00 (1767337800) is equal to previous stop departure_time 08:10:00 (1767337800) - times must increase between two sequential stops
- trip_id 1048-36381 stop_sequence 3 departure_time 08:10:00 (1767337800) is equal to previous stop arrival_time 08:10:00 (1767337800) - times must increase between two sequential stops
- trip_id 1048-36381 stop_sequence 4 arrival_time 08:10:00 (1767337800) is equal to previous stop arrival_time 08:10:00 (1767337800) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 56 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 1250-37049 stop_sequence 0 doesn't have arrival or departure
- trip_id 1055-37631 stop_sequence 0 doesn't have arrival or departure
- trip_id 8_3_4 stop_sequence 0 doesn't have arrival or departure
- trip_id 8_3_4 stop_sequence 1 doesn't have arrival or departure
- trip_id 8_3_4 stop_sequence 2 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 201 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 1048-36381 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 1048-36381 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 1048-36381 stop_sequence 24 has stop_id BJPMICH2 but GTFS stop_sequence 24 has stop_id BJLYCEE2 - stop_ids should be the same
- GTFS-rt trip_id 1048-36381 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 1048-36381 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 32 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 1045-38142 is in TripUpdates but not in VehiclePositions feed
- trip_id 1046-38113 is in TripUpdates but not in VehiclePositions feed
- trip_id 1253-38440 is in TripUpdates but not in VehiclePositions feed
- trip_id 1056-38115 is in TripUpdates but not in VehiclePositions feed
- trip_id 1048-36377 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. | 3,824 | 24 times (80 % 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,811 | 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 | 716 | 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 | 763 | 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. | 25 | 8 times (27 % 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) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-03 at 04:24 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-03 at 04:24 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767410652"
}
}