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

❌37 errors, 18 warnings

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 3 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id 3-305037551 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3-839057410 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3-305103086 does not exist in the GTFS data and does not have schedule_relationship of ADDED

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 3-275709981 stop_sequence 2 departure_time 07:58:50 (1763794730) is less than the same stop arrival_time 07:58:56 (1763794736) - departure time must be equal to or greater than arrival time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 33 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 3-282329439 stop_sequence 1 has stop_id 106 but GTFS stop_sequence 1 has stop_id 107 - stop_ids should be the same
GTFS-rt trip_id 3-282329439 stop_sequence 9 has stop_id 136 but GTFS stop_sequence 9 has stop_id 137 - stop_ids should be the same
GTFS-rt trip_id 3-282329439 stop_sequence 10 has stop_id 124 but GTFS stop_sequence 10 has stop_id 125 - stop_ids should be the same
GTFS-rt trip_id 3-282329439 stop_sequence 11 has stop_id 120 but GTFS stop_sequence 11 has stop_id 121 - stop_ids should be the same
GTFS-rt trip_id 3-282329439 stop_sequence 12 has stop_id 141 but GTFS stop_sequence 12 has stop_id 142 - stop_ids should be the same

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 3-305037551 does not have a vehicle_id
trip_id 3-839057410 does not have a vehicle_id
trip_id 3-282329439 does not have a vehicle_id
trip_id 3-299040772 does not have a vehicle_id
trip_id 3-305103086 does not have a vehicle_id

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 3-305037551 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-305037551 does not have a schedule_relationship
trip_id 3-839057410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-839057410 does not have a schedule_relationship
trip_id 3-282329439 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	206	25 times (83 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	412	25 times (83 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	8	8 times (27 % 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.	9	7 times (23 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	11	5 times (17 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	8	4 times (13 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	33	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-22 at 22:07 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-11-22 at 22:07 Europe/Paris. You can look at the GTFS-RT documentation.


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