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, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-28 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 136 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 91 does not exist in the GTFS data routes.txt
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 136 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 178402 min 6 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 2 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 136 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 136 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 |
|---|---|---|---|
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 30 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 30 | 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 | 60 | 30 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 25 | 25 times (83 % 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 | 5 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-05-27 at 11:44 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-05-27 at 11:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:136",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 179,
"time": "1748339099"
},
"stopId": "11506",
"stopSequence": 18
}
],
"timestamp": "1748335740",
"trip": {
"routeId": "91",
"tripId": "136"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1748339091"
}
}