Resource details

File name: Horaires temps réel des lignes du réseau Distribus
Format: gtfs-rt

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

Download availability

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

1 error, 119 warnings

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

Errors

stop_time_update departure time is before arrival time E025 1 error

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.

Sample errors
  • trip_id 405T-0823 stop_sequence 22 departure_time 09:05:12 (1781679912) is less than the same stop arrival_time 09:07:12 (1781680032) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 40 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1101-0905 does not have a vehicle_id
  • trip_id 1101-0935 does not have a vehicle_id
  • trip_id 1101-0920 does not have a vehicle_id
  • trip_id 1101-0850 does not have a vehicle_id
  • trip_id 103-0905 does not have a vehicle_id

schedule_relationship not populated W009 79 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1101-0905 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1101-0905 does not have a schedule_relationship
  • trip_id 1101-0935 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1101-0935 does not have a schedule_relationship
  • trip_id 1101-0920 stop_sequence 1 (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,075 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,132 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. 4 4 times (13 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-06-18 at 01:15 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-06-18 at 01:15 Europe/Paris. You can look at the GTFS-RT documentation.

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