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
❌294 errors, 40 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-16 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 8 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:11729_PT2-PH1-DIMANCHE:716398 stop_sequence [34, 33, 29, 30, 31, 35, 32, 36] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 stop_sequence [26, 29, 34, 30, 27, 36, 31, 33, 37, 32, 28, 35] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716364 stop_sequence [11, 26, 20, 29, 34, 15, 13, 30, 21, 19, 27, 24, 25, 36, 31, 33, 10, 16, 22, 18, 8, 17, 7, 37, 32, 23, 12, 6, 14, 9, 28, 35] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716332 stop_sequence [27, 12, 18, 9, 23, 34, 25, 8, 33, 17, 29, 19, 11, 14, 13, 7, 28, 22, 16, 20, 30, 21, 31, 35, 6, 15, 26, 32, 24, 36, 10] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:325082 stop_sequence [11, 10, 9, 24, 22, 14, 7, 19, 15, 18, 28, 27, 13, 17, 8, 16, 26, 23, 20, 21, 12, 25] 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 10 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:11729_PT2-PH1-DIMANCHE:716398 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716364 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716332 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:325084 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 276 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:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 33 arrival_time 08:06:48 (1763276808) is less than previous stop arrival_time 08:08:36 (1763276916) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 33 arrival_time 08:06:48 (1763276808) is less than previous stop departure_time 08:08:36 (1763276916) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 33 departure_time 08:06:48 (1763276808) is less than previous stop departure_time 08:08:36 (1763276916) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 33 departure_time 08:06:48 (1763276808) is less than previous stop arrival_time 08:08:36 (1763276916) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 29 arrival_time 08:00:28 (1763276428) is less than previous stop arrival_time 08:06:48 (1763276808) - times must increase between two sequential stops
Warnings
timestamp not populated W001 10 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716364 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716332 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:325084 does not have a timestamp
vehicle_id not populated W002 10 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716364 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716332 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:325084 does not have a vehicle_id
schedule_relationship not populated W009 20 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 stop_sequence 34 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716398 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 stop_sequence 26 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716386 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11729_PT2-PH1-DIMANCHE:716364 stop_sequence 11 (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 309 | 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. | 95 352 | 27 times (87 % of validations) |
| W001 | Timestamps should be populated for all elements | 2 488 | 27 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 488 | 27 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 976 | 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 502 | 15 times (48 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 780 | 12 times (39 % 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-17 at 01:59 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-17 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1763341192"
}
}