gtfs-rt Transport open dataset - https://data.filbleu.fr/ws-tr/gtfs-rt/opendata/trip-updates for Réseau urbain et périurbain Fil Bleu

Resource details

File name: https://data.filbleu.fr/ws-tr/gtfs-rt/opendata/trip-updates

Format: gtfs-rt

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

We test this resource download availability every hour by making an HTTP 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

❌5 854 errors, 576 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-20 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 130 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:11724_PT2-PH1-JEUDI:740366 stop_sequence [25, 28, 16] is not strictly sorted by increasing stop_sequence
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740360 stop_sequence [25, 28, 29, 27, 24, 26] is not strictly sorted by increasing stop_sequence
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 stop_sequence [18, 22, 24, 26, 21] is not strictly sorted by increasing stop_sequence
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740318 stop_sequence [22, 24, 26, 23] is not strictly sorted by increasing stop_sequence
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 stop_sequence [25, 28, 16] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 5 608 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:11724_PT2-PH1-JEUDI:740366 stop_sequence 16 arrival_time 08:08:39 (1763622519) is less than previous stop arrival_time 08:28:12 (1763623692) - times must increase between two sequential stops
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 16 arrival_time 08:08:39 (1763622519) is less than previous stop departure_time 08:28:12 (1763623692) - times must increase between two sequential stops
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 16 departure_time 08:08:39 (1763622519) is less than previous stop departure_time 08:28:12 (1763623692) - times must increase between two sequential stops
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 16 departure_time 08:08:39 (1763622519) is less than previous stop arrival_time 08:28:12 (1763623692) - times must increase between two sequential stops
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 12 arrival_time 07:59:30 (1763621970) is less than previous stop arrival_time 08:08:39 (1763622519) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 116 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors

GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 contains stop_sequence 16 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740318 contains stop_sequence 23 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 contains stop_sequence 16 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:739740 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 144 errors

Timestamps should be populated for all elements

Sample errors

trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a timestamp
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740360 does not have a timestamp
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 does not have a timestamp
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740318 does not have a timestamp
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 does not have a timestamp

vehicle_id not populated W002 144 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a vehicle_id
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740360 does not have a vehicle_id
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 does not have a vehicle_id
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740318 does not have a vehicle_id
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 does not have a vehicle_id

schedule_relationship not populated W009 288 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 25 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a schedule_relationship
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740360 stop_sequence 25 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740360 does not have a schedule_relationship
trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship

Validate this GTFS-RT now

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 570	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.	106 760	27 times (87 % of validations)
W001	Timestamps should be populated for all elements	2 772	27 times (87 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 772	27 times (87 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	5 544	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 795	17 times (55 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	779	10 times (32 % 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-21 at 04:24 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-11-21 at 04:24 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1763695494"
  }
}