gtfs-rt Transport open dataset - Prochains passages des lignes du réseau Astuce exploitées par TNI for Réseau urbain Astuce

Resource details

File name: Prochains passages des lignes du réseau Astuce exploitées par TNI

Format: gtfs-rt

Ce fichier au format GTFS-RT contient les prochains passages (trip updates) pour les lignes du réseau Astuce exploitées en propre par TNI, à savoir les lignes 26 et 530.

La fréquence de rafraîchissement de ces données est de 30 secondes.

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

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

⚠️60 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-17 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 20 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id TNI:585 does not have a vehicle_id
trip_id TNI:83 does not have a vehicle_id
trip_id TNI:103 does not have a vehicle_id
trip_id TNI:255 does not have a vehicle_id
trip_id TNI:493 does not have a vehicle_id

schedule_relationship not populated W009 40 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id TNI:585 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id TNI:585 does not have a schedule_relationship
trip_id TNI:83 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id TNI:83 does not have a schedule_relationship
trip_id TNI:103 stop_sequence 1 (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	483	24 times (86 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	966	24 times (86 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-18 at 04:24 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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-03-18 at 04:24 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1773804275"
  }
}