Resource details
This resource file is part of the dataset Réseau urbain Distribus.
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
❌1 error, 218 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-09 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
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 403-0728 stop_sequence 19 departure_time 08:00:19 (1765263619) is less than the same stop arrival_time 08:02:19 (1765263739) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 73 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1103-0750 does not have a vehicle_id
- trip_id 1101-0805 does not have a vehicle_id
- trip_id 1103-0820 does not have a vehicle_id
- trip_id 10-0805 does not have a vehicle_id
- trip_id 10-0835 does not have a vehicle_id
schedule_relationship not populated W009 145 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1103-0750 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1103-0750 does not have a schedule_relationship
- trip_id 1101-0805 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1101-0805 does not have a schedule_relationship
- trip_id 1103-0820 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 629 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 3 231 | 30 times (100 % 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. | 18 | 14 times (47 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 11 | 11 times (37 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-10 at 03:45 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 2025-12-10 at 03:45 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:MT3-0254",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"delay": 3084,
"time": "1765334724"
},
"stopId": "Burgfelderhof_R",
"stopSequence": 1
},
{
"arrival": {
"delay": 3144,
"time": "1765334844"
},
"departure": {
"delay": 3144,
"time": "1765334844"
},
"stopId": "Waldighoferstrasse_AR",
"stopSequence": 2
},
{
"arrival": {
"delay": 2904,
"time": "1765335264"
},
"departure": {
"delay": 2904,
"time": "1765334964"
},
"stopId": "Pilgerstrasse_AR",
"stopSequence": 7
}
],
"timestamp": "1765331133",
"trip": {
"directionId": 1,
"routeId": "T3",
"tripId": "MT3-0254"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1765334718"
}
}