Tec
View API DocumentationThe TEC is the main public transport operator in Wallonia with a fraction of its network in Brussels. It publishes a GTFS feed which is used to provide the schedule of the vehicles and a GTFS-RT feed which is used to provide real-time data.
Endpoints
Gtfs
/tec/gtfs
The GTFS zip file of TEC
GTFS (Parquet)
/tec/gtfs-parquet
The GTFS feed of TEC converted to Apache Parquet format (zip archive of .parquet files). Parquet uses columnar storage with zstd compression and strong typing, resulting in 40-75% smaller files compared to the original GTFS zip. This format enables extremely efficient data transfer and near-zero RAM overhead when reading specific columns via Polars or DuckDB, making it ideal for analytical workloads and large-scale processing. Produced using gtfs-parquet v0.4.0.
Gtfs realtime
/tec/gtfs-realtime
The GTFS-RT binary file of TEC
GTFS-RT Alerts
/tec/gtfs-rt-alert
Real-time service alerts for TEC (disruptions, detours, cancellations).
GTFS-RT Trip updates
/tec/gtfs-rt-trip-update
Real-time trip updates for TEC including schedule deviations and cancellations.
Punctuality
/tec/punctuality
Daily punctuality table derived from TEC's GTFS-RT trip-update stream over a full Brussels-day window. Each row represents one (trip, stop) observation with the latest known arrival/departure times, delays, and schedule_relationship — plus a synthetic row per cancelled trip when the feed signals cancellation without stop-time entries. Single Parquet file (zstd-compressed). Read with Polars, DuckDB or PyArrow. The data is consistent with the GTFS schedule: scheduled = actual_time − delay matches the static GTFS arrival_time for TEC feeds that publish absolute times.