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

✅No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-19 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.

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	779	27 times (90 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	683	23 times (77 % 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	12	12 times (40 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	26	11 times (37 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	26	11 times (37 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	238	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)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	16	2 times (7 % 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-19 at 18:07 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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-07-19 at 18:07 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "186688",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "departure": {
              "delay": 120,
              "time": "1784476320"
            },
            "stopId": "6659",
            "stopSequence": 1
          },
          {
            "arrival": {
              "delay": 63,
              "time": "1784476383"
            },
            "departure": {
              "delay": 72,
              "time": "1784476392"
            },
            "stopId": "6661",
            "stopSequence": 2
          },
          {
            "arrival": {
              "delay": 61,
              "time": "1784476441"
            },
            "departure": {
              "delay": 67,
              "time": "1784476447"
            },
            "stopId": "7721",
            "stopSequence": 3
          },
          {
            "arrival": {
              "delay": 86,
              "time": "1784476526"
            },
            "departure": {
              "delay": 118,
              "time": "1784476558"
            },
            "stopId": "6649",
            "stopSequence": 4
          },
          {
            "arrival": {
              "delay": 102,
              "time": "1784476662"
            },
            "departure": {
              "delay": 110,
              "time": "1784476670"
            },
            "stopId": "6653",
            "stopSequence": 5
          },
          {
            "arrival": {
              "delay": 111,
              "time": "1784476851"
            },
            "departure": {
              "delay": 141,
              "time": "1784476881"
            },
            "stopId": "6646",
            "stopSequence": 6
          },
          {
            "scheduleRelationship": "SKIPPED",
            "stopId": "6629",
            "stopSequence": 7
          },
          {
            "arrival": {
              "delay": 80,
              "time": "1784477060"
            },
            "stopId": "6639",
            "stopSequence": 8
          }
        ],
        "trip": {
          "directionId": 1,
          "routeId": "3",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260719",
          "startTime": "17:50:00",
          "tripId": "25-50462725"
        },
        "vehicle": {
          "id": "243",
          "label": "349",
          "licensePlate": "HH-604-ZE"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1784477232"
  }
}