gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau LE BUS for Réseau urbain Le Bus

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

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

⚠️16 warnings

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

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id A-LU4-110-1730 does not have a vehicle_id
trip_id 2d228ba4-c881-42ca-b17f-71770d35922e does not have a vehicle_id
trip_id R-LU3-112-1739 does not have a vehicle_id
trip_id 93708a01-552a-4483-8001-e55f125a2cf9 does not have a vehicle_id
trip_id e0b28dd9-20d1-41cf-8601-58ed4b4b2076 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 921 min 37 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id A-LU4-110-1730 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
trip_id A-LU4-110-1730 does not have a schedule_relationship
trip_id 2d228ba4-c881-42ca-b17f-71770d35922e stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
trip_id 2d228ba4-c881-42ca-b17f-71770d35922e does not have a schedule_relationship
trip_id R-LU3-112-1739 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	133	20 times (67 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	266	20 times (67 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	19	19 times (63 % 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.	6	4 times (13 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	2	2 times (7 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	2	2 times (7 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	2	2 times (7 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-12 at 23:03 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 2 731 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 2025-06-12 at 23:03 Europe/Paris. You can look at the GTFS-RT documentation.


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