Resource details

File name: Horaires temps-réel du réseau
Format: gtfs-rt

Horaires temps-réel du réseau Envia

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

Download availability

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

143 errors, 16 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-22 at 08:03 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 1 error

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 1-1006698509 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 1 error

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 60 does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 140 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 1-674955269 stop_sequence 22 arrival_time 08:05:22 (1763795122) is equal to previous stop arrival_time 08:05:22 (1763795122) - times must increase between two sequential stops
  • trip_id 1-674955269 stop_sequence 22 arrival_time 08:05:22 (1763795122) is equal to previous stop departure_time 08:05:22 (1763795122) - times must increase between two sequential stops
  • trip_id 1-674955269 stop_sequence 22 departure_time 08:05:22 (1763795122) is equal to previous stop departure_time 08:05:22 (1763795122) - times must increase between two sequential stops
  • trip_id 1-674955269 stop_sequence 22 departure_time 08:05:22 (1763795122) is equal to previous stop arrival_time 08:05:22 (1763795122) - times must increase between two sequential stops
  • trip_id 1-589561857 stop_sequence 12 arrival_time 08:06:58 (1763795218) is equal to previous stop arrival_time 08:06:58 (1763795218) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 1 error

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 1-1006698509 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different

Warnings

timestamp not populated W001 16 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-1006698509 does not have a timestamp
  • trip_id 1-719650853 does not have a timestamp
  • trip_id 1-674889732 does not have a timestamp
  • trip_id 1-638517252 does not have a timestamp
  • trip_id 1-674955269 does not have a timestamp
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 674 30 times (100 % of validations)
W001 Timestamps should be populated for all elements 648 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 58 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 41 24 times (80 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 41 24 times (80 % 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. 24 14 times (47 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-23 at 06:57 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 2025-11-23 at 06:57 Europe/Paris. You can look at the GTFS-RT documentation.

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