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

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

⚠️22 warnings

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

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 6479889348689920:0 does not have a vehicle_id
  • trip_id 4726417863475200:1 does not have a vehicle_id
  • trip_id 6571238762741760:2 does not have a vehicle_id
  • trip_id 5967298782298112:1 does not have a vehicle_id
  • trip_id 6039233646034944:0 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 1 min 8 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 14 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 6479889348689920:0 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6479889348689920:0 does not have a schedule_relationship
  • trip_id 4726417863475200:1 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 4726417863475200:1 does not have a schedule_relationship
  • trip_id 6571238762741760:2 stop_sequence 10 (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 138 26 times (87 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 276 26 times (87 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 15 15 times (50 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-11-05 at 04:28 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-11-05 at 04:28 Europe/Paris. You can look at the GTFS-RT documentation.

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