Welcome to the experimental Linked Data wrapper for German public transport departures: stops, departure and arrival boards with realtime predictions, and stop search, from the public EFA timetable information servers of seven German transport authorities. It is a live view of those servers, not a copy: every document is fetched on request and names the exact upstream request it came from. Every field the server sends is served, under the server's own field name (vocab/efa).
Licence: the data belongs to the operator of each server, named in every document. None of them declares a licence for its EFA interface, so this wrapper names none; name the operator as the source. This page and the vocabularies are CC BY 4.0.
Every server answers for any stop in Germany (they share the nationwide DELFI timetable), but each has realtime predictions only for its own region. Measured on 2026-11-06 over eleven main stations; Berlin and Hamburg had none on any of them.
vrrbayernmvvkvvbwegtvvsvvovbbvbb/stop/900100003, Alexanderplatz),
not by DHID; the DHID is in the stop's data.
All about one station, Essen Hauptbahnhof. Its DHID, the nationwide stop id, is
de:05113:9289; the examples follow it through search, the stop, its boards,
a second server and the ways a request can go wrong.
vrr/stops?q=Essen%20Hbf —
find a stop by name. The server says how well each match fits
(matchQuality); boards take the id, never a name, because EFA resolves a
bare name silently: asked for "Hauptbahnhof", it answers with Erfurt's.vrr/stop/de:05113:9289 — the
stop: names, position, the stops assigned to it, the products serving it, and links
to its boards.vrr/stop/de:05113:9289/departures
— the next departures, with planned and predicted times, platform changes,
cancellations and service messages. The page opens with one line per departure.bayern/stop/de:05113:9289/departures
— the same station on the Bavarian server: the same timetable, but no
predictions, because Essen is outside its realtime region.vrr/stop/de:05113:9289/arrivals?limit=5
— arrivals, with where each trip comes from.vrr/stop/de:05113:9289/departures.json
— the server's own rapidJSON response, verbatim.vrr/stop/20009289 — the same stop
by EFA's own stop number: a 301 to its DHID, so each stop has one URI.vrr/stop/de:05113:9289:13:1/departures
— a platform's DHID: the server answers for the whole station, so this is a 301
to the station's board.vrr/stop/de:05113:9289/departures?when=2025-01-01T08:00
— a date outside the timetable period: a 400 (upstream answers it with a 200 and
an error code).vrr/stop/de:99999:1 — a DHID no
server knows: a 404.{server}/stop/{DHID}.ttl .nt .rdf
.jsonld .html, and .json for the server's
response{server}/stop/{DHID}/departures[?when=&limit=]when (Europe/Berlin, e.g.
2026-11-07T08:00; default now), at most limit (default 20,
at most 200); same suffixes{server}/stop/{DHID}/arrivals[?when=&limit=]{server}/stops?q={name}index, vocab,
vocab/efa, routes