Resource details
File name:
Données en temps réel au format GTFS-RT
Format: gtfs-rt
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
2026-01-10
98.7%
2026-01-11
87.7%
2026-01-12
84.2%
2026-01-13
81.8%
2026-01-14
95.6%
2026-01-15
98.1%
2026-01-16
97.6%
2026-01-17
98.2%
2026-01-18
97.5%
2026-01-19
98.2%
2026-01-20
97.5%
2026-01-21
97.9%
2026-01-22
98.6%
2026-01-23
99.7%
2026-01-24
99.6%
2026-01-25
98.4%
2026-01-26
98.3%
2026-01-27
99.6%
2026-01-28
98.5%
2026-01-29
99.7%
2026-01-30
99.6%
2026-01-31
100%
2026-02-01
98.4%
2026-02-02
99.6%
2026-02-03
98.2%
2026-02-04
98.3%
2026-02-05
99.6%
2026-02-06
99.5%
2026-02-07
99.5%
2026-02-08
99.5%
2026-02-09
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-08 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 39 | 13 times (45 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 21 | 8 times (28 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 21 | 8 times (28 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 54 | 8 times (28 % 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 | 17 | 6 times (21 % 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. | 5 | 5 times (17 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 4 | 4 times (14 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 14 | 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. | 2 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-09 at 07:19 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-02-09 at 07:19 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770617950"
}
}