Resource details
Version Fil Bleu des mises à jour de trajets (retards, annulations, itinéraires modifiés) au format GTFS-RT (
filbleu-gtfsrt-tripupdates)
This resource file is part of the dataset Réseau urbain et périurbain Fil Bleu.
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
❌3 070 errors, 296 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-15 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 68 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence [40, 43, 35, 42, 36, 31, 39, 29, 33, 34, 37, 30, 38, 41, 32] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 stop_sequence [39, 18, 19, 34, 35, 30, 37, 26, 40, 29, 21, 24, 33, 32, 25, 20, 28, 36, 22, 23, 38, 31, 27] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739990 stop_sequence [67, 68, 66, 69, 70] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739981 stop_sequence [56, 67, 38, 64, 50, 48, 59, 39, 62, 65, 49, 51, 63, 40, 68, 66, 52, 55, 57, 44, 69, 45, 46, 61, 58, 70, 53, 43, 47, 60, 54, 41, 42] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739975 stop_sequence [73, 71, 72] is not strictly sorted by increasing stop_sequence
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 74 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 TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739990 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739981 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739975 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 2 928 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 TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 35 arrival_time 08:13:11 (1763190791) is less than previous stop arrival_time 08:25:24 (1763191524) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 35 arrival_time 08:13:11 (1763190791) is less than previous stop departure_time 08:25:24 (1763191524) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 35 departure_time 08:13:11 (1763190791) is less than previous stop departure_time 08:25:24 (1763191524) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 35 departure_time 08:13:11 (1763190791) is less than previous stop arrival_time 08:25:24 (1763191524) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 36 arrival_time 08:14:28 (1763190868) is less than previous stop arrival_time 08:23:24 (1763191404) - times must increase between two sequential stops
Warnings
timestamp not populated W001 74 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739990 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739981 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739975 does not have a timestamp
vehicle_id not populated W002 74 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739990 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739981 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739975 does not have a vehicle_id
schedule_relationship not populated W009 148 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 stop_sequence 40 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:740002 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 stop_sequence 39 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739998 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11726_PT2-PH1-SAMEDI:739990 stop_sequence 67 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 2 402 | 27 times (87 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 99 116 | 27 times (87 % of validations) |
| W001 | Timestamps should be populated for all elements | 2 591 | 27 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 591 | 27 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 5 182 | 27 times (87 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 492 | 14 times (45 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 867 | 13 times (42 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-16 at 04:08 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 2025-11-16 at 04:08 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1763262501"
}
}