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

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

2 957 errors, 1 290 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-01 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 23 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:cb277215-b8ef-4848-8f33-16880fd56527:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id chouette:VehicleJourney:67309930-e07e-49b6-afc5-46c916cff303:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id chouette:VehicleJourney:b63ae62c-dd08-4c0a-b966-8df89fe347b1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id chouette:VehicleJourney:1267fcef-9e99-44f6-bfa8-33b9e7d96560: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 23 errors

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

Sample errors
  • route_id MAURYLigne609 does not exist in the GTFS data routes.txt
  • route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
  • route_id BSAScol61137 does not exist in the GTFS data routes.txt
  • route_id BSALigne611 does not exist in the GTFS data routes.txt
  • route_id AVBLigne608 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:3f3655e5-ddc5-410d-a66a-ee3f0279b35c:LOC does not exist in GTFS data stops.txt
  • trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:5b4834b3-bdf7-402b-b6b3-d6e1db89d36f:LOC does not exist in GTFS data stops.txt
  • trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:bca95593-9f29-46ae-9eca-a9f5185b32a2:LOC does not exist in GTFS data stops.txt
  • trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:e462c1b3-6666-448e-b8ae-da455c43c7bf:LOC does not exist in GTFS data stops.txt
  • trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC stop_id chouette:StopArea:5d794600-ebc2-4ef7-89dc-5428268d8051:LOC does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 2 734 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:15:03 (1764569703) is less than previous stop arrival_time 08:20:04 (1764573604) - times must increase between two sequential stops
  • trip_id 2-336134203 stop_sequence 46 arrival_time 07:15:03 (1764569703) is less than previous stop departure_time 08:20:04 (1764573604) - times must increase between two sequential stops
  • trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:15:06 (1764573306) is equal to previous stop arrival_time 08:15:06 (1764573306) - times must increase between two sequential stops
  • trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 arrival_time 08:15:06 (1764573306) is equal to previous stop departure_time 08:15:06 (1764573306) - times must increase between two sequential stops
  • trip_id 2-121765929-M574A-LMCJV__ stop_sequence 34 departure_time 08:15:06 (1764573306) is equal to previous stop departure_time 08:15:06 (1764573306) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 6 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 2-121700380-V762A-LMCJV__ stop_sequence 18 departure_time 08:13:39 (1764573219) is less than the same stop arrival_time 08:13:45 (1764573225) - departure time must be equal to or greater than arrival time
  • trip_id 2-218431494 stop_sequence 20 departure_time 08:13:45 (1764573225) is less than the same stop arrival_time 08:13:46 (1764573226) - departure time must be equal to or greater than arrival time
  • trip_id 2-336134215 stop_sequence 8 departure_time 08:13:04 (1764573184) is less than the same stop arrival_time 08:13:30 (1764573210) - departure time must be equal to or greater than arrival time
  • trip_id 22-2986409985 stop_sequence 10 departure_time 08:13:28 (1764573208) is less than the same stop arrival_time 08:13:55 (1764573235) - departure time must be equal to or greater than arrival time
  • trip_id 22-1124139009 stop_sequence 2 departure_time 08:10:24 (1764573024) is less than the same stop arrival_time 08:13:07 (1764573187) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 732 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 22-486604801 does not have a timestamp
  • trip_id 2-288161794 does not have a timestamp
  • trip_id 2-336134203 does not have a timestamp
  • trip_id 2-121700400 does not have a timestamp
  • trip_id 2-121765929-M574A-LMCJV__ does not have a timestamp

vehicle_id not populated W002 558 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 2-168689696-V10114-LMCJV__ does not have a vehicle_id
  • trip_id 2-169345037-V10114-LMCJV__ does not have a vehicle_id
  • trip_id 2-185466894 does not have a vehicle_id
  • trip_id 2-185729036 does not have a vehicle_id
  • trip_id 2-185663498 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 14 952 27 times (84 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 11 620 26 times (81 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 2 675 24 times (75 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 466 24 times (75 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 167 24 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. 61 933 24 times (75 % 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. 141 24 times (75 % 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 176 12 times (38 % 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 1 1 times (3 % of validations)
E041 Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-01 at 21:38 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 2025-12-01 at 21:38 Europe/Paris. You can look at the GTFS-RT documentation.

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