Resource details
This resource file is part of the dataset Réseau urbain SITAC.
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-22 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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. | 2,001 | 14 times (78 % 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. | 127 | 11 times (61 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 20 | 10 times (56 % 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 | 20 | 10 times (56 % 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 | 334 | 5 times (28 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 189 | 5 times (28 % of validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 306 | 5 times (28 % 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,745 | 5 times (28 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 62 | 5 times (28 % of validations) |
| E034 | All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt | 1 | 1 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-11-22 at 22:34 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-11-22 at 22:34 Europe/Paris.
Unknown effect
From 2022-03-02 at 04:00 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-11-22 at 22:34 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"start": "1646190000"
}
],
"cause": "OTHER_CAUSE",
"descriptionText": {
"translation": [
{
"language": "fr",
"text": "VOTRE AVIS NOUS INTÉRESSE ✨\r\nVous aimez l’application ? 💌 \r\nN’hésitez pas à nous le dire en laissant votre avis sur App Store https://apps.apple.com/fr/app/zenbus/id808231328 ou Google Play https://play.google.com/store/apps/details?id=com.byjoul.code.zenbus.android&gl=FR ! \r\nCe sont vos bons et nombreux avis qui nous aide à nous déployer sur davantage de lignes ! 😉\r\nBon voyage avec Zenbus 🚌"
}
]
},
"headerText": {
"translation": [
{
"language": "fr",
"text": "Evénement"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "5727348410286080"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1795383260"
}
}