Resource details

File name: GTFS-RT
Format: gtfs-rt

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

Download availability

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

62 errors, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-08 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 60 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 41029{2_24}-ETE25_E25_LMWJV stop_sequence 32 departure_time 09:00:20 (1754636420) is equal to previous stop departure_time 09:00:20 (1754636420) - times must increase between two sequential stops
  • trip_id 41334{11_24}-ETE25_E25_LMWJV stop_sequence 36 arrival_time 08:42:59 (1754635379) is less than previous stop arrival_time 09:03:08 (1754636588) - times must increase between two sequential stops
  • trip_id 41334{11_24}-ETE25_E25_LMWJV stop_sequence 36 arrival_time 08:42:59 (1754635379) is less than previous stop departure_time 09:03:08 (1754636588) - times must increase between two sequential stops
  • trip_id 41334{11_24}-ETE25_E25_LMWJV stop_sequence 36 departure_time 08:43:07 (1754635387) is less than previous stop departure_time 09:03:08 (1754636588) - times must increase between two sequential stops
  • trip_id 41334{11_24}-ETE25_E25_LMWJV stop_sequence 36 departure_time 08:43:07 (1754635387) is less than previous stop arrival_time 09:03:08 (1754636588) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 2 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 41029{2_24}-ETE25_E25_LMWJV stop_sequence 32 departure_time 09:00:20 (1754636420) is less than the same stop arrival_time 09:00:48 (1754636448) - departure time must be equal to or greater than arrival time
  • trip_id 41030{2_24}-ETE25_E25_LMWJV stop_sequence 4 departure_time 09:00:53 (1754636453) is less than the same stop arrival_time 09:01:22 (1754636482) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 9 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 41029{2_24}-ETE25_E25_LMWJV does not have a timestamp
  • trip_id 41334{11_24}-ETE25_E25_LMWJV does not have a timestamp
  • trip_id 41161{3_24}-ETE25_E25_LMWJVS does not have a timestamp
  • trip_id 41300{5_24}-ETE25_E25_LMWJV does not have a timestamp
  • trip_id 41266{4_24}-ETE25_E25_LMWJV does not have a timestamp
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 950 25 times (83 % of validations)
W001 Timestamps should be populated for all elements 245 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 11 11 times (37 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 11 11 times (37 % 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. 12 9 times (30 % of validations)

GTFS-RT feed content

Entities

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

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