Resource details

File name: Temps réel GTFS-RT TripUpdate
Format: gtfs-rt

Horaires de prochains passages aux arrêts

This resource file is part of the dataset Réseau urbain Mistral.

Download availability

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

250 errors, 73 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-02 at 08:01 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 2 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 9525 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 9526 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 2 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 0095 does not exist in the GTFS data routes.txt
  • route_id 0095 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 8 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id 9525 stop_id SEBRG2 does not exist in GTFS data stops.txt
  • trip_id 9525 stop_id SEBRG3 does not exist in GTFS data stops.txt
  • trip_id 9525 stop_id SEBRG4 does not exist in GTFS data stops.txt
  • trip_id 9525 stop_id SEBRG5 does not exist in GTFS data stops.txt
  • trip_id 9526 stop_id SEBRG2 does not exist in GTFS data stops.txt

Header timestamp should be greater than or equal to all other timestamps E012 66 errors

No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp

Sample errors
  • trip_id 5456407 timestamp 1762067148 is greater than the header
  • trip_id 5456399 timestamp 1762067148 is greater than the header
  • trip_id 5456410 timestamp 1762066948 is greater than the header
  • trip_id 5456409 timestamp 1762067158 is greater than the header
  • trip_id 5456408 timestamp 1762067138 is greater than the header

Sequential stop_time_update times are not increasing E022 114 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 5456407 stop_id TOPASS arrival_time 08:00:40 (1762066840) is equal to previous stop departure_time 08:00:40 (1762066840) - times must increase between two sequential stops
  • trip_id 5456407 stop_id TOPASS departure_time 08:00:40 (1762066840) is equal to previous stop departure_time 08:00:40 (1762066840) - times must increase between two sequential stops
  • trip_id 5456407 stop_id TOBNRS arrival_time 08:04:15 (1762067055) is less than previous stop arrival_time 08:04:22 (1762067062) - times must increase between two sequential stops
  • trip_id 5456407 stop_id TOBNRS arrival_time 08:04:15 (1762067055) is less than previous stop departure_time 08:04:22 (1762067062) - times must increase between two sequential stops
  • trip_id 5456407 stop_id TOBNRS departure_time 08:04:15 (1762067055) is less than previous stop departure_time 08:04:22 (1762067062) - times must increase between two sequential stops

timestamp is in the future E050 58 errors

All timestamps must be less than the current time

Sample errors
  • trip_id 5456407 timestamp 08:05:48 (1762067148) is 4 min 38 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
  • trip_id 5456399 timestamp 08:05:48 (1762067148) is 4 min 38 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
  • trip_id 5456410 timestamp 08:02:28 (1762066948) is 1 min 18 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
  • trip_id 5456409 timestamp 08:05:58 (1762067158) is 4 min 48 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
  • trip_id 5456408 timestamp 08:05:38 (1762067138) is 4 min 28 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds

Warnings

vehicle_id not populated W002 72 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5456399 does not have a vehicle_id
  • trip_id 5456393 does not have a vehicle_id
  • trip_id 5456404 does not have a vehicle_id
  • trip_id 5456406 does not have a vehicle_id
  • trip_id 5456396 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 1 min 23 sec old which is greater than the recommended age of 65 seconds
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
E012 No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp 7 355 30 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 9 477 30 times (100 % of validations)
E050 All timestamps must be less than the current time 6 775 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 6 329 30 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 30 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 77 28 times (93 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 77 28 times (93 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 80 28 times (93 % 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. 31 18 times (60 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 39 12 times (40 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 1 528 12 times (40 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-03 at 00:53 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-11-03 at 00:53 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "5459857", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": 0, "time": "1762126800" }, "departure": { "delay": 0, "time": "1762126800" }, "stopId": "SMPSMS" }, { "arrival": { "delay": 0, "time": "1762126920" }, "departure": { "delay": 0, "time": "1762126920" }, "stopId": "SMPPRO" }, { "departure": { "delay": 0, "time": "1762128120" }, "stopId": "TOPTOS" } ], "timestamp": "1762127111", "trip": { "directionId": 1, "routeId": "28M", "scheduleRelationship": "SCHEDULED", "tripId": "5459857" }, "vehicle": {} } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1762127594" } }