Resource details
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éseaux urbain MOCA.
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
❌153 errors, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-20 at 09:02 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 8 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 67d29b626045b634aa4efebd trip_id 9 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0631d4a897eb633c trip_id 10 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 10 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 8 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 67d29b626045b634aa4efebd route_id 1 does not exist in the GTFS data routes.txt
- vehicle_id 0631d4a897eb633c route_id 2 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 126 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 67d29b626045b634aa4efebd stop_id 30042 does not exist in GTFS data stops.txt
- vehicle_id 0631d4a897eb633c stop_id 30028 does not exist in GTFS data stops.txt
- trip_id 3 stop_id 30028 does not exist in GTFS data stops.txt
- trip_id 3 stop_id 30024 does not exist in GTFS data stops.txt
- trip_id 3 stop_id 30001 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 5 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 5 stop_sequence 23 arrival_time 08:32:26 (1760941946) is less than previous stop arrival_time 08:33:08 (1760941988) - times must increase between two sequential stops
- trip_id 5 stop_sequence 23 departure_time 08:26:00 (1760941560) is less than previous stop arrival_time 08:33:08 (1760941988) - times must increase between two sequential stops
- trip_id 5 stop_sequence 24 arrival_time 08:25:28 (1760941528) is less than previous stop arrival_time 08:32:26 (1760941946) - times must increase between two sequential stops
- trip_id 5 stop_sequence 24 arrival_time 08:25:28 (1760941528) is less than previous stop departure_time 08:26:00 (1760941560) - times must increase between two sequential stops
- trip_id 5 stop_sequence 24 departure_time 08:27:00 (1760941620) is less than previous stop arrival_time 08:32:26 (1760941946) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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.
Sample errors
- trip_id 5 stop_sequence 22 departure_time 08:25:00 (1760941500) is less than the same stop arrival_time 08:33:08 (1760941988) - departure time must be equal to or greater than arrival time
- trip_id 5 stop_sequence 23 departure_time 08:26:00 (1760941560) is less than the same stop arrival_time 08:32:26 (1760941946) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 3 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 7 stop_sequence 0 doesn't have arrival or departure
- trip_id 7 stop_sequence 1 doesn't have arrival or departure
- trip_id 7 stop_sequence 2 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 9 and vehicle_id 67d29b626045b634aa4efebd pairing in VehiclePositions does not match trip_id 7 and vehicle_id 67d29b626045b634aa4efebd pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 4 errors
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 1 is in TripUpdates but not in VehiclePositions feed
- trip_id 3 is in TripUpdates but not in VehiclePositions feed
- trip_id 5 is in TripUpdates but not in VehiclePositions feed
- trip_id 7 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 207 | 26 times (84 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 207 | 26 times (84 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 037 | 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 | 105 | 25 times (81 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 20 | 20 times (65 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 23 | 6 times (19 % 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 | 11 | 5 times (16 % 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. | 4 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-10-20 at 10:54 Europe/Paris.
vehicle_positions (1) trip_updates (1) service_alerts (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 2025-10-20 at 10:54 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "vehicle:0631d4a897eb633c",
"vehicle": {
"currentStatus": "STOPPED_AT",
"currentStopSequence": 8,
"position": {
"latitude": 49.54246520996094,
"longitude": 0.9548389911651611
},
"stopId": "30013",
"timestamp": "1760950459",
"trip": {
"routeId": "2",
"scheduleRelationship": "SCHEDULED",
"tripId": "16"
},
"vehicle": {
"id": "0631d4a897eb633c"
}
}
},
{
"id": "trip:16",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1760948382"
},
"departure": {
"time": "1760950022"
},
"stopId": "30049",
"stopSequence": 0
},
{
"arrival": {
"time": "1760950090"
},
"departure": {
"time": "1760950107"
},
"stopId": "30046",
"stopSequence": 1
},
{
"arrival": {
"time": "1760950144"
},
"departure": {
"time": "1760950151"
},
"stopId": "30048",
"stopSequence": 2
},
{
"arrival": {
"time": "1760950212"
},
"departure": {
"time": "1760950221"
},
"stopId": "30023",
"stopSequence": 3
},
{
"arrival": {
"time": "1760950252"
},
"departure": {
"time": "1760950263"
},
"stopId": "30050",
"stopSequence": 4
},
{
"arrival": {
"time": "1760950281"
},
"departure": {
"time": "1760950293"
},
"stopId": "30021",
"stopSequence": 5
},
{
"arrival": {
"time": "1760950320"
},
"departure": {
"time": "1760950379"
},
"stopId": "30007",
"stopSequence": 6
},
{
"arrival": {
"time": "1760950406"
},
"departure": {
"time": "1760950420"
},
"stopId": "30019",
"stopSequence": 7
},
{
"arrival": {
"time": "1760950454"
},
"departure": {
"time": "1760950460"
},
"stopId": "30013",
"stopSequence": 8
},
{
"arrival": {
"time": "1760950520"
},
"departure": {
"time": "1760950520"
},
"stopId": "30017",
"stopSequence": 9
},
{
"arrival": {
"time": "1760950580"
},
"departure": {
"time": "1760950580"
},
"stopId": "30002",
"stopSequence": 10
},
{
"arrival": {
"time": "1760950700"
},
"departure": {
"time": "1760950700"
},
"stopId": "30025",
"stopSequence": 11
},
{
"arrival": {
"time": "1760950760"
},
"departure": {
"time": "1760950760"
},
"stopId": "30003",
"stopSequence": 12
},
{
"arrival": {
"time": "1760950820"
},
"departure": {
"time": "1760950820"
},
"stopId": "30028",
"stopSequence": 13
}
],
"timestamp": "1760950459",
"trip": {
"routeId": "2",
"scheduleRelationship": "SCHEDULED",
"tripId": "16"
},
"vehicle": {
"id": "0631d4a897eb633c"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1760950463"
}
}