Resource details

File name: Horaire temps réel (GTFS-RT PROTOBUF) - réseau TIC (interurbain)
Format: gtfs-rt

Données horaires temps réel, au format GTFS-RT PROTOBUF, du réseau TIC (interurbain)

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

Download availability

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

⚠️30 warnings

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

Warnings

vehicle_id not populated W002 10 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 7714 does not have a vehicle_id
  • trip_id 6881 does not have a vehicle_id
  • trip_id 7715 does not have a vehicle_id
  • trip_id 7659 does not have a vehicle_id
  • trip_id 6710 does not have a vehicle_id

schedule_relationship not populated W009 20 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 7714 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7714 does not have a schedule_relationship
  • trip_id 6881 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6881 does not have a schedule_relationship
  • trip_id 7715 stop_sequence 1 (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 395 19 times (61 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 781 19 times (61 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 178 5 times (16 % 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)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-08 at 22:17 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-11-08 at 22:17 Europe/Paris. You can look at the GTFS-RT documentation.

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