Resource details

File name: Données en temps réel de la position des véhicules du réseau Transurbain
Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules.

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

Download availability

2025-08-21
86.5%
2025-08-22
96.2%
2025-08-23
96.4%
2025-08-24
87.4%
2025-08-25
99.6%
2025-08-26
91.4%
2025-08-27
91.5%
2025-08-28
100%
2025-08-29
96.1%
2025-08-30
99.7%
2025-08-31
89.1%
2025-09-01
91.5%
2025-09-02
99.7%
2025-09-03
100%
2025-09-04
99.7%
2025-09-05
99.7%
2025-09-06
96.2%
2025-09-07
80.3%
2025-09-08
91.6%
2025-09-09
100%
2025-09-10
96.3%
2025-09-11
89.4%
2025-09-12
99.1%
2025-09-13
98.6%
2025-09-14
87.7%
2025-09-15
97.7%
2025-09-16
91.9%
2025-09-17
99.1%
2025-09-18
95.1%
2025-09-19
100%
2025-09-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

⚠️20 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-20 at 09:05 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

schedule_relationship not populated W009 20 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD004:ServiceJourney:SamedixSCOC585002:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SamedixSCOC595641:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SamedixSCOC584999:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SamedixSCOC586183:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SamedixSCOC584978:LOC 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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 500 23 times (82 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 26 14 times (50 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 8 8 times (29 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 10 6 times (21 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-21 at 01:18 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-09-21 at 01:18 Europe/Paris. You can look at the GTFS-RT documentation.

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