Resource details
Flux temps réel (GTFS-RT) du réseau Tout’enbus (via Hubup)
- Permalien *
This resource file is part of the dataset Réseau urbain Tout'enbus.
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
❌4 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-29 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 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 40705 stop_sequence 15 arrival_time 09:24:32 (1745911472) is equal to previous stop arrival_time 09:24:32 (1745911472) - times must increase between two sequential stops
- trip_id 40705 stop_sequence 15 arrival_time 09:24:32 (1745911472) is equal to previous stop departure_time 09:24:32 (1745911472) - times must increase between two sequential stops
- trip_id 40705 stop_sequence 15 departure_time 09:24:32 (1745911472) is equal to previous stop departure_time 09:24:32 (1745911472) - times must increase between two sequential stops
- trip_id 40705 stop_sequence 15 departure_time 09:24:32 (1745911472) is equal to previous stop arrival_time 09:24:32 (1745911472) - 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. | 112 | 19 times (66 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 16 | 16 times (55 % 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 | 16 | 16 times (55 % of validations) |
| W001 | Timestamps should be populated for all elements | 1 | 1 times (3 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 | 1 times (3 % 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 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-29 at 21:58 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-04-29 at 21:58 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1745956681"
}
}