Resource details

File name: Position des véhicules sur les lignes du réseau Fluo Grand Est dans le Haut-Rhin (68)
Format: gtfs-rt

Flux temps réel (position des véhicules) 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-10-23
89.7%
2026-10-24
71.5%
2026-10-25
62.3%
2026-10-26
74.3%
2026-10-27
76.2%
2026-10-28
82.1%
2026-10-29
90.5%
2026-10-30
74.9%
2026-10-31
82.2%
2026-11-01
60.7%
2026-11-02
76.6%
2026-11-03
84.9%
2026-11-04
84.2%
2026-11-05
100%
2026-11-06
75.9%
2026-11-07
69.9%
2026-11-08
58.9%
2026-11-09
84.7%
2026-11-10
85.1%
2026-11-11
65.7%
2026-11-12
84%
2026-11-13
74.3%
2026-11-14
70.6%
2026-11-15
57.2%
2026-11-16
79.9%
2026-11-17
87.4%
2026-11-18
79%
2026-11-19
78.7%
2026-11-20
76.2%
2026-11-21
70%
2026-11-22
61.7%
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

⚠️2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-22 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

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 1 min 29 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 1 error

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1043635-1064383 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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,308 29 times (97 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 218 22 times (73 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 19 19 times (63 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 4 3 times (10 % of validations)
W001 Timestamps should be populated for all elements 4 3 times (10 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.