Resource details

File name: Lien vers le GTFS RT DU SAEIV de Lorient Agglomération
Format: gtfs-rt

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

Download availability

2026-10-23
100%
2026-10-24
100%
2026-10-25
100%
2026-10-26
100%
2026-10-27
100%
2026-10-28
100%
2026-10-29
100%
2026-10-30
100%
2026-10-31
100%
2026-11-01
100%
2026-11-02
96.6%
2026-11-03
100%
2026-11-04
100%
2026-11-05
100%
2026-11-06
100%
2026-11-07
100%
2026-11-08
100%
2026-11-09
100%
2026-11-10
100%
2026-11-11
100%
2026-11-12
100%
2026-11-13
100%
2026-11-14
100%
2026-11-15
100%
2026-11-16
100%
2026-11-17
100%
2026-11-18
100%
2026-11-19
100%
2026-11-20
100%
2026-11-21
100%
2026-11-22
100%
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

❌799 errors, 87 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-21 at 08:14 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 1 error

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 417490 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 1 error

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

Sample errors
  • route_id 113 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 418344 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 418343 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 417897 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 417898 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 418673 stop_id GE6 does not exist in GTFS data stops.txt

stop_times_updates not strictly sorted E002 1 error

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

Sample errors
  • trip_id 417823 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 64, 65] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 744 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 418319 stop_sequence 2 arrival_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 2 departure_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 arrival_time 08:14:18 (1795245258) is equal to previous stop arrival_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 arrival_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 departure_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 22 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 418344 stop_sequence 21 has stop_id GE2 but GTFS stop_sequence 21 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 418343 stop_sequence 21 has stop_id GE2 but GTFS stop_sequence 21 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 417897 stop_sequence 31 has stop_id GE2 but GTFS stop_sequence 31 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 418673 stop_sequence 1 has stop_id GE6 but GTFS stop_sequence 1 has stop_id GE-D - stop_ids should be the same
  • GTFS-rt trip_id 418675 stop_sequence 1 has stop_id GE6 but GTFS stop_sequence 1 has stop_id GE-D - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 2 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 418401 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 418400 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 87 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 417953 does not have a vehicle_id
  • trip_id 417954 does not have a vehicle_id
  • trip_id 418345 does not have a vehicle_id
  • trip_id 418347 does not have a vehicle_id
  • trip_id 418346 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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 100 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2,911 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 42 28 times (93 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 28 28 times (93 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 19,370 28 times (93 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 47 27 times (90 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 21 10 times (33 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 12 6 times (20 % 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 31 2 times (7 % of validations)

GTFS-RT feed content

Entities

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

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