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
❌4,103 errors, 177 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-18 at 08:08 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 302 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 1_39334673 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_39334722 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_39491336 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_39333266 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_39103018 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 3,631 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 1_39334673 stop_id 0:NCBAT1 does not exist in GTFS data stops.txt
- trip_id 1_39334673 stop_id 0:FELA does not exist in GTFS data stops.txt
- trip_id 1_39334673 stop_id 0:MOUT2A does not exist in GTFS data stops.txt
- trip_id 1_39334673 stop_id 0:BRUA does not exist in GTFS data stops.txt
- trip_id 1_39334673 stop_id 0:ORVA does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 170 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 1_39334137 stop_sequence 1 departure_time 08:32:00 (1771399920) is less than previous stop departure_time 08:47:06 (1771400826) - times must increase between two sequential stops
- trip_id 1_39334137 stop_sequence 1 departure_time 08:32:00 (1771399920) is less than previous stop arrival_time 09:06:24 (1771401984) - times must increase between two sequential stops
- trip_id 1_39334137 stop_sequence 2 arrival_time 08:32:49 (1771399969) is less than previous stop arrival_time 09:06:24 (1771401984) - times must increase between two sequential stops
- trip_id 1_39334137 stop_sequence 2 departure_time 08:32:49 (1771399969) is less than previous stop arrival_time 09:06:24 (1771401984) - times must increase between two sequential stops
- trip_id 1_39334137 stop_sequence 18 arrival_time 08:49:03 (1771400943) is less than previous stop arrival_time 08:49:25 (1771400965) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 177 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1_39334722 does not have a vehicle_id
- trip_id 1_39333266 does not have a vehicle_id
- trip_id 1_39103018 does not have a vehicle_id
- trip_id 1_39336620 does not have a vehicle_id
- trip_id 1_39334604 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,012 | 24 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 73,346 | 24 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,557 | 24 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3,575 | 24 times (100 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 54 | 11 times (46 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-19 at 02:45 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-02-19 at 02:45 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771465515"
}
}