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

❌3,200 errors, 1,311 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-19 at 08:05 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 24 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 chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:aaa13cdd-af52-4aae-9f1a-224f4c8404f6:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC 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 24 errors

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

Sample errors

route_id BSAScol61133 does not exist in the GTFS data routes.txt
route_id CAT56Scol60375 does not exist in the GTFS data routes.txt
route_id AVBScol60830 does not exist in the GTFS data routes.txt
route_id MorioLigne602 does not exist in the GTFS data routes.txt
route_id MAURYLigne609 does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.21335 does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.17963 does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.21337 does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id bre_vannes_2024_2025.17969 does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC stop_id keoskol.11214710 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 2,861 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-336134203 stop_sequence 46 arrival_time 07:18:02 (1768803482) is less than previous stop arrival_time 08:19:18 (1768807158) - times must increase between two sequential stops
trip_id 2-336134203 stop_sequence 46 arrival_time 07:18:02 (1768803482) is less than previous stop departure_time 08:19:18 (1768807158) - times must increase between two sequential stops
trip_id 2-121765929 stop_sequence 34 arrival_time 08:15:26 (1768806926) is equal to previous stop arrival_time 08:15:26 (1768806926) - times must increase between two sequential stops
trip_id 2-121765929 stop_sequence 34 arrival_time 08:15:26 (1768806926) is equal to previous stop departure_time 08:15:26 (1768806926) - times must increase between two sequential stops
trip_id 2-121765929 stop_sequence 34 departure_time 08:15:26 (1768806926) is equal to previous stop departure_time 08:15:26 (1768806926) - times must increase between two sequential stops

trip start_time does not match first GTFS arrival_time E023 10 errors

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

Sample errors

GTFS-rt trip_id 2-5671092818 start_time is 13:15:00 and GTFS initial arrival_time is 13:20:00 - times do not match
GTFS-rt trip_id 2-5671027272 start_time is 11:22:00 and GTFS initial arrival_time is 11:32:00 - times do not match
GTFS-rt trip_id 2-5671092439 start_time is 11:50:00 and GTFS initial arrival_time is 12:00:00 - times do not match
GTFS-rt trip_id 2-5671026900 start_time is 12:20:00 and GTFS initial arrival_time is 12:35:00 - times do not match
GTFS-rt trip_id 2-5671092232 start_time is 17:30:00 and GTFS initial arrival_time is 17:25:00 - times do not match

stop_time_update departure time is before arrival time E025 7 errors

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.

Sample errors

trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_sequence 11 departure_time 08:05:27 (1768806327) is less than the same stop arrival_time 08:05:33 (1768806333) - departure time must be equal to or greater than arrival time
trip_id 22-2684551169 stop_sequence 9 departure_time 08:04:36 (1768806276) is less than the same stop arrival_time 08:04:51 (1768806291) - departure time must be equal to or greater than arrival time
trip_id 22-1912668161 stop_sequence 5 departure_time 08:04:48 (1768806288) is less than the same stop arrival_time 08:04:52 (1768806292) - departure time must be equal to or greater than arrival time
trip_id 22-1342242817 stop_sequence 6 departure_time 08:04:04 (1768806244) is less than the same stop arrival_time 08:04:58 (1768806298) - departure time must be equal to or greater than arrival time
trip_id 22-2617442305 stop_sequence 5 departure_time 08:04:48 (1768806288) is less than the same stop arrival_time 08:05:41 (1768806341) - departure time must be equal to or greater than arrival time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 104 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-5671092227 stop_sequence 7 has stop_id 4359 but GTFS stop_sequence 7 has stop_id 6816 - stop_ids should be the same
GTFS-rt trip_id 2-5671092227 stop_sequence 8 has stop_id 4360 but GTFS stop_sequence 8 has stop_id 4359 - stop_ids should be the same
GTFS-rt trip_id 2-5671092227 stop_sequence 9 has stop_id 4419 but GTFS stop_sequence 9 has stop_id 4360 - stop_ids should be the same
GTFS-rt trip_id 2-5671092227 stop_sequence 10 has stop_id 4347 but GTFS stop_sequence 10 has stop_id 4419 - stop_ids should be the same
GTFS-rt trip_id 2-5671092227 stop_sequence 11 has stop_id 4350 but GTFS stop_sequence 11 has stop_id 4347 - stop_ids should be the same

Warnings

timestamp not populated W001 740 errors

Timestamps should be populated for all elements

Sample errors

trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not have a timestamp
trip_id chouette:VehicleJourney:b291fc00-a717-4ec7-8aae-8fa660ab5c32:LOC does not have a timestamp
trip_id 2-319160397 does not have a timestamp
trip_id 2-19136573 does not have a timestamp

vehicle_id not populated W002 571 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 2-17039438 does not have a vehicle_id
trip_id 2-19136586 does not have a vehicle_id
trip_id 2-17039432 does not have a vehicle_id
trip_id 2-19136585 does not have a vehicle_id
trip_id 2-17039431 does not have a vehicle_id

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,506	25 times (83 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	10,180	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	1,018	23 times (77 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	354	23 times (77 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	2,381	23 times (77 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	59,035	23 times (77 % 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.	98	21 times (70 % 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	82	10 times (33 % 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	526	6 times (20 % of validations)

GTFS-RT feed content

Entities

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


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