Resource details

File name: Mises à jour des trajets urbain
Format: gtfs-rt

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

Download availability

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

186 errors, 277 warnings

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

Errors

stop_times_updates not strictly sorted E002 1 error

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

Sample errors
  • trip_id 1583190523-20 stop_sequence for stop_ids [1071, 1071, 1764, 1764, 1072, 1072, 1073, 1073, 1074, 1074, 1075, 1075, 1076, 1076, 1077, 1077, 1078, 1078, 1079, 1079, 1080, 1080, 1081, 1081, 1082, 1082, 1083, 1083, 1084, 1084, 1085, 1085, 1086, 1086, 1087, 1087, 1088, 1088, 1752, 1752, 1090, 1090, 1091, 1091, 1092, 1092, 1093, 1093, 1094, 1094, 1095, 1095, 1652, 1652, 1096, 1096, 1540, 1540, 1097, 1097, 2446, 2446] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 5 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 20-1-T104-1-073300-20 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 20-1-T115-1-073701-20 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 20-1-T127-1-071000-20 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 20-1-T131-1-072500-20 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 20-1-T132-1-074100-20 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 68 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 1583010348-20 stop_id 408 arrival_time 08:43:11 (1769672591) is less than previous stop arrival_time 08:43:19 (1769672599) - times must increase between two sequential stops
  • trip_id 1583010348-20 stop_id 408 arrival_time 08:43:11 (1769672591) is less than previous stop departure_time 08:43:19 (1769672599) - times must increase between two sequential stops
  • trip_id 1583010348-20 stop_id 408 departure_time 08:43:11 (1769672591) is less than previous stop departure_time 08:43:19 (1769672599) - times must increase between two sequential stops
  • trip_id 1583010348-20 stop_id 408 departure_time 08:43:11 (1769672591) is less than previous stop arrival_time 08:43:19 (1769672599) - times must increase between two sequential stops
  • trip_id 1583001476-20 stop_id 132 arrival_time 08:25:25 (1769671525) is less than previous stop arrival_time 08:25:28 (1769671528) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 112 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 20-1-T104-1-073300-20 has repeating stop_id 1071 - sequential stop_ids should be different
  • trip_id 20-1-T104-1-073300-20 has repeating stop_id 1764 - sequential stop_ids should be different
  • trip_id 20-1-T104-1-073300-20 has repeating stop_id 1072 - sequential stop_ids should be different
  • trip_id 20-1-T104-1-073300-20 has repeating stop_id 1073 - sequential stop_ids should be different
  • trip_id 20-1-T104-1-073300-20 has repeating stop_id 1074 - sequential stop_ids should be different

Warnings

vehicle_id not populated W002 277 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1583190512-20 does not have a vehicle_id
  • trip_id 1583190364-20 does not have a vehicle_id
  • trip_id 1583190542-20 does not have a vehicle_id
  • trip_id 1583190572-20 does not have a vehicle_id
  • trip_id 1583190573-20 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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 187 4 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 734 4 times (100 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 1 1 times (25 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 5 1 times (25 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 112 1 times (25 % of validations)

GTFS-RT feed content

Entities

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

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