Resource details
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
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
❌939 errors, 67 warnings
Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-27 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 36 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 1-318963713 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 25-67239937 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 25-33685506 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 25-17104903 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 25-50462725 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 36 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 19 does not exist in the GTFS data routes.txt
- route_id 4 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 3 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 867 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 1-318963713 stop_id STP-26F10 does not exist in GTFS data stops.txt
- trip_id 1-318963713 stop_id STP-26F09 does not exist in GTFS data stops.txt
- trip_id 1-318963713 stop_id 17922 does not exist in GTFS data stops.txt
- trip_id 1-318963713 stop_id STP-26F08 does not exist in GTFS data stops.txt
- trip_id 1-318963713 stop_id STP-26F07 does not exist in GTFS data stops.txt
Warnings
timestamp not populated W001 36 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-318963713 does not have a timestamp
- trip_id 25-67239937 does not have a timestamp
- trip_id 25-33685506 does not have a timestamp
- trip_id 25-17104903 does not have a timestamp
- trip_id 25-50462725 does not have a timestamp
vehicle_id not populated W002 31 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 25-17170436 does not have a vehicle_id
- trip_id 25-17104900 does not have a vehicle_id
- trip_id 25-17104901 does not have a vehicle_id
- trip_id 25-17170434 does not have a vehicle_id
- trip_id 25-67502084 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 769 | 28 times (93 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 665 | 22 times (73 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 137 | 17 times (57 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 137 | 17 times (57 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,895 | 17 times (57 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 15 | 15 times (50 % 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. | 4 | 4 times (13 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8 | 1 times (3 % of validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-28 at 03:32 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 2026-07-28 at 03:32 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785202342"
}
}