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

⚠️16 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-07 at 08:09 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 3-305037585 does not have a vehicle_id
trip_id 3-839057414 does not have a vehicle_id
trip_id 3-282329121 does not have a vehicle_id
trip_id 3-326107150 does not have a vehicle_id
trip_id 3-275709983 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 924 min 7 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 3-305037585 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-305037585 does not have a schedule_relationship
trip_id 3-839057414 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-839057414 does not have a schedule_relationship
trip_id 3-282329121 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	219	26 times (87 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	438	26 times (87 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	12	12 times (40 % 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.	5	5 times (17 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	3	1 times (3 % 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-12-07 at 22:20 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-12-07 at 22:20 Europe/Paris. You can look at the GTFS-RT documentation.


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