gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (TripUpdate) for Réseau urbain Kicéo - CA Golfe du Morbihan

Resource details

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

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Kicéo.

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

❌79 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-02 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 11 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id 2-85852236 stop_sequence [7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 18, 19, 20, 20] is not strictly sorted by increasing stop_sequence
trip_id 2-85983275 stop_sequence [9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 2-85852235 stop_sequence [20, 20] is not strictly sorted by increasing stop_sequence
trip_id 2-135921680 stop_sequence [16, 18, 18] is not strictly sorted by increasing stop_sequence
trip_id 2-85983267 stop_sequence [1, 2, 3, 4, 5, 6, 7, 9, 10, 10] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 32 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 2-85852236 stop_sequence 20 arrival_time 09:31:50 (1775115110) is less than previous stop arrival_time 09:33:50 (1775115230) - times must increase between two sequential stops
trip_id 2-85852236 stop_sequence 20 arrival_time 09:31:50 (1775115110) is less than previous stop departure_time 09:33:50 (1775115230) - times must increase between two sequential stops
trip_id 2-85852236 stop_sequence 20 departure_time 09:31:50 (1775115110) is less than previous stop departure_time 09:33:50 (1775115230) - times must increase between two sequential stops
trip_id 2-85852236 stop_sequence 20 departure_time 09:31:50 (1775115110) is less than previous stop arrival_time 09:33:50 (1775115230) - times must increase between two sequential stops
trip_id 2-85983275 stop_sequence 10 arrival_time 09:13:35 (1775114015) is less than previous stop arrival_time 09:15:35 (1775114135) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 11 errors

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors

trip_id 2-85852236 has repeating stop_sequence 20 - stop_sequence must increase for each stop_time_update
trip_id 2-85983275 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 2-85852235 has repeating stop_sequence 20 - stop_sequence must increase for each stop_time_update
trip_id 2-135921680 has repeating stop_sequence 18 - stop_sequence must increase for each stop_time_update
trip_id 2-85983267 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 14 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 2-251854852 stop_sequence 5 has stop_id 4009 but GTFS stop_sequence 5 has stop_id 6464 - stop_ids should be the same
GTFS-rt trip_id 2-251854852 stop_sequence 7 has stop_id 4234 but GTFS stop_sequence 7 has stop_id 4012 - stop_ids should be the same
GTFS-rt trip_id 2-85852236 stop_sequence 18 has stop_id 245 but GTFS stop_sequence 18 has stop_id 367 - stop_ids should be the same
GTFS-rt trip_id 2-85852236 stop_sequence 19 has stop_id 274 but GTFS stop_sequence 19 has stop_id 574 - stop_ids should be the same
GTFS-rt trip_id 2-85983275 stop_sequence 9 has stop_id 605 but GTFS stop_sequence 9 has stop_id 373 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 11 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors

GTFS-rt trip_id 2-85852236 contains stop_sequence 20 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2-85983275 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2-85852235 contains stop_sequence 20 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2-135921680 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2-85983267 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip

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
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	96	16 times (57 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	13	12 times (43 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	24	5 times (18 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	24	5 times (18 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	24	5 times (18 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	40	3 times (11 % of validations)

GTFS-RT feed content

Entities

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


        {
  "entity": [
    {
      "id": "66",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "arrival": {
              "time": "1775165002"
            },
            "departure": {
              "time": "1775165002"
            },
            "stopId": "493",
            "stopSequence": 3
          },
          {
            "arrival": {
              "time": "1775165062"
            },
            "departure": {
              "time": "1775165062"
            },
            "stopId": "511",
            "stopSequence": 4
          },
          {
            "arrival": {
              "time": "1775165122"
            },
            "departure": {
              "time": "1775165122"
            },
            "stopId": "603",
            "stopSequence": 5
          }
        ],
        "timestamp": "1775164964",
        "trip": {
          "directionId": 0,
          "routeId": "21",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260402",
          "tripId": "2-353042442"
        },
        "vehicle": {
          "id": "66",
          "label": "97210",
          "licensePlate": "FC 194 MS"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1775164964"
  }
}