Resource details
GTFS-RT réseau CapBus (temps réel)
This resource file is part of the dataset Réseau urbain Cap’Bus.
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
❌16 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-13 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 16 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 6064739487580160:3 stop_sequence 26 arrival_time 10:31:20 (1773394280) is less than previous stop departure_time 10:31:35 (1773394295) - times must increase between two sequential stops
- trip_id 5227099246821376:1 stop_sequence 2 arrival_time 08:22:14 (1773386534) is less than previous stop departure_time 08:22:17 (1773386537) - times must increase between two sequential stops
- trip_id 5227099246821376:1 stop_sequence 3 arrival_time 08:23:13 (1773386593) is less than previous stop departure_time 08:23:42 (1773386622) - times must increase between two sequential stops
- trip_id 5227099246821376:1 stop_sequence 4 arrival_time 08:24:40 (1773386680) is less than previous stop departure_time 08:24:41 (1773386681) - times must increase between two sequential stops
- trip_id 5227099246821376:1 stop_sequence 5 arrival_time 08:25:13 (1773386713) is less than previous stop departure_time 08:26:25 (1773386785) - 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. | 388 | 26 times (87 % 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. | 13 | 11 times (37 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 | 5 times (17 % 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 | 6 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-14 at 06:33 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-03-14 at 06:33 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773466426"
}
}