Resource details

File name: Position des véhicules en temps réel
Format: gtfs-rt

This resource file is part of the dataset Navette de la CC Sel et Vermois.

Download availability

2026-02-09
85.3%
2026-02-10
84.7%
2026-02-11
95.6%
2026-02-12
92.1%
2026-02-13
74.7%
2026-02-14
69.3%
2026-02-15
58.4%
2026-02-16
74.8%
2026-02-17
74.6%
2026-02-18
82.7%
2026-02-19
95.2%
2026-02-20
95.7%
2026-02-21
97.6%
2026-02-22
67.8%
2026-02-23
74.8%
2026-02-24
84%
2026-02-28
87.2%
2026-03-01
54.4%
2026-03-02
74.9%
2026-03-03
84.7%
2026-03-04
78.4%
2026-03-05
83.7%
2026-03-06
99.7%
2026-03-07
87.9%
2026-03-08
60%
2026-03-09
74.7%
2026-03-10
82.6%
2026-02-26
100%
2026-02-27
100%
2026-03-11
100%
2026-02-25
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

⚠️3 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-10 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

schedule_relationship not populated W009 3 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 4884444067397632:1 does not have a schedule_relationship
  • trip_id 4920967529758720:1 does not have a schedule_relationship
  • trip_id 4920967529758720:2 does not have a schedule_relationship
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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 60 26 times (84 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 16 16 times (52 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 4 4 times (13 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-10 at 17:30 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 49,332 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-10 at 17:30 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "VM:4920967529758720:11", "vehicle": { "currentStopSequence": 23, "position": { "latitude": 48.63652038574219, "longitude": 6.312290191650391 }, "stopId": "poi1040039", "timestamp": "1773160150", "trip": { "directionId": 1, "routeId": "zenbus:Line:287440019:LOC", "tripId": "4920967529758720:11" }, "vehicle": { "id": "zenbus:Vehicle:6001708208488448:LOC" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1773160220" } }