Resource details

File name: Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • TripUpdate

This resource file is part of the dataset Réseau urbain et scolaire Guingamp-Paimpol Mobilité.

Download availability

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

5 errors, 71 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-31 at 08:15 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 1005001 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 1005 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 1005001 stop_id 10000 does not exist in GTFS data stops.txt
  • trip_id 1005001 stop_id 10001 does not exist in GTFS data stops.txt

stop_time_update departure time is before arrival time E025 1 error

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 25-33816577 stop_sequence 14 departure_time 08:14:40 (1767165280) is less than the same stop arrival_time 08:15:07 (1767165307) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 38 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 25-17104910 does not have a timestamp
  • trip_id 25-33816577 does not have a timestamp
  • trip_id 25-67371009 does not have a timestamp
  • trip_id 25-17170433 does not have a timestamp
  • trip_id 1005001 does not have a timestamp

vehicle_id not populated W002 33 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 25-17170436 does not have a vehicle_id
  • trip_id 25-17104900 does not have a vehicle_id
  • trip_id 25-17104901 does not have a vehicle_id
  • trip_id 25-17170434 does not have a vehicle_id
  • trip_id 25-17104903 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 257 7 times (70 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 231 7 times (70 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 4 4 times (40 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 4 4 times (40 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 8 4 times (40 % 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. 3 3 times (30 % of validations)

GTFS-RT feed content

Entities

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

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