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

2025-06-01
100%
2025-06-02
100%
2025-06-03
100%
2025-06-04
100%
2025-06-05
100%
2025-06-06
100%
2025-06-07
100%
2025-06-08
100%
2025-06-09
100%
2025-06-10
100%
2025-06-11
100%
2025-06-12
100%
2025-06-13
100%
2025-06-14
100%
2025-06-15
100%
2025-06-16
100%
2025-06-17
100%
2025-06-18
100%
2025-06-19
100%
2025-06-20
100%
2025-06-21
100%
2025-06-22
100%
2025-06-23
100%
2025-06-24
100%
2025-06-25
100%
2025-06-26
100%
2025-06-27
100%
2025-06-28
100%
2025-06-29
100%
2025-06-30
100%
2025-07-01
100%
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 warning

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

Warnings

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 376 min 56 sec old which is greater than the recommended age of 65 seconds
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
W008 The data in a GTFS-realtime feed should always be less than one minute old 22 22 times (76 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 263 13 times (45 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 263 13 times (45 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 310 13 times (45 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 263 13 times (45 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 204 13 times (45 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2 408 13 times (45 % 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. 7 5 times (17 % of validations)

GTFS-RT feed content

Entities

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

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