Resource details

File name: Données en temps réel de la position des véhicules du réseau SNGO
Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules.

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

Download availability

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

⚠️5 warnings

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

Warnings

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 3 min 41 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 4 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:409:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:397:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:403:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:391:LOC 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 92 21 times (70 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 7 7 times (23 % 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. 4 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-10 at 02:47 Europe/Paris.

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

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

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