Resource details
Horaires temps-réel du réseau Envia
This resource file is part of the dataset Réseau urbain Envia.
Download availability
Learn more
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
❌194 errors, 32 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-05 at 08:10 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 3 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 1-594739201-A50_5-LM_JV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-1006698507 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-857866253 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 2 errors
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
- route_id 51 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 186 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-671154181 stop_sequence 19 arrival_time 08:10:14 (1764918614) is equal to previous stop departure_time 08:10:14 (1764918614) - times must increase between two sequential stops
- trip_id 1-671154181 stop_sequence 19 departure_time 08:10:14 (1764918614) is equal to previous stop departure_time 08:10:14 (1764918614) - times must increase between two sequential stops
- trip_id 1-671154181 stop_sequence 22 arrival_time 08:13:14 (1764918794) is equal to previous stop arrival_time 08:13:14 (1764918794) - times must increase between two sequential stops
- trip_id 1-671154181 stop_sequence 22 arrival_time 08:13:14 (1764918794) is equal to previous stop departure_time 08:13:14 (1764918794) - times must increase between two sequential stops
- trip_id 1-671154181 stop_sequence 22 departure_time 08:13:14 (1764918794) is equal to previous stop departure_time 08:13:14 (1764918794) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 1-561840138 stop_sequence 16 departure_time 08:08:53 (1764918533) is less than the same stop arrival_time 08:09:52 (1764918592) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_id E037 2 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 1-1006698507 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different
- trip_id 1-857866253 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
Warnings
timestamp not populated W001 32 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-719650817 does not have a timestamp
- trip_id 1-671285253 does not have a timestamp
- trip_id 1-594739201-A50_5-LM_JV__ does not have a timestamp
- trip_id 1-1275199491 does not have a timestamp
- trip_id 1-570687489 does not have a timestamp
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 646 | 30 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 725 | 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 | 72 | 25 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 43 | 25 times (83 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 43 | 25 times (83 % 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. | 36 | 21 times (70 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-05 at 23:44 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-05 at 23:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764974689"
}
}