Resource details

File name: BeeMob - Localisation des véhicules en temps réel au format GTFS-RT Vehicle_Position
Format: gtfs-rt

Position en directe des véhicules BeeMob Agglomération Béziers Méditerranée

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

Download availability

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

⚠️33 warnings

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

Warnings

vehicle_id not populated W002 33 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 88 does not have a vehicle_id
  • entity ID 89 does not have a vehicle_id
  • entity ID 102 does not have a vehicle_id
  • entity ID 107 does not have a vehicle_id
  • entity ID 110 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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 917 30 times (100 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 13 10 times (33 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 37 3 times (10 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-09-23 at 01:38 Europe/Paris.

vehicle_positions (1) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-09-23 at 01:38 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "379", "vehicle": { "position": { "bearing": 0.0, "latitude": 43.35709762573242, "longitude": 3.2119269371032715 }, "timestamp": "1790079816", "trip": { "routeId": "8", "scheduleRelationship": "SCHEDULED", "tripId": "51000831" }, "vehicle": { "label": "763" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1790120317" } }