Resource details
Les 2 types de données sont mises à disposition dans ce flux de données temps réel.
Pour l’instant les données sont diffusées en GTFS-RT et en Siri lorsque le flux sera disponible.
This resource file is part of the dataset Réseau urbain Citibus.
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
❌233 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-30 at 09:19 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 132 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 6001604 stop_sequence 36 arrival_time 09:30:00 (1790753400) is equal to previous stop arrival_time 09:30:00 (1790753400) - times must increase between two sequential stops
- trip_id 6001604 stop_sequence 36 arrival_time 09:30:00 (1790753400) is equal to previous stop departure_time 09:30:00 (1790753400) - times must increase between two sequential stops
- trip_id 6001604 stop_sequence 36 departure_time 09:30:00 (1790753400) is equal to previous stop departure_time 09:30:00 (1790753400) - times must increase between two sequential stops
- trip_id 6001604 stop_sequence 36 departure_time 09:30:00 (1790753400) is equal to previous stop arrival_time 09:30:00 (1790753400) - times must increase between two sequential stops
- trip_id 6001091 stop_sequence 33 arrival_time 09:20:14 (1790752814) is equal to previous stop arrival_time 09:20:14 (1790752814) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 101 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 6001424 stop_sequence 32 has stop_id _2679 but GTFS stop_sequence 32 has stop_id _3079 - stop_ids should be the same
- GTFS-rt trip_id 6001424 stop_sequence 33 has stop_id _3079 but GTFS stop_sequence 33 has stop_id _3080 - stop_ids should be the same
- GTFS-rt trip_id 6001424 stop_sequence 34 has stop_id _3080 but GTFS stop_sequence 34 has stop_id _3139 - stop_ids should be the same
- GTFS-rt trip_id 6001424 stop_sequence 35 has stop_id _3139 but GTFS stop_sequence 35 has stop_id _2834 - stop_ids should be the same
- GTFS-rt trip_id 6001424 stop_sequence 36 has stop_id _2834 but GTFS stop_sequence 36 has stop_id _3000 - stop_ids should be the same
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 6000485 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 6000485 is in TripUpdates but not in VehiclePositions feed
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. | 1,759 | 30 times (100 % 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 | 121 | 28 times (93 % 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 | 1,629 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 63 | 25 times (83 % 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. | 83 | 18 times (60 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 467 | 15 times (50 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 93 | 12 times (40 % of validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 183 | 12 times (40 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 48 | 12 times (40 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 89 | 10 times (33 % of validations) |
| E044 | stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing | 1 | 1 times (3 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-10-01 at 04:04 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-10-01 at 04:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1790820268"
}
}