gtfs-rt Transport open dataset - GTFS-RT - Mises à jour des trajets en temps réel for Réseau urbain Ametis

Resource details

File name: GTFS-RT - Mises à jour des trajets en temps réel

Format: gtfs-rt

Les mises à jour des trajets vous informent des fluctuations d’horaires. Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.

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

GTFS - pour être utilisé avec le GTFS-RT

Associated GTFS file

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

❌153 errors, 7 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 153 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 27-14-2-B-080600 stop_id 1080 arrival_time 08:38:33 (1774424313) is less than previous stop arrival_time 08:38:34 (1774424314) - times must increase between two sequential stops
trip_id 27-14-2-B-080600 stop_id 1080 arrival_time 08:38:33 (1774424313) is less than previous stop departure_time 08:38:34 (1774424314) - times must increase between two sequential stops
trip_id 27-14-2-B-080600 stop_id 1080 departure_time 08:38:33 (1774424313) is less than previous stop departure_time 08:38:34 (1774424314) - times must increase between two sequential stops
trip_id 27-14-2-B-080600 stop_id 1080 departure_time 08:38:33 (1774424313) is less than previous stop arrival_time 08:38:34 (1774424314) - times must increase between two sequential stops
trip_id 27-10-3-B-074501 stop_id 846 arrival_time 08:12:30 (1774422750) is less than previous stop arrival_time 08:13:11 (1774422791) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 27-13-2-B-044501 does not have a vehicle_id
trip_id 27-N3-9-B-055100 does not have a vehicle_id
trip_id 27-5B-11-B-054601 does not have a vehicle_id
trip_id 27-L-7-B-063301 does not have a vehicle_id
trip_id 27-N3-10-B-072701 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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	4,981	31 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	182	30 times (97 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	2	2 times (6 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	1	1 times (3 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	26	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-26 at 03:22 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-26 at 03:22 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1774491766"
  }
}