Resource details

File name: Horaires temps réel des lignes du réseau de la Communauté de Communes des Pays du Sel et du Vermois
Format: gtfs-rt

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

Download availability

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

⚠️6 warnings

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

Warnings

vehicle_id not populated W002 2 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4884444067397632:1 does not have a vehicle_id
  • trip_id 4920967529758720:2 does not have a vehicle_id

schedule_relationship not populated W009 4 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 4884444067397632:1 stop_sequence 20 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 4884444067397632:1 does not have a schedule_relationship
  • trip_id 4920967529758720:2 stop_sequence 17 (and potentially more for this trip) 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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 57 23 times (77 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 114 23 times (77 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 13 13 times (43 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-23 at 02:12 Europe/Paris.

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

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

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 2026-01-23 at 02:12 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1769130769" } }