Resource details
GTFS-RT Position des véhicules en temps réel
This resource file is part of the dataset Réseau urbain Tango.
Download availability
Learn more
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
❌130 errors
Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.
Validation carried out using the current GTFS file and the GTFS-RT the 2026-05-02 at 09: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 65 errors
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 382 trip_id 2_69337547 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 381 trip_id 2_69337572 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 6380 trip_id 2_69096644 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 525 trip_id 2_69337326 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 8669 trip_id 2_68658223 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 65 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 382 stop_id 0:VOVR does not exist in GTFS data stops.txt
- vehicle_id 381 stop_id 0:OREA does not exist in GTFS data stops.txt
- vehicle_id 6380 stop_id 0:CPERDR does not exist in GTFS data stops.txt
- vehicle_id 525 stop_id 0:T does not exist in GTFS data stops.txt
- vehicle_id 8669 stop_id 0:MAGR does not exist in GTFS data stops.txt
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,028 | 28 times (97 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,035 | 28 times (97 % 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 2026-05-02 at 22:20 Europe/Paris.
vehicle_positions (2) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-05-02 at 22:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "720",
"vehicle": {
"position": {
"bearing": 85.0,
"latitude": 43.842872619628906,
"longitude": 4.381740570068359,
"speed": 2.0
},
"stopId": "0:DOMIT2R",
"timestamp": "1777753202",
"trip": {
"directionId": 1,
"routeId": "T2",
"scheduleRelationship": "SCHEDULED",
"tripId": "2_69466064"
},
"vehicle": {
"id": "720",
"label": "720"
}
}
},
{
"id": "704",
"vehicle": {
"position": {
"bearing": 108.0,
"latitude": 43.8403205871582,
"longitude": 4.362069129943848,
"speed": 1.0
},
"stopId": "0:PAUGT1",
"timestamp": "1777753202",
"trip": {
"directionId": 0,
"routeId": "T1",
"scheduleRelationship": "SCHEDULED",
"tripId": "2_69466567"
},
"vehicle": {
"id": "704",
"label": "704"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1777753212"
}
}