gtfs-rt Transport open dataset - Mises à jour des trajets suburbain for Réseau urbain TaM

Resource details

File name: Mises à jour des trajets suburbain

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain TaM.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌98 errors, 13 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

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 19 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 202601041583140998 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 202601041583141004 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 202601041583199184 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 202601041583203003 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 202601041583194667 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt stop_id does not exist in GTFS data E011 71 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id 202601041583140998 stop_id 0:26112 does not exist in GTFS data stops.txt
trip_id 202601041583141004 stop_id 0:23216 does not exist in GTFS data stops.txt
trip_id 202601041583199184 stop_id 0:20139 does not exist in GTFS data stops.txt
trip_id 202601041583203003 stop_id 0:35110 does not exist in GTFS data stops.txt
trip_id 202601041583194667 stop_id 0:33100 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 8 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 202601041583176227 stop_id 0:23125 departure_time 09:00:00 (1767513600) is less than previous stop departure_time 09:16:08 (1767514568) - times must increase between two sequential stops
trip_id 202601041583176227 stop_id 0:23125 departure_time 09:00:00 (1767513600) is less than previous stop arrival_time 09:16:08 (1767514568) - times must increase between two sequential stops
trip_id 202601041583176227 stop_id 0:23237 arrival_time 09:01:28 (1767513688) is less than previous stop arrival_time 09:16:08 (1767514568) - times must increase between two sequential stops
trip_id 202601041583176227 stop_id 0:23237 departure_time 09:01:28 (1767513688) is less than previous stop arrival_time 09:16:08 (1767514568) - times must increase between two sequential stops
trip_id 202601041583176227 stop_id 0:22113 arrival_time 09:17:08 (1767514628) is less than previous stop arrival_time 09:17:23 (1767514643) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 13 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 202601041583140998 does not have a vehicle_id
trip_id 202601041583199184 does not have a vehicle_id
trip_id 202601041583203003 does not have a vehicle_id
trip_id 202601041583194667 does not have a vehicle_id
trip_id 202601041583198800 does not have a vehicle_id

Validate this GTFS-RT now

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	124	3 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	897	3 times (100 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	56	3 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	90	3 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-07 at 02:33 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-07 at 02:33 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "1583156628",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "departure": {
              "time": "1767711726",
              "uncertainty": 120
            },
            "stopId": "0:23104"
          }
        ],
        "timestamp": "1767749605",
        "trip": {
          "directionId": 0,
          "routeId": "26",
          "scheduleRelationship": "SCHEDULED",
          "tripId": "202601061583156628"
        },
        "vehicle": {
          "id": "643",
          "label": "643"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1767749605"
  }
}