Resource details

File name: Mises à jour des trajets en temps réel
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Sète Agglopole Mobilité.

Download availability

2025-12-09
100%
2025-12-10
100%
2025-12-11
100%
2025-12-12
100%
2025-12-13
100%
2025-12-14
100%
2025-12-15
100%
2025-12-16
100%
2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
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

⚠️264 warnings

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

Warnings

timestamp not populated W001 132 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 96067_260106-5410 does not have a timestamp
  • trip_id 96026_260106-5410 does not have a timestamp
  • trip_id 96068_260106-5410 does not have a timestamp
  • trip_id 96027_260106-5410 does not have a timestamp
  • trip_id 96069_260106-5410 does not have a timestamp

schedule_relationship not populated W009 132 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 96067_260106-5410 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96026_260106-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96068_260106-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96027_260106-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96069_260106-5410 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
W001 Timestamps should be populated for all elements 2,742 28 times (93 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2,742 28 times (93 % 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,137 12 times (40 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 320 11 times (37 % of validations)

GTFS-RT feed content

Entities

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

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