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
❌26 errors, 282 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-30 at 08:16 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 20-14-1423-0-091000 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 20-14-1423-0-100000 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 24 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 1583010348-20 stop_id 408 arrival_time 08:42:16 (1769758936) is less than previous stop arrival_time 08:42:29 (1769758949) - times must increase between two sequential stops
- trip_id 1583010348-20 stop_id 408 arrival_time 08:42:16 (1769758936) is less than previous stop departure_time 08:42:29 (1769758949) - times must increase between two sequential stops
- trip_id 1583010348-20 stop_id 408 departure_time 08:42:16 (1769758936) is less than previous stop departure_time 08:42:29 (1769758949) - times must increase between two sequential stops
- trip_id 1583010348-20 stop_id 408 departure_time 08:42:16 (1769758936) is less than previous stop arrival_time 08:42:29 (1769758949) - times must increase between two sequential stops
- trip_id 1583001549-20 stop_id 129 arrival_time 08:48:10 (1769759290) is less than previous stop arrival_time 08:48:11 (1769759291) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 281 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1583191782-20 does not have a vehicle_id
- trip_id 1583191779-20 does not have a vehicle_id
- trip_id 1583191748-20 does not have a vehicle_id
- trip_id 1583191383-20 does not have a vehicle_id
- trip_id 1583191384-20 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 1 min 7 sec old which is greater than the recommended age of 65 seconds
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. | 126 | 3 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 672 | 3 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 | 7 | 2 times (67 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 1 | 1 times (33 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 112 | 1 times (33 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (33 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-03 at 03:04 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-02-03 at 03:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770084267"
}
}