Resource details
This resource file is part of the dataset Réseau urbain TaM.
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
❌34 errors, 114 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-04 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 34 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 1583123112-16 stop_id 2459 arrival_time 07:41:30 (1767508890) is equal to previous stop arrival_time 07:41:30 (1767508890) - times must increase between two sequential stops
- trip_id 1583123112-16 stop_id 2459 arrival_time 07:41:30 (1767508890) is equal to previous stop departure_time 07:41:30 (1767508890) - times must increase between two sequential stops
- trip_id 1583017164-16 stop_id 594 arrival_time 08:11:32 (1767510692) is less than previous stop arrival_time 08:11:35 (1767510695) - times must increase between two sequential stops
- trip_id 1583017164-16 stop_id 594 arrival_time 08:11:32 (1767510692) is less than previous stop departure_time 08:11:35 (1767510695) - times must increase between two sequential stops
- trip_id 1583017164-16 stop_id 594 departure_time 08:11:32 (1767510692) is less than previous stop departure_time 08:11:35 (1767510695) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 114 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1583188044-16 does not have a vehicle_id
- trip_id 1583188006-16 does not have a vehicle_id
- trip_id 1583188083-16 does not have a vehicle_id
- trip_id 1583188007-16 does not have a vehicle_id
- trip_id 1583188040-16 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. | 708 | 13 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2,683 | 13 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 68 | 5 times (38 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 251 | 5 times (38 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 8 | 2 times (15 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-16 at 03:02 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-01-16 at 03:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768528928"
}
}