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

❌52 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-12 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 52 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-319160387 stop_sequence 27 has stop_id 618 but GTFS stop_sequence 27 has stop_id 470 - stop_ids should be the same
GTFS-rt trip_id 2-319160387 stop_sequence 28 has stop_id 560 but GTFS stop_sequence 28 has stop_id 489 - stop_ids should be the same
GTFS-rt trip_id 2-319160387 stop_sequence 29 has stop_id 521 but GTFS stop_sequence 29 has stop_id 618 - stop_ids should be the same
GTFS-rt trip_id 2-319160387 stop_sequence 30 has stop_id 382 but GTFS stop_sequence 30 has stop_id 560 - stop_ids should be the same
GTFS-rt trip_id 2-319160387 stop_sequence 31 has stop_id 428 but GTFS stop_sequence 31 has stop_id 521 - stop_ids should be the same

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	12,693	21 times (75 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	9,905	21 times (75 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	53,330	20 times (71 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	730	19 times (68 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	381	19 times (68 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	2,751	19 times (68 % 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.	118	18 times (64 % 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,336	15 times (54 % 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	120	12 times (43 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	3	2 times (7 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	3	2 times (7 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	3	2 times (7 % 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-12 at 23:26 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-12 at 23:26 Europe/Paris. You can look at the GTFS-RT documentation.


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