Resource details
File name:
filbleu-gtfsrt-tripupdates
Format: gtfs-rt
Version Fil Bleu des alertes de services au format GTFS-RT
This resource file is part of the dataset Réseau urbain et périurbain Fil Bleu.
Download availability
2025-06-07
100%
2025-06-08
100%
2025-06-09
100%
2025-06-10
100%
2025-06-11
100%
2025-06-12
100%
2025-06-13
100%
2025-06-14
100%
2025-06-15
100%
2025-06-16
100%
2025-06-17
100%
2025-06-18
100%
2025-06-19
100%
2025-06-20
100%
2025-06-21
100%
2025-06-22
100%
2025-06-23
100%
2025-06-24
100%
2025-06-25
100%
2025-06-26
100%
2025-06-27
100%
2025-06-28
100%
2025-06-29
100%
2025-06-30
100%
2025-07-01
100%
2025-07-02
100%
2025-07-03
100%
2025-07-04
100%
2025-07-05
100%
2025-07-06
100%
2025-07-07
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
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-06 at 09:03 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 275 | 26 times (93 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 93 404 | 26 times (93 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 970 | 26 times (93 % of validations) |
W001 | Timestamps should be populated for all elements | 2 504 | 26 times (93 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 504 | 26 times (93 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 5 008 | 26 times (93 % 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 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-07 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-07-07 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1751846391"
}
}