Resource details

File name: Horaires temps réel des lignes du réseau Fluo Grand Est dans le Haut-Rhin (68)
Format: gtfs-rt

Flux temps réel (horaires) au format GTFS-RT du réseau Fluo Grand Est dans le Haut-Rhin (68)

This resource file is part of the dataset Réseau interurbain Fluo Grand-Est - Haut-Rhin (68).

Download availability

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

⚠️66 warnings

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

Warnings

vehicle_id not populated W002 22 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1035883-1052271 does not have a vehicle_id
  • trip_id 1035585-1051436 does not have a vehicle_id
  • trip_id 1041090-1060172 does not have a vehicle_id
  • trip_id 1030669-1043391 does not have a vehicle_id
  • trip_id 1038170-1055662 does not have a vehicle_id

schedule_relationship not populated W009 44 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1035883-1052271 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1035883-1052271 does not have a schedule_relationship
  • trip_id 1035585-1051436 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1035585-1051436 does not have a schedule_relationship
  • trip_id 1041090-1060172 stop_sequence 4 (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 1,029 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,058 30 times (100 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 35 20 times (67 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-08-04 at 22:42 Europe/Paris.

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

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-08-04 at 22:42 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1785876140" } }