gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau TUB for Réseau urbain TUB - CA de Bar-le-Duc

Resource details

File name: Horaires temps réel des lignes du réseau TUB

Format: gtfs-rt

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

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

⚠️21 warnings

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

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 3-292487175 does not have a vehicle_id
trip_id 3-304906481 does not have a vehicle_id
trip_id 3-838926339 does not have a vehicle_id
trip_id 3-283508740 does not have a vehicle_id
trip_id 3-304972016 does not have a vehicle_id

schedule_relationship not populated W009 14 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 3-292487175 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-292487175 does not have a schedule_relationship
trip_id 3-304906481 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-304906481 does not have a schedule_relationship
trip_id 3-838926339 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	203	24 times (83 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	406	24 times (83 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	20	20 times (69 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	20	20 times (69 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	20	20 times (69 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	20	20 times (69 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	6	6 times (21 % 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.	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

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


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