Resource details

File name: Horaires temps-réel au format GTFS-RT
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain RLV Mobilités.

Download availability

2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
100%
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

77 errors, 37 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-18 at 09:00 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 37 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id 36313_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 36322_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 36316_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 36319_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 36302_0 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 37 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 2 does not exist in the GTFS data routes.txt
  • route_id 2 does not exist in the GTFS data routes.txt
  • route_id 2 does not exist in the GTFS data routes.txt
  • route_id 2 does not exist in the GTFS data routes.txt
  • route_id 2 does not exist in the GTFS data routes.txt

Sequential stop_time_updates have the same stop_id E037 3 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 36369_0 has repeating stop_id RIOPSNC1 at stop_sequence 14 - sequential stop_ids should be different
  • trip_id 36375_0 has repeating stop_id RIOPSNC1 at stop_sequence 25 - sequential stop_ids should be different
  • trip_id 36361_0 has repeating stop_id RIOPSNC1 at stop_sequence 25 - sequential stop_ids should be different

Warnings

vehicle_id not populated W002 37 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 36313_0 does not have a vehicle_id
  • trip_id 36322_0 does not have a vehicle_id
  • trip_id 36316_0 does not have a vehicle_id
  • trip_id 36319_0 does not have a vehicle_id
  • trip_id 36302_0 does not have a vehicle_id
Validate this GTFS-RT now

GTFS-RT feed content

Entities

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

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

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

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