Resource details

File name: Données en temps réel des horaires aux arrêts du réseau Transurbain
Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts.

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

Download availability

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

⚠️105 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-07 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 39 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596169:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596524:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596556:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC598257:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC598275:LOC does not have a vehicle_id

schedule_relationship not populated W009 66 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596169:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596169:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596524:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596524:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:MercredixSCOC596556:LOC 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 1,096 17 times (89 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,158 17 times (89 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 1 1 times (5 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.