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

2025-12-17
83.8%
2025-12-18
85.4%
2025-12-19
94.2%
2025-12-20
99.5%
2025-12-21
88.1%
2025-12-22
80.3%
2025-12-23
89.3%
2025-12-24
94.2%
2025-12-25
96.4%
2025-12-26
87.2%
2025-12-27
98.9%
2025-12-28
91.2%
2025-12-29
90.8%
2025-12-30
88.7%
2025-12-31
95.4%
2026-01-01
96.9%
2026-01-02
95%
2026-01-03
98.4%
2026-01-04
96%
2026-01-05
85.4%
2026-01-06
79.3%
2026-01-07
82.4%
2026-01-08
89.3%
2026-01-09
46.9%
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
100%
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 error

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-15 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update doesn't have arrival or departure E043 1 error

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id 39-5254152250 stop_sequence 1 doesn't have arrival or departure
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
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 13 8 times (28 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 5 2 times (7 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 5 2 times (7 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 23 2 times (7 % 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 2 2 times (7 % 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. 1 1 times (3 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 21 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-16 at 03:18 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-16 at 03:18 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1768529892" } }