Resource details

File name: GTFS-RT Trip-updates moova
Format: gtfs-rt

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

Download availability

2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
94.1%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
94.1%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
93.8%
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
93.8%
2026-03-23
100%
2026-03-24
100%
2026-03-25
100%
2026-03-26
100%
2026-03-27
100%
2026-03-28
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

23 errors, 23 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-26 at 09:34 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 23 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 1100409051 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1100409252 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1100109351 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1100109352 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1100209351 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 23 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1100409051 does not have a vehicle_id
  • trip_id 1100409252 does not have a vehicle_id
  • trip_id 1100109351 does not have a vehicle_id
  • trip_id 1100109352 does not have a vehicle_id
  • trip_id 1100209351 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 640 26 times (87 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 640 26 times (87 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 4 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-28 at 05:56 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-03-28 at 05:56 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1774673766" } }