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
⚠️4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-15 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 450 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 627 min 11 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 450 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 450 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,182 | 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 | 2,364 | 30 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 16 | 7 times (23 % of validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 1 | 1 times (3 % 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 | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-15 at 15:04 Europe/Paris.
trip_updates (3) 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-03-15 at 15:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:256",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 254,
"time": "1773584354"
},
"stopId": "23834",
"stopSequence": 8
}
],
"timestamp": "1773583429",
"trip": {
"directionId": 1,
"routeId": "416",
"tripId": "256"
}
}
},
{
"id": "SM:143304{L16_16}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": -63,
"time": "1773583557"
},
"departure": {
"delay": -63,
"time": "1773583557"
},
"stopId": "9302",
"stopSequence": 11
},
{
"arrival": {
"delay": -63,
"time": "1773583617"
},
"departure": {
"delay": -63,
"time": "1773583617"
},
"stopId": "9304",
"stopSequence": 12
},
{
"arrival": {
"delay": -63,
"time": "1773583677"
},
"departure": {
"delay": -63,
"time": "1773583677"
},
"stopId": "28700",
"stopSequence": 13
},
{
"arrival": {
"delay": -63,
"time": "1773583737"
},
"departure": {
"delay": -63,
"time": "1773583737"
},
"stopId": "28702",
"stopSequence": 14
},
{
"arrival": {
"delay": -63,
"time": "1773583797"
},
"departure": {
"delay": -63,
"time": "1773583797"
},
"stopId": "28706",
"stopSequence": 15
},
{
"arrival": {
"delay": -63,
"time": "1773583917"
},
"departure": {
"delay": -63,
"time": "1773583917"
},
"stopId": "28712",
"stopSequence": 16
},
{
"arrival": {
"delay": -63,
"time": "1773583977"
},
"departure": {
"delay": -63,
"time": "1773583977"
},
"stopId": "28716",
"stopSequence": 17
},
{
"arrival": {
"delay": -63,
"time": "1773584037"
},
"departure": {
"delay": -63,
"time": "1773584037"
},
"stopId": "28714",
"stopSequence": 18
},
{
"arrival": {
"delay": -63,
"time": "1773584157"
},
"departure": {
"delay": -63,
"time": "1773584157"
},
"stopId": "25600",
"stopSequence": 19
},
{
"arrival": {
"delay": -63,
"time": "1773584217"
},
"departure": {
"delay": -63,
"time": "1773584217"
},
"stopId": "25608",
"stopSequence": 20
},
{
"arrival": {
"delay": -63,
"time": "1773584637"
},
"stopId": "25606",
"stopSequence": 21
}
],
"timestamp": "1773583436",
"trip": {
"directionId": 1,
"routeId": "L16_16",
"tripId": "143304{L16_16}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF"
}
}
},
{
"id": "SM:143286{L16_16}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 131,
"time": "1773583320"
},
"departure": {
"delay": 131,
"time": "1773583451"
},
"stopId": "9301",
"stopSequence": 16
},
{
"arrival": {
"delay": 116,
"time": "1773583496"
},
"departure": {
"delay": 116,
"time": "1773583496"
},
"stopId": "24103",
"stopSequence": 17
},
{
"arrival": {
"delay": 116,
"time": "1773584036"
},
"departure": {
"delay": 116,
"time": "1773584036"
},
"stopId": "28805",
"stopSequence": 18
},
{
"arrival": {
"delay": 116,
"time": "1773584276"
},
"departure": {
"delay": 116,
"time": "1773584276"
},
"stopId": "28809",
"stopSequence": 19
},
{
"arrival": {
"delay": 116,
"time": "1773584516"
},
"stopId": "28810",
"stopSequence": 20
}
],
"timestamp": "1773583435",
"trip": {
"routeId": "L16_16",
"tripId": "143286{L16_16}-BREIZHGO JANVIER 2026 PS_01_LMWJVSDF"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1773583479"
}
}