gtfs-rt Transport open dataset - Tilt - Lannion-Trégor Communauté for Réseau urbain Tilt

Resource details

File name: Tilt - Lannion-Trégor Communauté

Format: gtfs-rt

Fichier GTFS-RT

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

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

⚠️16 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-11 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id B02-02 does not have a vehicle_id
trip_id D02-01 Marché does not have a vehicle_id
trip_id E02-01 MARC does not have a vehicle_id
trip_id A01-03 does not have a vehicle_id
trip_id LM01-02 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 7 min 17 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id B02-02 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
trip_id B02-02 does not have a schedule_relationship
trip_id D02-01 Marché stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
trip_id D02-01 Marché does not have a schedule_relationship
trip_id E02-01 MARC stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship

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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	125	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	250	30 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	29	29 times (97 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-08-11 at 20:38 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 14 625 seconds. Try to update your feed at most every 30 seconds.

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 2025-08-11 at 20:38 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:M02-20",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "arrival": {
              "delay": 1,
              "time": "1754935254"
            },
            "departure": {
              "delay": 1,
              "time": "1754937510"
            },
            "stopId": "740",
            "stopSequence": 21
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754935335"
            },
            "departure": {
              "delay": 1,
              "time": "1754937570"
            },
            "stopId": "719",
            "stopSequence": 22
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754935417"
            },
            "departure": {
              "delay": 1,
              "time": "1754937750"
            },
            "stopId": "1245",
            "stopSequence": 23
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754938110"
            },
            "departure": {
              "delay": 1,
              "time": "1754938110"
            },
            "stopId": "618",
            "stopSequence": 24
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754938170"
            },
            "departure": {
              "delay": 1,
              "time": "1754938170"
            },
            "stopId": "653",
            "stopSequence": 25
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754938290"
            },
            "departure": {
              "delay": 1,
              "time": "1754938290"
            },
            "stopId": "659",
            "stopSequence": 26
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754938410"
            },
            "departure": {
              "delay": 1,
              "time": "1754938410"
            },
            "stopId": "1139",
            "stopSequence": 27
          },
          {
            "arrival": {
              "delay": 1,
              "time": "1754938710"
            },
            "departure": {
              "delay": 1,
              "time": "1754938710"
            },
            "stopId": "8455",
            "stopSequence": 28
          }
        ],
        "timestamp": "1754936738",
        "trip": {
          "directionId": 1,
          "routeId": "Le Macareux",
          "tripId": "M02-20"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1754937493"
  }
}