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
❌18 errors, 357 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-17 at 08:03 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 e868187e-20d0-43af-95c5-cfbebbfc486b stop_sequence 10 departure_time 09:25:42 (1771316742) is less than the same stop arrival_time 09:45:42 (1771317942) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_id E037 17 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 1c9da668-854b-4f28-b49b-53ac1542ee7e has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 3573e205-1504-414d-9441-4b1b45e074eb has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 42fb6533-419e-4fb5-a231-152667d73b51 has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
Warnings
vehicle_id not populated W002 119 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4af82985-8292-4b3d-b14e-2082299e4813 does not have a vehicle_id
- trip_id 59f61597-2dec-4d7a-9cb1-26b8b5e01c4a does not have a vehicle_id
- trip_id 5c649cc4-736c-4453-8216-6c6ff3e7bdb0 does not have a vehicle_id
- trip_id 7fcca3b4-8ab1-452b-a2e0-12a710f817fa does not have a vehicle_id
- trip_id 82d40512-6c59-4605-b2a2-de797eb07e4e does not have a vehicle_id
schedule_relationship not populated W009 238 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 4af82985-8292-4b3d-b14e-2082299e4813 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 4af82985-8292-4b3d-b14e-2082299e4813 does not have a schedule_relationship
- trip_id 59f61597-2dec-4d7a-9cb1-26b8b5e01c4a stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 59f61597-2dec-4d7a-9cb1-26b8b5e01c4a does not have a schedule_relationship
- trip_id 5c649cc4-736c-4453-8216-6c6ff3e7bdb0 stop_sequence 1 (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 | 2,921 | 24 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 5,842 | 24 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 | 9 times (31 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 9 | 9 times (31 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 68 | 4 times (14 % 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-18 at 03:17 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-02-18 at 03:17 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1771381054"
}
}