Resource details
File name:
Données gobales en temps réel du réseau MOCA
Format: gtfs-rt
GTFS-RT (protobuff) global, regroupant les horaires aux arrêts, la position des véhicules et les perturbations.
This resource file is part of the dataset Réseau urbain MOCA.
Download availability
2026-01-23
99.5%
2026-01-24
99.5%
2026-01-25
98.3%
2026-01-26
98.2%
2026-01-27
99%
2026-01-28
97.5%
2026-01-29
99.4%
2026-01-30
98.8%
2026-01-31
99%
2026-02-01
99.4%
2026-02-02
98.9%
2026-02-03
98.1%
2026-02-04
98.2%
2026-02-05
99.5%
2026-02-06
98.9%
2026-02-07
99.3%
2026-02-08
99.3%
2026-02-09
99.3%
2026-02-10
100%
2026-02-11
100%
2026-02-12
99.2%
2026-02-13
100%
2026-02-14
100%
2026-02-15
100%
2026-02-16
100%
2026-02-17
100%
2026-02-18
99.4%
2026-02-19
99.5%
2026-02-20
99.5%
2026-02-21
99.3%
2026-02-22
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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-02-22 at 08:01 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 158 | 22 times (76 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 158 | 22 times (76 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,557 | 22 times (76 % 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 | 78 | 21 times (72 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 21 | 17 times (59 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8 | 8 times (28 % 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 | 26 | 4 times (14 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-22 at 09:52 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-02-22 at 09:52 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771750352"
}
}