Resource details
Fichier GTFS-RT
This resource file is part of the dataset Réseau interurbain BreizhGo Car.
Related resources
Breizhgo Car 22
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
⚠️10 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-05 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 3 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-1649934337-36528-_M_JV__ does not have a vehicle_id
- trip_id 1-945356801 does not have a vehicle_id
- trip_id 1-1650196482-36528-_M_JV__ does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 28 min 39 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 6 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1-1649934337-36528-_M_JV__ stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-1649934337-36528-_M_JV__ does not have a schedule_relationship
- trip_id 1-945356801 stop_sequence 24 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-945356801 does not have a schedule_relationship
- trip_id 1-1650196482-36528-_M_JV__ stop_sequence 3 (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 | 80 | 30 times (100 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 30 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 160 | 30 times (100 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-05 at 19:39 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 2025-06-05 at 19:39 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:1-945684483",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 84,
"time": "1749145434"
},
"departure": {
"delay": 84,
"time": "1749145434"
},
"stopId": "PZC9A2",
"stopSequence": 28
},
{
"arrival": {
"delay": 84,
"time": "1749145494"
},
"departure": {
"delay": 84,
"time": "1749145494"
},
"stopId": "PZC6A2",
"stopSequence": 29
},
{
"arrival": {
"delay": 84,
"time": "1749145614"
},
"departure": {
"delay": 84,
"time": "1749145614"
},
"stopId": "PZC2A2",
"stopSequence": 30
}
],
"timestamp": "1749144784",
"trip": {
"routeId": "56",
"tripId": "1-945684483"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1749145182"
}
}