gtfs-rt Transport open dataset - RUBAN - Offre temps-réel au format GTFS-RT (PB) for Réseau urbain Ruban

Resource details

File name: RUBAN - Offre temps-réel au format GTFS-RT (PB)

Format: gtfs-rt

Données temps-réel du réseau RUBAN suivant la structure GTFS-RT au format Protocol Buffers.

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

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

✅No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-21 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.

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 177	26 times (84 % of validations)
E043	If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided	1 133	26 times (84 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	9 029	26 times (84 % 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	1 235	26 times (84 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	276	24 times (77 % 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.	42	11 times (35 % 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.	7	7 times (23 % of validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	9	2 times (6 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

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


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