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-03-04
100%
2025-03-05
100%
2025-03-06
100%
2025-03-07
100%
2025-03-08
100%
2025-03-09
100%
2025-03-10
100%
2025-03-11
100%
2025-03-12
100%
2025-03-13
100%
2025-03-14
100%
2025-03-15
100%
2025-03-16
100%
2025-03-17
100%
2025-03-18
100%
2025-03-19
100%
2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
100%
2025-03-24
100%
2025-03-25
100%
2025-03-26
100%
2025-03-27
100%
2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
100%
2025-04-03
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-04-03 at 09:04 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-4599709719 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 27 min 16 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-4599709719 stop_sequence 5 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5-4599709719 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 40 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 80 30 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 29 29 times (97 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-03 at 15:12 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 18 472 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-04-03 at 15:12 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:5-4599185449", "trip_update": { "stop_time_update": [ { "arrival": { "delay": 100, "time": "1743685960" }, "stop_id": "RNS1A3", "stop_sequence": 8 } ], "timestamp": "1743685139", "trip": { "route_id": "620", "trip_id": "5-4599185449" } } } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1743685947" } }