Resource details

File name: Breizhgo Car - Rennes – Loudéac/Pontivy
Format: gtfs-rt

Fichier GTFS-RT

This resource file is part of the dataset Réseau interurbain BreizhGo Car.

Download availability

2025-05-06
100%
2025-05-07
100%
2025-05-08
100%
2025-05-09
100%
2025-05-10
100%
2025-05-11
100%
2025-05-12
100%
2025-05-13
100%
2025-05-14
100%
2025-05-15
100%
2025-05-16
100%
2025-05-17
100%
2025-05-18
100%
2025-05-19
100%
2025-05-20
100%
2025-05-21
100%
2025-05-22
100%
2025-05-23
100%
2025-05-24
100%
2025-05-25
100%
2025-05-26
100%
2025-05-27
100%
2025-05-28
100%
2025-05-29
100%
2025-05-30
100%
2025-05-31
100%
2025-06-01
100%
2025-06-02
100%
2025-06-03
100%
2025-06-04
100%
2025-06-05
100%
Learn more
We test this resource download availability every hour by making an HTTP 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 2025-06-05 at 09:01 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 5-4598136876 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 711 min 54 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 5-4598136876 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5-4598136876 does not have a schedule_relationship
Validate this GTFS-RT now

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 32 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 64 30 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-05 at 21:17 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (0)

The timestamp field appears to be too old compared to the current time: the delay is 4 858 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-06-05 at 21:17 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:5-4598136876", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": -70, "time": "1749151070" }, "stopId": "LDA1A3", "stopSequence": 6 } ], "timestamp": "1749150024", "trip": { "directionId": 1, "routeId": "620", "tripId": "5-4598136876" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1749151062" } }