Resource details
This resource file is part of the dataset Réseau urbain Forbus.
Download availability
Learn more
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
❌2 errors, 48 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-26 at 08:24 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 2 errors
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 a3f07f39-a643-4e69-9f94-6ad9c40535db stop_sequence 19 departure_time 08:22:19 (1792999339) is less than the same stop arrival_time 08:22:42 (1792999362) - departure time must be equal to or greater than arrival time
- trip_id b50594bd-970c-4b31-94ee-c03268ab7eef stop_sequence 21 departure_time 08:23:00 (1792999380) is less than the same stop arrival_time 08:23:01 (1792999381) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 16 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 does not have a vehicle_id
- trip_id a3f07f39-a643-4e69-9f94-6ad9c40535db does not have a vehicle_id
- trip_id b50594bd-970c-4b31-94ee-c03268ab7eef does not have a vehicle_id
- trip_id 4608f52e-2a0d-4d31-9f74-3cd02c79ed95 does not have a vehicle_id
- trip_id 3c230d4c-ca01-49a7-a6a8-e7265e820f08 does not have a vehicle_id
schedule_relationship not populated W009 32 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 stop_sequence 1 (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 a3f07f39-a643-4e69-9f94-6ad9c40535db stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
- trip_id a3f07f39-a643-4e69-9f94-6ad9c40535db does not have a schedule_relationship
- trip_id b50594bd-970c-4b31-94ee-c03268ab7eef stop_sequence 11 (and potentially more for this trip) does not have a schedule_relationship
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 | 451 | 25 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 902 | 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. | 16 | 10 times (33 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 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-10-27 at 01:42 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-10-27 at 01:42 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1793061775"
}
}