Finding Transit Stop IDs
This guide explains how to find stop IDs for different transit providers. The stop ID is required to set up transit monitoring for your display.
Quick Methods for Real-time Providers
STIB (Brussels)
- Go to the STIB website
- Click on a line that passes through your stop of interest
- Select your direction and click on your specific stop
- In your browser’s URL, look for a part that looks like
_stop=4213
- The number after
_stop=
is your stop ID
De Lijn (Flanders)
- Go to the De Lijn website
- Select “Stops” in the menu
- Enter your stop’s name in the search bar
- In the suggestions that load, look for the small number next to the stop name
- This number is your stop ID
BKK (Budapest)
- Go to the BKK Trip Planner
- Find your stop on the map
- In the popup that appears in the top left corner, there will be a number starting with a #
- The stop ID is that number (without the hashtag)
SNCB (Belgian Railways)
Currently, there is no easy way to find SNCB stop IDs through their website. Please use one of the advanced methods below.
Advanced Methods
Using Stop Explorer
If your device can handle it (not recommended for Raspberry Pi), you can use the Stop Explorer interface:
- Set up the brussels_transit package
- Access the Stop Explorer interface
- Search for your stop
- The interface will show the stop ID
Note: The interface and GTFS data processing can be resource-intensive. It’s recommended to run this on a desktop computer or server rather than directly on the Raspberry Pi.
Manual GTFS Method
For any provider (including those without real-time data):
- Download the GTFS schedule from your chosen provider
- Open the zip file
- Find and open
stops.txt
- Look for your stop name and note the associated stop ID
- If there are multiple IDs for the same stop name, you may need to experiment to find the one that serves your specific line and direction
Line IDs (Advanced)
Some providers allow filtering by line ID:
- STIB: You can use the line number, but this will disable fallback to GTFS schedule because the line number used in the real-time API is different from the route ID used in the GTFS Schedule.
- BKK: Must use the route_id (different from the line number shown on vehicles)
- De Lijn: ? (Line number works for the real-time API, not sure about the GTFS Schedule)
- Other providers: Use the route_id from their GTFS feed