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

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

⚠️15 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-26 at 09:09 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 ATOUMOD004:ServiceJourney:DimanchexANNUELC395413:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC598592:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC595888:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC598573:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC598576:LOC does not have a vehicle_id

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC395413:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC395413:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC598592:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC598592:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:DimanchexANNUELC595888: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,272 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,542 30 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-26 at 12:16 Europe/Paris.

trip_updates (2) 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-04-26 at 12:16 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:ATOUMOD004:ServiceJourney:DimanchexANNUELC395411:LOC", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": 215, "time": "1777198475" }, "departure": { "delay": 215, "time": "1777198475" }, "stopId": "FR:27229:ZE:0xHAP02:ATOUMOD004", "stopSequence": 13 }, { "arrival": { "delay": 141, "time": "1777198581" }, "departure": { "delay": 141, "time": "1777198581" }, "stopId": "FR:27229:ZE:0xHOT01:ATOUMOD004", "stopSequence": 14 }, { "arrival": { "delay": 158, "time": "1777198658" }, "departure": { "delay": 158, "time": "1777198658" }, "stopId": "FR:27229:ZE:0xCHA01:ATOUMOD004", "stopSequence": 15 }, { "arrival": { "delay": 148, "time": "1777198768" }, "departure": { "delay": 148, "time": "1777198768" }, "stopId": "FR:27229:ZE:0xTAU02:ATOUMOD004", "stopSequence": 16 }, { "arrival": { "delay": 65, "time": "1777198865" }, "departure": { "delay": 65, "time": "1777198865" }, "stopId": "FR:27229:ZE:0xMFO02:ATOUMOD004", "stopSequence": 17 }, { "arrival": { "delay": 77, "time": "1777198937" }, "departure": { "delay": 77, "time": "1777198937" }, "stopId": "FR:27229:ZE:0xCCA02:ATOUMOD004", "stopSequence": 18 }, { "arrival": { "time": "1777199100" }, "stopId": "FR:27229:ZE:0xCAM01:ATOUMOD004", "stopSequence": 19 } ], "timestamp": "1777198516", "trip": { "directionId": 1, "routeId": "ATOUMOD004:Line:T1:LOC", "tripId": "ATOUMOD004:ServiceJourney:DimanchexANNUELC395411:LOC" } } }, { "id": "SM:ATOUMOD004:ServiceJourney:DimanchexANNUELC598584:LOC", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "time": "1777198475" }, "departure": { "time": "1777198500" }, "stopId": "FR:27229:ZE:0xKEN04:ATOUMOD004", "stopSequence": 2 } ], "timestamp": "1777198516", "trip": { "directionId": 1, "routeId": "ATOUMOD004:Line:T2:LOC", "tripId": "ATOUMOD004:ServiceJourney:DimanchexANNUELC598584:LOC" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1777198615" } }