Resource details
This resource file is part of the dataset Réseau urbain Buss.
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
❌7 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-24 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 7 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 5939385078906880:7 stop_sequence 28 arrival_time 09:18:27 (1777015107) is equal to previous stop departure_time 09:18:27 (1777015107) - times must increase between two sequential stops
- trip_id 5939385078906880:8 stop_sequence 28 arrival_time 09:32:54 (1777015974) is less than previous stop departure_time 09:33:10 (1777015990) - times must increase between two sequential stops
- trip_id 5939385078906880:8 stop_sequence 29 arrival_time 09:33:29 (1777016009) is less than previous stop departure_time 09:33:32 (1777016012) - times must increase between two sequential stops
- trip_id 5838467574530048:4 stop_sequence 9 arrival_time 09:07:21 (1777014441) is less than previous stop departure_time 09:07:26 (1777014446) - times must increase between two sequential stops
- trip_id 5440079360163840:3 stop_sequence 26 arrival_time 09:20:25 (1777015225) is less than previous stop departure_time 09:20:28 (1777015228) - times must increase between two sequential stops
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. | 553 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 9 | 9 times (30 % 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 | 9 | 9 times (30 % 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. | 10 | 8 times (27 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-25 at 04:51 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-04-25 at 04:51 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1777085502"
}
}