Resource details
GTFS-RT Mises à jour des trajets 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
❌311 errors, 19 warnings
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-04-05 at 09:04 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 30 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 7_79345723 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7_79345722 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7_79345699 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7_79345706 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7_79183766 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 277 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 7_79345723 stop_id 0:CALVT does not exist in GTFS data stops.txt
- trip_id 7_79345722 stop_id 0:CALVT does not exist in GTFS data stops.txt
- trip_id 7_79345722 stop_id 0:LUNA does not exist in GTFS data stops.txt
- trip_id 7_79345722 stop_id 0:TROA does not exist in GTFS data stops.txt
- trip_id 7_79345722 stop_id 0:CHALEA does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 4 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 7_79492231 stop_sequence 4 arrival_time 09:31:55 (1775374315) is less than previous stop arrival_time 09:32:00 (1775374320) - times must increase between two sequential stops
- trip_id 7_79492231 stop_sequence 4 arrival_time 09:31:55 (1775374315) is less than previous stop departure_time 09:32:00 (1775374320) - times must increase between two sequential stops
- trip_id 7_79492231 stop_sequence 4 departure_time 09:31:55 (1775374315) is less than previous stop departure_time 09:32:00 (1775374320) - times must increase between two sequential stops
- trip_id 7_79492231 stop_sequence 4 departure_time 09:31:55 (1775374315) is less than previous stop arrival_time 09:32:00 (1775374320) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 19 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 7_79345723 does not have a vehicle_id
- trip_id 7_79345699 does not have a vehicle_id
- trip_id 7_79183766 does not have a vehicle_id
- trip_id 7_79345692 does not have a vehicle_id
- trip_id 7_78658265 does not have a vehicle_id
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 | 6,686 | 30 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 75,077 | 30 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2,230 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 4,089 | 30 times (100 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 9 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-05 at 21:36 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-04-05 at 21:36 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775417786"
}
}