Resource details

File name: GTFS-RT MATAWAN POSITION
Format: gtfs-rt

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

Download availability

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

1 error

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 160 trip_id 5-522452993-501-______D does not exist in the GTFS data and does not have schedule_relationship of ADDED
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 74 29 times (97 % of validations)
W001 Timestamps should be populated for all elements 77 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 38 23 times (77 % 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. 6 6 times (20 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-07-26 at 22:00 Europe/Paris.

vehicle_positions (2) 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-07-26 at 22:00 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "1124058", "vehicle": { "currentStopSequence": 1, "stopId": "371", "trip": { "directionId": 0, "routeId": "39", "scheduleRelationship": "SCHEDULED", "startDate": "20260726", "startTime": "22:00:00", "tripId": "5-654442502" }, "vehicle": { "id": "69", "label": "108252", "licensePlate": "FY-134-KK" } } }, { "id": "1124042", "vehicle": { "currentStopSequence": 1, "stopId": "1264", "trip": { "directionId": 0, "routeId": "35", "scheduleRelationship": "SCHEDULED", "startDate": "20260726", "startTime": "22:00:00", "tripId": "5-596377615" }, "vehicle": { "id": "256", "label": "2058", "licensePlate": "FR-463-GP" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1785096037" } }