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
❌406 errors, 30 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-26 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 145 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 1056-38146 stop_sequence 28 arrival_time 08:39:00 (1766734740) is equal to previous stop arrival_time 08:39:00 (1766734740) - times must increase between two sequential stops
- trip_id 1056-38146 stop_sequence 28 arrival_time 08:39:00 (1766734740) is equal to previous stop departure_time 08:39:00 (1766734740) - times must increase between two sequential stops
- trip_id 1056-38146 stop_sequence 28 departure_time 08:39:00 (1766734740) is equal to previous stop departure_time 08:39:00 (1766734740) - times must increase between two sequential stops
- trip_id 1056-38146 stop_sequence 28 departure_time 08:39:00 (1766734740) is equal to previous stop arrival_time 08:39:00 (1766734740) - times must increase between two sequential stops
- trip_id 1045-36435 stop_sequence 15 arrival_time 08:06:46 (1766732806) is less than previous stop departure_time 08:07:00 (1766732820) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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 1048-36428 stop_sequence 29 departure_time 08:03:03 (1766732583) is less than the same stop arrival_time 08:03:37 (1766732617) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 15 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 1049-38924 stop_sequence 0 doesn't have arrival or departure
- trip_id 1049-38924 stop_sequence 1 doesn't have arrival or departure
- trip_id 8_2 stop_sequence 13 doesn't have arrival or departure
- trip_id 1261-37072 stop_sequence 0 doesn't have arrival or departure
- trip_id 1060-38930 stop_sequence 0 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 244 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 1056-38146 stop_sequence 15 has stop_id BJALPES2 but GTFS stop_sequence 15 has stop_id BJGARE1 - stop_ids should be the same
- GTFS-rt trip_id 1056-38146 stop_sequence 16 has stop_id BJCLESP2 but GTFS stop_sequence 16 has stop_id BJALPES2 - stop_ids should be the same
- GTFS-rt trip_id 1056-38146 stop_sequence 17 has stop_id BJPAPIN2 but GTFS stop_sequence 17 has stop_id BJCLESP2 - stop_ids should be the same
- GTFS-rt trip_id 1056-38146 stop_sequence 18 has stop_id BJMALAS2 but GTFS stop_sequence 18 has stop_id BJPAPIN2 - stop_ids should be the same
- GTFS-rt trip_id 1056-38146 stop_sequence 19 has stop_id BJMALBR2 but GTFS stop_sequence 19 has stop_id BJMALAS2 - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 1049-38926 and vehicle_id 636a2e22c520d5a13c77e10f pairing in VehiclePositions does not match trip_id 1060-38930 and vehicle_id 636a2e22c520d5a13c77e10f 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 30 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 1056-38115 is in TripUpdates but not in VehiclePositions feed
- trip_id 1046-38113 is in TripUpdates but not in VehiclePositions feed
- trip_id 1048-36377 is in TripUpdates but not in VehiclePositions feed
- trip_id 4_3_0 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,169 | 25 times (83 % 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 | 762 | 25 times (83 % 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,011 | 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 | 5,065 | 24 times (80 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 23 | 13 times (43 % 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. | 28 | 10 times (33 % 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. | 2 | 2 times (7 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-27 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 2025-12-27 at 02:26 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766798797"
}
}