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

✅No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-15 at 08:10 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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	44,936	18 times (64 % of validations)
W001	Timestamps should be populated for all elements	10,520	18 times (64 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	8,219	18 times (64 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	660	16 times (57 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	311	16 times (57 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	2,246	16 times (57 % 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.	91	15 times (54 % 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,087	14 times (50 % 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	90	9 times (32 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	5	3 times (11 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	5	3 times (11 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	5	3 times (11 % of validations)
E041	Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update	1	1 times (4 % of validations)

GTFS-RT feed content

Entities

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


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