Resource details

File name: Breizhgo Car 22
Format: gtfs-rt

Fichier GTFS-RT

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

Breizhgo Car 22

Associated GTFS file

Download availability

2026-04-04
100%
2026-04-05
100%
2026-04-06
100%
2026-04-07
100%
2026-04-08
100%
2026-04-09
100%
2026-04-10
100%
2026-04-11
100%
2026-04-12
100%
2026-04-13
100%
2026-04-14
100%
2026-04-15
100%
2026-04-16
100%
2026-04-17
100%
2026-04-18
100%
2026-04-19
100%
2026-04-20
100%
2026-04-21
100%
2026-04-22
100%
2026-04-23
100%
2026-04-24
100%
2026-04-25
100%
2026-04-26
100%
2026-04-27
100%
2026-04-28
100%
2026-04-29
100%
2026-04-30
100%
2026-05-01
100%
2026-05-02
100%
2026-05-03
100%
2026-05-04
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

⚠️7 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-05-04 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 2 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-1653473281 does not have a vehicle_id
  • trip_id 1-947978241 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 97 min 43 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 4 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1-1653473281 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-1653473281 does not have a schedule_relationship
  • trip_id 1-947978241 stop_sequence 5 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-947978241 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 2026-05-04 at 13:08 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 6,592 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 2026-05-04 at 13:08 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:1-6778257411-05031-LM_JV__", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": -111, "time": "1777892893" }, "departure": { "delay": -111, "time": "1777892893" }, "stopId": "RNN1B2", "stopSequence": 4 } ], "timestamp": "1777892891", "trip": { "directionId": 1, "routeId": "404", "tripId": "1-6778257411-05031-LM_JV__" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1777892928" } }