Resource details
Flux temps réel (horaires) au format GTFS-RT du réseau TeMo’b
This resource file is part of the dataset Réseau urbain TeMo'b.
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
❌2 errors, 175 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-04 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 2 errors
Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.
Sample errors
- trip_id 4536658-25-26-SCO_NS02-L-Ma-J-V-01 stop_sequence 7 departure_time 16:23:00 (1770132180) is less than the same stop arrival_time 16:23:43 (1770132223) - departure time must be equal to or greater than arrival time
- trip_id 4536845-25-26-SCO_NS02-L-Ma-J-V-01-1101100 stop_sequence 8 departure_time 16:29:00 (1770132540) is less than the same stop arrival_time 16:30:52 (1770132652) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 58 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4529897-25-26-SCO_NS02-L-Ma-J-V-01 does not have a vehicle_id
- trip_id 4529931-25-26-SCO_NS02-L-Ma-J-V-01 does not have a vehicle_id
- trip_id 4550591-25-26-SCO_NS02-L-Ma-J-V-01 does not have a vehicle_id
- trip_id 4550592-25-26-SCO_NS02-L-Ma-J-V-01 does not have a vehicle_id
- trip_id 4539325-25-26-SCO_NS02-L-Ma-J-V-01 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 928 min 45 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 116 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 4529897-25-26-SCO_NS02-L-Ma-J-V-01 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 4529897-25-26-SCO_NS02-L-Ma-J-V-01 does not have a schedule_relationship
- trip_id 4529931-25-26-SCO_NS02-L-Ma-J-V-01 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 4529931-25-26-SCO_NS02-L-Ma-J-V-01 does not have a schedule_relationship
- trip_id 4550591-25-26-SCO_NS02-L-Ma-J-V-01 stop_sequence 13 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,455 | 20 times (67 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2,910 | 20 times (67 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 14 | 14 times (47 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 49 | 13 times (43 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-06 at 03:38 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-02-06 at 03:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1770345507"
}
}