gtfs-rt Transport open dataset - GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt for Réseau urbain Marinéo

Resource details

File name: GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt

Format: gtfs-rt

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

Download availability

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

❌68 errors, 42 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-24 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 1 error

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 21323855 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 1 error

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

Sample errors

route_id SC does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id 21725824 stop_id outmds does not exist in GTFS data stops.txt
trip_id 21725826 stop_id outmds does not exist in GTFS data stops.txt
trip_id 21323855 stop_id smbsand does not exist in GTFS data stops.txt
trip_id 21725990 stop_id wimmair4 does not exist in GTFS data stops.txt
trip_id 21725991 stop_id wimmair3 does not exist in GTFS data stops.txt

stop_times_updates not strictly sorted E002 2 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id 21725825 stop_sequence [7, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
trip_id 21725823 stop_sequence [7, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 40 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 21725824 stop_sequence 1 departure_time 08:01:02 (1774335662) is less than previous stop departure_time 08:17:03 (1774336623) - times must increase between two sequential stops
trip_id 21725824 stop_sequence 1 departure_time 08:01:02 (1774335662) is less than previous stop arrival_time 08:17:03 (1774336623) - times must increase between two sequential stops
trip_id 21725824 stop_sequence 2 arrival_time 08:02:37 (1774335757) is less than previous stop arrival_time 08:17:03 (1774336623) - times must increase between two sequential stops
trip_id 21725824 stop_sequence 2 departure_time 08:02:37 (1774335757) is less than previous stop arrival_time 08:17:03 (1774336623) - times must increase between two sequential stops
trip_id 21725824 stop_sequence 16 arrival_time 08:17:42 (1774336662) is less than previous stop arrival_time 08:18:11 (1774336691) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 14 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 21725937 stop_sequence 6 has stop_id smbecol but GTFS stop_sequence 6 has stop_id smbecol3 - stop_ids should be the same
GTFS-rt trip_id 21725926 stop_sequence 13 has stop_id smbecol but GTFS stop_sequence 13 has stop_id smbecol3 - stop_ids should be the same
GTFS-rt trip_id 21725929 stop_sequence 4 has stop_id smbecol but GTFS stop_sequence 4 has stop_id smbecol3 - stop_ids should be the same
GTFS-rt trip_id 21725990 stop_sequence 25 has stop_id wimmair4 but GTFS stop_sequence 25 has stop_id wimmair2 - stop_ids should be the same
GTFS-rt trip_id 21725991 stop_sequence 11 has stop_id wimmair3 but GTFS stop_sequence 11 has stop_id wimmair - stop_ids should be the same

Warnings

vehicle_id not populated W002 42 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 21323825 does not have a vehicle_id
trip_id 21725825 does not have a vehicle_id
trip_id 21725826 does not have a vehicle_id
trip_id 21725936 does not have a vehicle_id
trip_id 21725937 does not have a vehicle_id

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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	263	30 times (100 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	377	30 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1,077	30 times (100 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	48	26 times (87 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1,004	26 times (87 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	11	11 times (37 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	11	11 times (37 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-25 at 04:14 Europe/Paris.

trip_updates (2) 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 2026-03-25 at 04:14 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "21323602",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "departure": {
              "time": "1774411200",
              "uncertainty": 120
            },
            "stopId": "bsmcca7",
            "stopSequence": 1
          }
        ],
        "timestamp": "1774408451",
        "trip": {
          "directionId": 1,
          "routeId": "B2",
          "scheduleRelationship": "SCHEDULED",
          "tripId": "21323602"
        }
      }
    },
    {
      "id": "21725915",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "departure": {
              "time": "1774411800",
              "uncertainty": 120
            },
            "stopId": "lpoalpr2",
            "stopSequence": 1
          }
        ],
        "timestamp": "1774408451",
        "trip": {
          "directionId": 0,
          "routeId": "C",
          "scheduleRelationship": "SCHEDULED",
          "tripId": "21725915"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1774408451"
  }
}