gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau ELSA for Réseau urbain ELSA

Resource details

File name: Horaires temps réel des lignes du réseau ELSA

Format: gtfs-rt

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

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

❌4 errors, 42 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-04 at 09:05 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 4 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 JT_V_K110-0839 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id JT_V_K111-0912 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id JT_V_K110-0914 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id JT_V_K111-0834 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 14 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id JT_V_K102-0908 does not have a vehicle_id
trip_id JT_V_K107-0838 does not have a vehicle_id
trip_id JT_V_K104-0907 does not have a vehicle_id
trip_id JT_V_K108-0837 does not have a vehicle_id
trip_id JT_V_K110-0839 does not have a vehicle_id

schedule_relationship not populated W009 28 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id JT_V_K102-0908 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id JT_V_K102-0908 does not have a schedule_relationship
trip_id JT_V_K107-0838 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
trip_id JT_V_K107-0838 does not have a schedule_relationship
trip_id JT_V_K104-0907 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	328	25 times (83 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	654	25 times (83 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	12	3 times (10 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	2	2 times (7 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

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


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