Resource details

File name: GTFS-RT Position des véhicules en temps réel
Format: gtfs-rt

GTFS-RT Position des véhicules en temps réel

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

Download availability

2025-10-03
100%
2025-10-04
100%
2025-10-05
100%
2025-10-06
100%
2025-10-07
100%
2025-10-08
100%
2025-10-09
100%
2025-10-10
99.3%
2025-10-11
100%
2025-10-12
98.4%
2025-10-13
100%
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
98%
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%
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

2 errors

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 401 trip_id 2_78982497 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt stop_id does not exist in GTFS data E011 1 error

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • vehicle_id 401 stop_id 0:PAUGTN does not exist in GTFS data stops.txt
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 2 036 30 times (100 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2 048 30 times (100 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-02 at 18:19 Europe/Paris.

vehicle_positions (1) 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-11-02 at 18:19 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "702", "vehicle": { "position": { "bearing": 90.0, "latitude": 43.832828521728516, "longitude": 4.392327308654785, "speed": 1.0 }, "stopId": "0:NLIBT2", "timestamp": "1762091049", "trip": { "directionId": 0, "routeId": "T1", "scheduleRelationship": "SCHEDULED", "tripId": "2_78996345" }, "vehicle": { "id": "702", "label": "702" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1762103944" } }