gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (TripUpdate) for Réseau urbain et scolaire Guingamp-Paimpol Mobilité - CA Guingamp-Paimpol Agglomération de l'Armor à l'Argoat

Resource details

File name: Données en temps réel au format GTFS-RT (TripUpdate)

Format: gtfs-rt

Download

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

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

❌12 errors, 4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-14 at 08:11 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 2 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 1004001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1006001 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 2 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id 1004 does not exist in the GTFS data routes.txt
route_id 1006 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 4 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id 1004001 stop_id 10000 does not exist in GTFS data stops.txt
trip_id 1004001 stop_id 10001 does not exist in GTFS data stops.txt
trip_id 1006001 stop_id 10000 does not exist in GTFS data stops.txt
trip_id 1006001 stop_id 10001 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 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 B_B_LMWJV_021 stop_sequence 26 arrival_time 08:11:30 (1794640290) is equal to previous stop arrival_time 08:11:30 (1794640290) - times must increase between two sequential stops
trip_id B_B_LMWJV_021 stop_sequence 26 arrival_time 08:11:30 (1794640290) is equal to previous stop departure_time 08:11:30 (1794640290) - times must increase between two sequential stops
trip_id B_B_LMWJV_021 stop_sequence 26 departure_time 08:11:30 (1794640290) is equal to previous stop departure_time 08:11:30 (1794640290) - times must increase between two sequential stops
trip_id B_B_LMWJV_021 stop_sequence 26 departure_time 08:11:30 (1794640290) is equal to previous stop arrival_time 08:11:30 (1794640290) - times must increase between two sequential stops

Warnings

timestamp not populated W001 4 errors

Timestamps should be populated for all elements

Sample errors

trip_id B_B_LMWJV_021 does not have a timestamp
trip_id A_A_SAMEDI_001 does not have a timestamp
trip_id 1004001 does not have a timestamp
trip_id 1006001 does not have a timestamp

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
W001	Timestamps should be populated for all elements	227	25 times (83 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	94	18 times (60 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	94	18 times (60 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	579	18 times (60 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	46	11 times (37 % 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.	5	5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-11-14 at 23:00 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 2026-11-14 at 23:00 Europe/Paris. You can look at the GTFS-RT documentation.


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