Resource details

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

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

Download availability

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

⚠️19 warnings

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

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 86a0c974-6535-425d-839e-05e00440dd47 does not have a vehicle_id
  • trip_id 327dcf4a-c61a-4dfd-984c-d40e24cf225b does not have a vehicle_id
  • trip_id f036cf66-b4b2-4ec1-a85f-4e7105f236ce does not have a vehicle_id
  • trip_id 6ccbb8b2-40cb-42ae-98c9-b5d2a80bbd73 does not have a vehicle_id
  • trip_id A-LU3-4-0908 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 1 min 8 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 86a0c974-6535-425d-839e-05e00440dd47 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 86a0c974-6535-425d-839e-05e00440dd47 does not have a schedule_relationship
  • trip_id 327dcf4a-c61a-4dfd-984c-d40e24cf225b stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 327dcf4a-c61a-4dfd-984c-d40e24cf225b does not have a schedule_relationship
  • trip_id f036cf66-b4b2-4ec1-a85f-4e7105f236ce 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 67 18 times (86 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 134 18 times (86 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 6 6 times (29 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-10-17 at 20:41 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 2025-10-17 at 20:41 Europe/Paris. You can look at the GTFS-RT documentation.

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