Resource details

File name: Horaires temps réel des lignes du réseau REZO
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Rezo.

Download availability

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

⚠️16 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-07 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5940839076331520:9 does not have a vehicle_id
  • trip_id 6050120056438784:9 does not have a vehicle_id
  • trip_id 4821386586488832:8 does not have a vehicle_id
  • trip_id 5474533835276288:15 does not have a vehicle_id
  • trip_id 5474533835276288:16 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 921 min 26 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 5940839076331520:9 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5940839076331520:9 does not have a schedule_relationship
  • trip_id 6050120056438784:9 stop_sequence 38 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6050120056438784:9 does not have a schedule_relationship
  • trip_id 4821386586488832:8 stop_sequence 7 (and potentially more for this trip) does not have a schedule_relationship
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 135 26 times (87 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 270 26 times (87 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 8 8 times (27 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 4 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-07 at 09:24 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 2025-12-07 at 09:24 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1765095883" } }