transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: Horaires en temps réel des lignes régulières du réseau Cap Cotentin
Format: gtfs-rt
Download

Horaires en temps réel des lignes urbaines et intercommunales du réseau de mobilité Cap Cotentin de la Communauté d’agglomération du Cotentin

Horaires en temps réel du réseau Cap Cotentin au format GTFS-RT comprenant :

  • Les lignes urbaines 1 à 6
  • Les lignes intercommunales A à G

This resource file is part of the dataset Réseau urbain Cap Cotentin.

Horaires théoriques des lignes régulières et secondaires du réseau Cap Cotentin

Associated GTFS file

Download availability

2026-02-18
99.6%
2026-02-19
98.8%
2026-02-20
99.3%
2026-02-21
100%
2026-02-22
99.2%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
99.4%
2026-03-02
99.8%
2026-03-03
99.6%
2026-03-04
100%
2026-03-05
98.4%
2026-03-06
98.4%
2026-03-07
100%
2026-03-08
99.5%
2026-03-09
99.4%
2026-03-10
98.6%
2026-03-11
98.5%
2026-03-12
99.6%
2026-03-13
98.4%
2026-03-14
99.2%
2026-03-15
97.3%
2026-03-16
98.9%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
89.8%
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

❌62 errors, 89 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-20 at 08:08 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 18 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 61289ff756b38782f6019df0 trip_id 3763955-2025_H-Mult_J&V-Jeu-Ven-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f6019f96 trip_id 3757951-2025_H-Mult_J&V-Jeu-Ven-00-1101110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 6321db03e6d440a4960cfdce trip_id 3757950-2025_H-Mult_J&V-Jeu-Ven-00-1101110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f6019a4e trip_id 3758115-2025_H-Mult_J&V-Jeu-Ven-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f601a12c trip_id 3758382-2025_H-Mult_J&V-Jeu-Ven-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED

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

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

Sample errors
  • trip_id 3757950-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL2 does not exist in GTFS data stops.txt
  • trip_id 3757951-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL2 does not exist in GTFS data stops.txt
  • trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt
  • trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 8 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 3745770-2025_H-Mult_J&V-Jeu-Ven-00-0001100 stop_sequence 35 arrival_time 00:20:10 (1773962410) is less than previous stop arrival_time 00:28:22 (1773962902) - times must increase between two sequential stops
  • trip_id 3745770-2025_H-Mult_J&V-Jeu-Ven-00-0001100 stop_sequence 35 arrival_time 00:20:10 (1773962410) is less than previous stop departure_time 00:27:35 (1773962855) - times must increase between two sequential stops
  • trip_id 3745770-2025_H-Mult_J&V-Jeu-Ven-00-0001100 stop_sequence 35 departure_time 00:20:10 (1773962410) is less than previous stop departure_time 00:27:35 (1773962855) - times must increase between two sequential stops
  • trip_id 3745770-2025_H-Mult_J&V-Jeu-Ven-00-0001100 stop_sequence 35 departure_time 00:20:10 (1773962410) is less than previous stop arrival_time 00:28:22 (1773962902) - times must increase between two sequential stops
  • trip_id 3746154-2025_H-Mult_J&V-Jeu-Ven-00-0001100 stop_sequence 49 arrival_time 00:34:10 (1773963250) is less than previous stop arrival_time 00:34:43 (1773963283) - times must increase between two sequential stops

stop_time_update doesn't have arrival or departure E043 28 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id 3745649-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 1 doesn't have arrival or departure
  • trip_id 3745649-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 2 doesn't have arrival or departure
  • trip_id 3745649-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 3 doesn't have arrival or departure
  • trip_id 3745649-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 4 doesn't have arrival or departure
  • trip_id 3745649-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 5 doesn't have arrival or departure

VehiclePosition and TripUpdate ID pairing mismatch E047 4 errors

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Sample errors
  • trip_id 3757950-2025_H-Mult_J&V-Jeu-Ven-00-1101110 and vehicle_id 6321db03e6d440a4960cfdce pairing in VehiclePositions does not match trip_id 3757944-2025_H-Mult_J&V-Jeu-Ven-00-1101110 and vehicle_id 6321db03e6d440a4960cfdce pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3758057-2025_H-Mult_J&V-Jeu-Ven-00 and vehicle_id 61289ff756b38782f6019f09 pairing in VehiclePositions does not match trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-00-1101110 and vehicle_id 61289ff756b38782f6019f09 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3763955-2025_H-Mult_J&V-Jeu-Ven-00-1110100 and vehicle_id 61289ff756b38782f6019df0 pairing in VehiclePositions does not match trip_id 3758175-2025_H-Mult_J&V-Jeu-Ven-00-1110100 and vehicle_id 61289ff756b38782f6019df0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3758049-2025_H-Mult_J&V-Jeu-Ven-00 and vehicle_id 6321daf7e6d440a4960cfdc7 pairing in VehiclePositions does not match trip_id 3758247-2025_H-Mult_J&V-Jeu-Ven-00-1111100 and vehicle_id 6321daf7e6d440a4960cfdc7 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Warnings

ID in one feed missing from the other W003 89 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 3745709-2025_H-Mult_J&V-Jeu-Ven-00-0001100 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3757944-2025_H-Mult_J&V-Jeu-Ven-00-1101110 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3748507-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3747887-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3746135-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 92 30 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 4,099 30 times (100 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 2,105 30 times (100 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 469 29 times (97 % 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,749 28 times (93 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 260 27 times (90 % 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. 52 12 times (40 % 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 15 5 times (17 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-21 at 00:51 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-21 at 00:51 Europe/Paris. You can look at the GTFS-RT documentation.

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