Resource details

File name: Position des véhicules du réseau FORBUS
Format: gtfs-rt

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

Download availability

2026-01-02
83.1%
2026-01-03
80.7%
2026-01-04
47.2%
2026-01-05
78%
2026-01-06
74%
2026-01-07
70%
2026-01-08
82.8%
2026-01-09
97.1%
2026-01-10
81.1%
2026-01-11
64.7%
2026-01-12
82.4%
2026-01-13
81.6%
2026-01-14
79.3%
2026-01-15
81.5%
2026-01-16
80.5%
2026-01-17
82.9%
2026-01-18
56.8%
2026-01-19
82.1%
2026-01-20
81.3%
2026-01-21
68.7%
2026-01-22
69.3%
2026-01-23
82.2%
2026-01-24
80.9%
2026-01-25
51.7%
2026-01-26
81.2%
2026-01-27
73.2%
2026-01-28
82.1%
2026-01-29
91.6%
2026-01-30
77%
2026-01-31
81.2%
2026-02-01
65.6%
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 2026-02-01 at 08:07 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 2 min 35 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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 324 22 times (88 % 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. 34 19 times (76 % of validations)
W001 Timestamps should be populated for all elements 33 18 times (72 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 15 15 times (60 % 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. 10 8 times (32 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-01 at 21:10 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 789 seconds. Try to update your feed at most every 30 seconds.

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-02-01 at 21:10 Europe/Paris. You can look at the GTFS-RT documentation.

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