Resource details

File name: Horaires temps-réel du réseau Ritmo - Haguenau (GTFS-RT)
Format: gtfs-rt

Les spécifications du format GTFS-RT sont disponibles ici : https://developers.google.com/transit/gtfs-realtime/

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

Download availability

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

78 errors, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-04 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 77 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 5359235979280384:7 stop_sequence 23 arrival_time 08:13:46 (1770189226) is less than previous stop departure_time 08:15:00 (1770189300) - times must increase between two sequential stops
  • trip_id 5359235979280384:7 stop_sequence 23 departure_time 08:14:58 (1770189298) is less than previous stop departure_time 08:15:00 (1770189300) - times must increase between two sequential stops
  • trip_id 5359235979280384:7 stop_sequence 24 arrival_time 08:14:32 (1770189272) is less than previous stop departure_time 08:14:58 (1770189298) - times must increase between two sequential stops
  • trip_id 5359235979280384:7 stop_sequence 25 arrival_time 08:15:18 (1770189318) is less than previous stop departure_time 08:15:51 (1770189351) - times must increase between two sequential stops
  • trip_id 5359235979280384:7 stop_sequence 26 arrival_time 08:16:05 (1770189365) is less than previous stop departure_time 08:16:44 (1770189404) - times must increase between two sequential stops

Vehicle position far from trip shape E029 1 error

The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.

Sample errors
  • vehicle.id zenbus:Vehicle:709630001:LOC trip_id 5988828524314624:4 at (48.70783,7.709779) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 6542731733106688:2 does not have a vehicle_id

ID in one feed missing from the other W003 1 error

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 6542731733106688:2 is in TripUpdates but not in VehiclePositions feed
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 25 15 times (52 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 25 15 times (52 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 13 12 times (41 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 83 6 times (21 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-06 at 04:04 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-02-06 at 04:04 Europe/Paris. You can look at the GTFS-RT documentation.

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