Resource details
This resource file is part of the dataset Réseau urbain TaM.
Related resources
Horaires de référence suburbain (GTFS)
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
❌4 errors, 66 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-01 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 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 202608011583443776 stop_id 0:36265 arrival_time 09:10:48 (1785568248) is less than previous stop arrival_time 09:12:13 (1785568333) - times must increase between two sequential stops
- trip_id 202608011583443776 stop_id 0:36265 arrival_time 09:10:48 (1785568248) is less than previous stop departure_time 09:12:13 (1785568333) - times must increase between two sequential stops
- trip_id 202608011583443776 stop_id 0:36265 departure_time 09:10:48 (1785568248) is less than previous stop departure_time 09:12:13 (1785568333) - times must increase between two sequential stops
- trip_id 202608011583443776 stop_id 0:36265 departure_time 09:10:48 (1785568248) is less than previous stop arrival_time 09:12:13 (1785568333) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 66 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 202608011583443774 does not have a vehicle_id
- trip_id 202608011583443775 does not have a vehicle_id
- trip_id 202608011583308416 does not have a vehicle_id
- trip_id 202608011583443773 does not have a vehicle_id
- trip_id 202608011583308429 does not have a vehicle_id
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. | 250 | 23 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,368 | 23 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 1 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-03 at 00:57 Europe/Paris.
trip_updates (3) 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 2026-08-03 at 00:57 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "1583438153",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1785711720",
"uncertainty": 120
},
"stopId": "0:09234"
}
],
"timestamp": "1785711441",
"trip": {
"directionId": 1,
"routeId": "92",
"scheduleRelationship": "SCHEDULED",
"tripId": "202608021583438153"
},
"vehicle": {
"id": "762",
"label": "762"
}
}
},
{
"id": "1583438148",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1785712800",
"uncertainty": 120
},
"stopId": "0:92110"
}
],
"timestamp": "1785711441",
"trip": {
"directionId": 0,
"routeId": "92",
"scheduleRelationship": "SCHEDULED",
"tripId": "202608021583438148"
}
}
},
{
"id": "1583438147",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1785711900"
},
"stopId": "0:92110"
}
],
"timestamp": "1785711441",
"trip": {
"directionId": 0,
"routeId": "92",
"scheduleRelationship": "SCHEDULED",
"tripId": "202608021583438147"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785711441"
}
}