gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau FORBUS for Réseau urbain Forbus

Resource details

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

Format: gtfs-rt

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

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

⚠️363 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-19 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 121 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 14f97c40-e1ba-4d3d-a423-68a4b9cf489f does not have a vehicle_id
trip_id 1c6b993b-001d-4594-89d5-6b092373f939 does not have a vehicle_id
trip_id 1d141152-b3e9-48c4-a505-44513daa0093 does not have a vehicle_id
trip_id 4659d11c-3690-4e71-817c-79971f9c4eeb does not have a vehicle_id
trip_id 4a5c000d-c762-4558-b4d8-8bc9534e06c8 does not have a vehicle_id

schedule_relationship not populated W009 242 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 14f97c40-e1ba-4d3d-a423-68a4b9cf489f stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 14f97c40-e1ba-4d3d-a423-68a4b9cf489f does not have a schedule_relationship
trip_id 1c6b993b-001d-4594-89d5-6b092373f939 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1c6b993b-001d-4594-89d5-6b092373f939 does not have a schedule_relationship
trip_id 1d141152-b3e9-48c4-a505-44513daa0093 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	2,895	24 times (83 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	5,790	24 times (83 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	9	9 times (31 % 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.	15	8 times (28 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	51	3 times (10 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-19 at 21:44 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 2026-02-19 at 21:44 Europe/Paris. You can look at the GTFS-RT documentation.


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