gtfs-rt Transport open dataset - Temps réel au format GTFS-RT (trip_update) for Réseau urbain Nemus

Resource details

File name: Temps réel au format GTFS-RT (trip_update)

Format: gtfs-rt

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

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, 3 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 4 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 e84811fc96d8565d843e56e1bd0c230a stop_sequence 9 arrival_time 08:08:11 (1766214491) is equal to previous stop arrival_time 08:08:11 (1766214491) - times must increase between two sequential stops
trip_id e84811fc96d8565d843e56e1bd0c230a stop_sequence 9 arrival_time 08:08:11 (1766214491) is equal to previous stop departure_time 08:08:11 (1766214491) - times must increase between two sequential stops
trip_id e84811fc96d8565d843e56e1bd0c230a stop_sequence 9 departure_time 08:08:11 (1766214491) is equal to previous stop departure_time 08:08:11 (1766214491) - times must increase between two sequential stops
trip_id e84811fc96d8565d843e56e1bd0c230a stop_sequence 9 departure_time 08:08:11 (1766214491) is equal to previous stop arrival_time 08:08:11 (1766214491) - times must increase between two sequential stops

Warnings

timestamp not populated W001 3 errors

Timestamps should be populated for all elements

Sample errors

trip_id 416e85d8d189d101f4e1863cb9cfdd0d does not have a timestamp
trip_id b69a77ddd1881bf8441b11aa87a22989 does not have a timestamp
trip_id e84811fc96d8565d843e56e1bd0c230a 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
W001	Timestamps should be populated for all elements	119	26 times (87 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	60	16 times (53 % 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.	4	4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-21 at 02:56 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-12-21 at 02:56 Europe/Paris. You can look at the GTFS-RT documentation.


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