Resource details

File name: Ar bus - Landerneau-Daoulas
Format: gtfs-rt

Fichier GTFS-RT

This resource file is part of the dataset Réseau urbain Ar bus.

Download availability

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

⚠️25 warnings

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

Warnings

vehicle_id not populated W002 8 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4 scolaire 08:40 does not have a vehicle_id
  • trip_id 1 scolaire 08:48 does not have a vehicle_id
  • trip_id 5 scolaire 08:42 does not have a vehicle_id
  • trip_id 6 scolaire 09:11 does not have a vehicle_id
  • trip_id 2 scolaire 07:05 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 4 min 12 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 16 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 4 scolaire 08:40 stop_sequence 21 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 4 scolaire 08:40 does not have a schedule_relationship
  • trip_id 1 scolaire 08:48 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1 scolaire 08:48 does not have a schedule_relationship
  • trip_id 5 scolaire 08:42 stop_sequence 16 (and potentially more for this trip) 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 92 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 184 30 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-09-10 at 19:40 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 20,169 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-09-10 at 19:40 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:1 scolaire 19:20", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": 1, "time": "1789061652" }, "departure": { "delay": 1, "time": "1789062450" }, "stopId": "12", "stopSequence": 19 } ], "timestamp": "1789061988", "trip": { "routeId": "1", "tripId": "1 scolaire 19:20" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1789062017" } }