Resource details
fichier GTFS-RT
This resource file is part of the dataset Réseau urbain T2C.
Download availability
Learn more
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
❌314 errors, 1,273 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-30 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 314 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 1475_1000003_12_3_075100 stop_sequence 48 arrival_time 09:05:26 (1777532726) is less than previous stop arrival_time 09:05:34 (1777532734) - times must increase between two sequential stops
- trip_id 1475_1000003_12_3_075100 stop_sequence 48 arrival_time 09:05:26 (1777532726) is less than previous stop departure_time 09:05:34 (1777532734) - times must increase between two sequential stops
- trip_id 1475_1000003_12_3_075100 stop_sequence 48 departure_time 09:05:26 (1777532726) is less than previous stop departure_time 09:05:34 (1777532734) - times must increase between two sequential stops
- trip_id 1475_1000003_12_3_075100 stop_sequence 48 departure_time 09:05:26 (1777532726) is less than previous stop arrival_time 09:05:34 (1777532734) - times must increase between two sequential stops
- trip_id 1475_1000003_12_2_075900 stop_sequence 6 arrival_time 08:03:53 (1777529033) is equal to previous stop departure_time 08:03:53 (1777529033) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 1,273 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1490_1000003_C_3_072200 does not have a vehicle_id
- trip_id 1475_1000003_03GC.AR_073900 does not have a vehicle_id
- trip_id 1475_1000003_12_3_075100 does not have a vehicle_id
- trip_id 1475_1000003_03GC.AR_075100 does not have a vehicle_id
- trip_id 1475_1000003_12_2_075900 does not have a vehicle_id
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. | 9,327 | 29 times (97 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 30,960 | 29 times (97 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 13,395 | 17 times (57 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 97 | 3 times (10 % 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 | 12 | 2 times (7 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 19 | 1 times (3 % of validations) |
| E016 | Trips that have a schedule_relationship of ADDED must not be included in the GTFS data | 93 | 1 times (3 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 1 | 1 times (3 % of validations) |
| FATAL | The validator could not run. Please provide a valid GTFS and a valid GTFS-RT feed. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-05-01 at 03:29 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-05-01 at 03:29 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1777598983"
}
}