Resource details
File name:
filbleu_gtfsrt_tripupdates
Format: gtfs-rt
GTFS-RT tripupdates Fil Bleu
This resource file is part of the dataset Réseau urbain et périurbain Fil Bleu.
Download availability
2025-11-28
91.8%
2025-11-29
100%
2025-11-30
96.1%
2025-12-01
92%
2025-12-02
91.8%
2025-12-03
91.8%
2025-12-04
100%
2025-12-05
95.9%
2025-12-06
96.2%
2025-12-07
96%
2025-12-08
91.9%
2025-12-09
92%
2025-12-10
96%
2025-12-11
92%
2025-12-12
100%
2025-12-13
100%
2025-12-14
100%
2025-12-15
96%
2025-12-16
91.8%
2025-12-17
100%
2025-12-18
100%
2025-12-19
99.6%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Shapes present in the GTFS have been ignored, some rules are not enforced.
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-28 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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,325 | 27 times (90 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 96,428 | 27 times (90 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 2,005 | 27 times (90 % of validations) |
| W001 | Timestamps should be populated for all elements | 2,517 | 27 times (90 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2,517 | 27 times (90 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 5,034 | 27 times (90 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 4 | 4 times (13 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 72 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-28 at 14:02 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-12-28 at 14:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766926956"
}
}