Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
TripUpdate
VehiclePosition
Alert
This resource file is part of the dataset Réseau urbain Réso.
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
❌9 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-06 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 60f6da02b397926c0b5b95b8 trip_id 3-5117116482 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3-5117116482 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 2 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 60f6da02b397926c0b5b95b8 route_id 305 does not exist in the GTFS data routes.txt
- route_id 305 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 5 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 60f6da02b397926c0b5b95b8 stop_id 5795 does not exist in GTFS data stops.txt
- trip_id 3-5117116482 stop_id 1423 does not exist in GTFS data stops.txt
- trip_id 3-5117116482 stop_id 5795 does not exist in GTFS data stops.txt
- trip_id 3-5117116482 stop_id 6768 does not exist in GTFS data stops.txt
- trip_id 3-5117116482 stop_id 6771 does not exist in GTFS data stops.txt
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 |
|---|---|---|---|
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 59 | 12 times (40 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 38 | 12 times (40 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 37 | 10 times (33 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 37 | 10 times (33 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 131 | 10 times (33 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 6 | 5 times (17 % of validations) |
| E052 | Each vehicle should have a unique ID | 4 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-07 at 00:07 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-07 at 00:07 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1786054051"
}
}