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 interurbain TIC.

Download availability

2026-02-19
100%
2026-02-20
100%
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
100%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
100%
2026-03-21
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

⚠️27 warnings

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

Warnings

vehicle_id not populated W002 9 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 7714 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
  • trip_id 7609 does not have a vehicle_id

schedule_relationship not populated W009 18 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 7714 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7714 does not have a schedule_relationship
  • trip_id 7715 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7715 does not have a schedule_relationship
  • trip_id 7659 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 868 24 times (75 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1,723 24 times (75 % 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. 2 2 times (6 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-21 at 10:29 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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-21 at 10:29 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:7874", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1774087800" }, "stopId": "CGARE3", "stopSequence": 1 } ], "timestamp": "1774084216", "trip": { "directionId": 1, "routeId": "103", "tripId": "7874" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1774085361" } }