Resource details

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

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

Download availability

2026-02-18
100%
2026-02-19
100%
2026-02-20
99.3%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
2026-03-16
95.8%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
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 2026-03-20 at 08:07 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 6023880549335040:2 does not have a vehicle_id
  • trip_id 6023880549335040:4 does not have a vehicle_id
  • trip_id 5105702836109312:4 does not have a vehicle_id
  • trip_id 6005861488001024:0 does not have a vehicle_id
  • trip_id 5959169128529920:3 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 57 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 6023880549335040:2 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6023880549335040:2 does not have a schedule_relationship
  • trip_id 6023880549335040:4 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6023880549335040:4 does not have a schedule_relationship
  • trip_id 5105702836109312:4 stop_sequence 5 (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 123 25 times (86 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 246 25 times (86 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 6 6 times (21 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-20 at 22:15 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-03-20 at 22:15 Europe/Paris. You can look at the GTFS-RT documentation.

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