Resource details

File name: https://app.mecatran.com/utw/ws/gtfsfeed/realtime/blois?apiKey=7a0d1031460836674e76041e7a78011813347
Format: gtfs-rt
Size: 36.59 KB

GTFS-RT

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

Download availability

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

9 errors, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-28 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt route_id does not exist in GTFS data E004 9 errors

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

Sample errors
  • route_id B_558 does not exist in the GTFS data routes.txt
  • route_id B_558 does not exist in the GTFS data routes.txt
  • route_id A_569 does not exist in the GTFS data routes.txt
  • route_id A_569 does not exist in the GTFS data routes.txt
  • route_id D_561 does not exist in the GTFS data routes.txt

Warnings

vehicle_id not populated W002 9 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 131386{B_558}-2025_09_PS_PP_001_DF does not have a vehicle_id
  • trip_id 131402{B_558}-2025_09_PS_PP_001_DF does not have a vehicle_id
  • trip_id 130905{A_569}-2025_09_PS_PP_001_DF does not have a vehicle_id
  • trip_id 130892{A_569}-2025_09_PS_PP_001_DF does not have a vehicle_id
  • trip_id 131535{D_561}-2025_09_PS_PP_001_DF 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
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 221 6 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 211 6 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 2 1 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-28 at 21:21 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 2025-09-28 at 21:21 Europe/Paris. You can look at the GTFS-RT documentation.

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