gtfs-rt Transport open dataset - Position des véhicules en temps réel GTFS-RT for Réseau urbain Bibus

Resource details

File name: Position des véhicules en temps réel GTFS-RT

Format: gtfs-rt

Position GPS temps réel des véhicules

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

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

❌23 errors, 274 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-28 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt route_id does not exist in GTFS data E004 23 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

vehicle_id 268435616 route_id S76 does not exist in the GTFS data routes.txt
vehicle_id 268436069 route_id S61 does not exist in the GTFS data routes.txt
vehicle_id 268435711 route_id S46 does not exist in the GTFS data routes.txt
vehicle_id 268435907 route_id S70 does not exist in the GTFS data routes.txt
vehicle_id 268435709 route_id S45 does not exist in the GTFS data routes.txt

Warnings

timestamp not populated W001 137 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 268436470 does not have a timestamp
vehicle_id 268435808 does not have a timestamp
vehicle_id 268436513 does not have a timestamp
vehicle_id 268435616 does not have a timestamp
vehicle_id 268436460 does not have a timestamp

schedule_relationship not populated W009 137 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 17685561 does not have a schedule_relationship
trip_id 17680626 does not have a schedule_relationship
trip_id 17684517 does not have a schedule_relationship
trip_id 17680047 does not have a schedule_relationship
trip_id 17684584 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
W001	Timestamps should be populated for all elements	2,754	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2,754	30 times (100 % of validations)
E029	The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.	40	16 times (53 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	225	11 times (37 % of validations)
E028	The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.	4	4 times (13 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	9	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-29 at 04:17 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-04-29 at 04:17 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1777429047"
  }
}