transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: Données en temps réel des horaires aux arrêts du réseau SNGO
Format: gtfs-rt
Download

Données en temps réel au format GTFS-RT (protobuf) du réseau de transport de Seine Normandie Agglomération.

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

Download availability

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

❌26 errors, 21 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-09 at 09: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 7 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 ATOUMOD007:ServiceJourney:615:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD007:ServiceJourney:633:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD007:ServiceJourney:627:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD007:ServiceJourney:609:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD007:ServiceJourney:639:LOC 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 7 errors

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

Sample errors
  • route_id ATOUMOD007:Line:23:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD007:Line:24:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD007:Line:25:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD007:Line:26:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD007:Line:31:LOC does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:615:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD007:ServiceJourney:633:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD007:ServiceJourney:627:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD007:ServiceJourney:609:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD007:ServiceJourney:639:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 1 error

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:701:LOC stop_sequence 13 departure_time 09:43:00 (1775720580) is less than previous stop arrival_time 09:45:00 (1775720700) - 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 ATOUMOD007:ServiceJourney:701:LOC stop_sequence 12 departure_time 09:42:00 (1775720520) is less than the same stop arrival_time 09:45:00 (1775720700) - departure time must be equal to or greater than arrival time
  • trip_id ATOUMOD007:ServiceJourney:701:LOC stop_sequence 13 departure_time 09:43:00 (1775720580) is less than the same stop arrival_time 09:46:00 (1775720760) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:615:LOC does not have a vehicle_id
  • trip_id ATOUMOD007:ServiceJourney:633:LOC does not have a vehicle_id
  • trip_id ATOUMOD007:ServiceJourney:627:LOC does not have a vehicle_id
  • trip_id ATOUMOD007:ServiceJourney:609:LOC does not have a vehicle_id
  • trip_id ATOUMOD007:ServiceJourney:639:LOC does not have a vehicle_id

schedule_relationship not populated W009 14 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:615:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:615:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:633:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:633:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:627:LOC stop_sequence 1 (and potentially more for this trip) 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 647 25 times (83 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 647 25 times (83 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 7,799 25 times (83 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 647 25 times (83 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1,294 25 times (83 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 7 7 times (23 % 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. 14 7 times (23 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-10 at 00:57 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 2026-04-10 at 00:57 Europe/Paris. You can look at the GTFS-RT documentation.

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