Resource details
File name:
Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
This resource file is part of the dataset Réseau urbain et scolaire Guingamp-Paimpol Mobilité.
Download availability
2025-08-29
100%
2025-08-30
100%
2025-08-31
100%
2025-09-01
100%
2025-09-02
100%
2025-09-03
100%
2025-09-04
100%
2025-09-05
100%
2025-09-06
100%
2025-09-07
100%
2025-09-08
100%
2025-09-09
100%
2025-09-10
100%
2025-09-11
100%
2025-09-12
100%
2025-09-13
100%
2025-09-14
100%
2025-09-15
100%
2025-09-16
100%
2025-09-17
100%
2025-09-18
99.7%
2025-09-19
100%
2025-09-20
100%
2025-09-21
100%
2025-09-22
100%
2025-09-23
100%
2025-09-24
100%
2025-09-25
100%
2025-09-26
100%
2025-09-27
100%
2025-09-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
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-28 at 09:05 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 |
---|---|---|---|
W001 | Timestamps should be populated for all elements | 776 | 24 times (86 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 692 | 23 times (82 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 24 | 6 times (21 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 24 | 6 times (21 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 159 | 6 times (21 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 20 | 4 times (14 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-28 at 13:38 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-09-28 at 13:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759059527"
}
}