Resource details
This resource file is part of the dataset Réseau urbain UGGO.
Download availability
Learn more
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
❌11 errors, 5 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-20 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 11 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 6710 stop_sequence 3 has stop_id 658603 but GTFS stop_sequence 3 has stop_id 426703 - stop_ids should be the same
- GTFS-rt trip_id 6710 stop_sequence 4 has stop_id 507103 but GTFS stop_sequence 4 has stop_id 507003 - stop_ids should be the same
- GTFS-rt trip_id 6710 stop_sequence 5 has stop_id 658703 but GTFS stop_sequence 5 has stop_id 439503 - stop_ids should be the same
- GTFS-rt trip_id 6710 stop_sequence 6 has stop_id 658803 but GTFS stop_sequence 6 has stop_id 439203 - stop_ids should be the same
- GTFS-rt trip_id 6710 stop_sequence 8 has stop_id 659003 but GTFS stop_sequence 8 has stop_id 438003 - stop_ids should be the same
Warnings
timestamp not populated W001 5 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 5884 does not have a timestamp
- trip_id 6710 does not have a timestamp
- trip_id 5982 does not have a timestamp
- trip_id 5569 does not have a timestamp
- trip_id 6645 does not have a timestamp
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 |
|---|---|---|---|
| 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 | 376 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 168 | 24 times (80 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 74 | 21 times (70 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 55 | 10 times (33 % 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. | 4 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-20 at 22:08 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-07-20 at 22:08 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1784578134"
}
}