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

❌1 error, 51 warnings

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

Errors

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 565d485f-683a-4150-bbe7-4e34ec0784b7 stop_sequence 4 departure_time 09:07:48 (1785827268) is less than the same stop arrival_time 09:08:03 (1785827283) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 17 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id f2e35e3b-b4bf-4600-af14-8113e65ca3f4 does not have a vehicle_id
trip_id a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 does not have a vehicle_id
trip_id e2f3f973-0928-42bd-84e6-bb97721459eb does not have a vehicle_id
trip_id 527a87f6-bc0e-40f5-9665-e142086d8740 does not have a vehicle_id
trip_id b6102267-9fcf-49ea-a94c-cd37c92b7fc4 does not have a vehicle_id

schedule_relationship not populated W009 34 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id f2e35e3b-b4bf-4600-af14-8113e65ca3f4 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
trip_id f2e35e3b-b4bf-4600-af14-8113e65ca3f4 does not have a schedule_relationship
trip_id a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
trip_id a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 does not have a schedule_relationship
trip_id e2f3f973-0928-42bd-84e6-bb97721459eb stop_sequence 7 (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	411	25 times (83 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	822	25 times (83 % 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.	13	10 times (33 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	2	2 times (7 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-08-05 at 02:09 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 349 seconds. Try to update your feed at most every 30 seconds.

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-08-05 at 02:09 Europe/Paris. You can look at the GTFS-RT documentation.


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