Resource details
File name:
DONNEES TRANSPORT 2024
Format: gtfs-rt
This resource file is part of the dataset Réseau urbain UGGO.
Download availability
2026-09-11
100%
2026-09-12
100%
2026-09-13
100%
2026-09-14
100%
2026-09-15
100%
2026-09-16
100%
2026-09-17
100%
2026-09-18
100%
2026-09-19
100%
2026-09-20
100%
2026-09-21
100%
2026-09-22
100%
2026-09-23
100%
2026-09-24
100%
2026-09-25
100%
2026-09-26
100%
2026-09-27
100%
2026-09-28
99.7%
2026-09-29
100%
2026-09-30
100%
2026-10-01
100%
2026-10-02
100%
2026-10-03
100%
2026-10-04
100%
2026-10-05
100%
2026-10-06
100%
2026-10-07
100%
2026-10-08
100%
2026-10-09
100%
2026-10-10
100%
2026-10-11
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-11 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 81 | 24 times (80 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 74 | 24 times (80 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 168 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 167 | 24 times (80 % 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 | 346 | 23 times (77 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 112 | 22 times (73 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 11 | 11 times (37 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 8 | 8 times (27 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 8 | 7 times (23 % 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 | 2 | 2 times (7 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-10-12 at 01:21 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-10-12 at 01:21 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1791760907"
}
}