Resource details
Gtfs-RT flux tripupdates : Mises à jour de trajets (retards, annulations, itinéraires modifiés) au format GTFS-RT
This resource file is part of the dataset Réseau urbain SETRAM.
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
❌72 errors, 101 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-04 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 11 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 5062988-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 5063020-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 5062990-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 5063019-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 5062989-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 1100 does not exist in GTFS data stops.txt
stop_times_updates not strictly sorted E002 2 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 5063020-B-ETE-2026-HB-SE-ET-Semaine-26 stop_sequence for stop_ids [2191, 2440, 3229, 2183, 2788, 2599, 2524, 3011, 2116, 2205, 2378, 2521, 2475, 2027, 2798, 2832, 2279, 3097, 2809, 2458, 2835, 2015, 1100] is not strictly sorted by increasing stop_sequence
- trip_id 5063019-B-ETE-2026-HB-SE-ET-Semaine-26 stop_sequence for stop_ids [2191, 2440, 3229, 2183, 2788, 2599, 2524, 3011, 2116, 2205, 2378, 2521, 2475, 2027, 2798, 2832, 2279, 3097, 2809, 2458, 2835, 2015, 1100] is not strictly sorted by increasing stop_sequence
GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 3 errors
If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence
Sample errors
- trip_id 5062429-B-ETE-2026-HB-SE-ET-Semaine-26 visits stop_id [2191] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
- trip_id 5062428-B-ETE-2026-HB-SE-ET-Semaine-26 visits stop_id [2191] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
- trip_id 5062430-B-ETE-2026-HB-SE-ET-Semaine-26 visits stop_id [2191] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
Sequential stop_time_update times are not increasing E022 56 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 5062467-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 2252 arrival_time 09:19:21 (1785827961) is equal to previous stop arrival_time 09:19:21 (1785827961) - times must increase between two sequential stops
- trip_id 5062467-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 2252 arrival_time 09:19:21 (1785827961) is equal to previous stop departure_time 09:19:21 (1785827961) - times must increase between two sequential stops
- trip_id 5062467-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 2252 departure_time 09:19:21 (1785827961) is equal to previous stop departure_time 09:19:21 (1785827961) - times must increase between two sequential stops
- trip_id 5062467-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 2252 departure_time 09:19:21 (1785827961) is equal to previous stop arrival_time 09:19:21 (1785827961) - times must increase between two sequential stops
- trip_id 5062593-B-ETE-2026-HB-SE-ET-Semaine-26 stop_id 2295 arrival_time 09:16:30 (1785827790) is less than previous stop arrival_time 09:16:42 (1785827802) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 101 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5062469-B-ETE-2026-HB-SE-ET-Semaine-26 does not have a vehicle_id
- trip_id 5062496-B-ETE-2026-HB-SE-ET-Semaine-26 does not have a vehicle_id
- trip_id 5062497-B-ETE-2026-HB-SE-ET-Semaine-26 does not have a vehicle_id
- trip_id 5062569-B-ETE-2026-HB-SE-ET-Semaine-26 does not have a vehicle_id
- trip_id 5062533-B-ETE-2026-HB-SE-ET-Semaine-26 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 |
|---|---|---|---|
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 99 | 29 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 286 | 29 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. | 3,276 | 29 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2,681 | 29 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 56 | 27 times (93 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 42 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-05 at 03:09 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-08-05 at 03:09 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785892193"
}
}