Resource details

File name: Tisseo_GTFSRT.pb
Format: gtfs-rt

Fichier GTFS-RT

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

Download availability

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

208 errors, 3,228 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-12 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 51 errors

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

Sample errors
  • trip_id 2216775 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
  • trip_id 2216767 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
  • trip_id 2216302 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
  • trip_id 2216893 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
  • trip_id 2191982 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 4 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 2216766 stop_sequence 5 arrival_time 08:14:39 (1770880479) is less than previous stop arrival_time 08:15:08 (1770880508) - times must increase between two sequential stops
  • trip_id 2216766 stop_sequence 5 arrival_time 08:14:39 (1770880479) is less than previous stop departure_time 08:15:08 (1770880508) - times must increase between two sequential stops
  • trip_id 2216766 stop_sequence 5 departure_time 08:14:39 (1770880479) is less than previous stop departure_time 08:15:08 (1770880508) - times must increase between two sequential stops
  • trip_id 2216766 stop_sequence 5 departure_time 08:14:39 (1770880479) is less than previous stop arrival_time 08:15:08 (1770880508) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 51 errors

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors
  • trip_id 2216775 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
  • trip_id 2216767 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
  • trip_id 2216302 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
  • trip_id 2216893 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
  • trip_id 2191982 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 51 errors

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

Sample errors
  • trip_id 2216775 has repeating stop_id stop_point:SP_4437 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 2216767 has repeating stop_id stop_point:SP_4437 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 2216302 has repeating stop_id stop_point:SP_3112 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 2216893 has repeating stop_id stop_point:SP_1679 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 2191982 has repeating stop_id stop_point:SP_1820 at stop_sequence 2 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 51 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors
  • GTFS-rt trip_id 2216775 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 2216767 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 2216302 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 2216893 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 2191982 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 41 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id new_8530 does not have a vehicle_id
  • trip_id new_8529 does not have a vehicle_id
  • trip_id new_8524 does not have a vehicle_id
  • trip_id new_8532 does not have a vehicle_id
  • trip_id new_6347 does not have a vehicle_id

schedule_relationship not populated W009 3,187 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 2151952 does not have a schedule_relationship
  • trip_id 2151953 does not have a schedule_relationship
  • trip_id 2151941 does not have a schedule_relationship
  • trip_id 2151920 does not have a schedule_relationship
  • trip_id 2151921 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
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 696 29 times (100 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 745 29 times (100 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 690 29 times (100 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 689 29 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 4,362 29 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 77,684 29 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 148 7 times (24 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.