Resource details

File name: Citibus - Horaires de prochains passages et géolocalisation en temps réel au format GTFS-RT Trip_Update et VehiclePosition
Format: gtfs-rt

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

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

40 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-05-02 at 09:09 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 40 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 500000661 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 500000326 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 500000297 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 500000293 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 500000503 does not exist in the GTFS data and does not have schedule_relationship of ADDED
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 958 29 times (97 % 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 43 21 times (70 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 20 11 times (37 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-05-02 at 23:06 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-05-02 at 23:06 Europe/Paris. You can look at the GTFS-RT documentation.

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