Resource details
Fichier GTFS-RT
This resource file is part of the dataset Réseau interurbain BreizhGo Car.
Related resources
Breizhgo 35
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
❌2 errors, 198 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-15 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 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 1982 stop_sequence 3 arrival_time 07:36:00 (1768458960) is less than previous stop arrival_time 08:14:36 (1768461276) - times must increase between two sequential stops
- trip_id 1982 stop_sequence 3 arrival_time 07:36:00 (1768458960) is less than previous stop departure_time 08:14:36 (1768461276) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 66 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 501-6-413 does not have a vehicle_id
- trip_id 504-7-413 does not have a vehicle_id
- trip_id 488 does not have a vehicle_id
- trip_id 490 does not have a vehicle_id
- trip_id 498 does not have a vehicle_id
schedule_relationship not populated W009 132 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 501-6-413 stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 501-6-413 does not have a schedule_relationship
- trip_id 504-7-413 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 504-7-413 does not have a schedule_relationship
- trip_id 488 stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,022 | 26 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2,044 | 26 times (100 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 25 | 25 times (96 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 10 | 5 times (19 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-15 at 21:47 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-15 at 21:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:143385{L7_13}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 1060,
"time": "1768510120"
},
"departure": {
"delay": 1060,
"time": "1768510120"
},
"stopId": "9306",
"stopSequence": 19
}
],
"timestamp": "1768509884",
"trip": {
"directionId": 1,
"routeId": "L7_13",
"tripId": "143385{L7_13}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1768510063"
}
}