Updated · 2026-09-04 snapshot of 2026-09-04
Aargau–Germany border crossings — live wait times (cross-border guide)
Live status of 7 Aargau–Germany crossings, refreshed every 15 minutes during peak hours.
All crossings
| Crossing | Wait minutes | Source |
|---|---|---|
| Rheinfelden (Baden) – Rheinfelden AG, Autostrada A861/A3 | 3 min | TomTom estimate (traffic flow) |
| Rheinfelden (Baden) – Rheinfelden AG, Alte Rheinbrücke | 1 min | TomTom estimate (traffic flow) |
| Bad Säckingen – Stein AG | 1 min | TomTom estimate (traffic flow) |
| Laufenburg (Baden) – Laufenburg AG | 1 min | TomTom estimate (traffic flow) |
| Waldshut-Tiengen – Koblenz AG | 3 min | TomTom estimate (traffic flow) |
| Küssaberg – Bad Zurzach AG | 0 min | TomTom estimate (traffic flow) |
| Hohentengen am Hochrhein – Kaiserstuhl AG | 0 min | TomTom estimate (traffic flow) |
The Aargau–Germany region groups 7 monitored border crossings. This hub shows the live status of each and recommends the one with the shortest wait right now. Keep in mind that commuter peaks usually concentrate traffic on the main motorway or trunk-road crossings, while local crossings more often stay fluid even during heavy commute hours.
This page is regenerated automatically on every deploy (typically 4–8 per day). Live readings come from the same pipeline that powers the site's interactive map and the Guide → Border traffic section in our SPA. For each crossing you get a dedicated page with current data, hourly pattern for today, 30-day weekly pattern, live webcam where available and FAQs focused on that crossing's commuter traffic behaviour.
Where the numbers come from and how to use them. The "live" reading in the table is the most recent wait-minutes figure, usually refreshed every 15 minutes during peak windows (06:00–10:00 inbound into Switzerland and 16:00–20:00 in the reverse direction). The three sources, in priority order, are: the official BAZG (Swiss Federal Customs) page for camera-monitored crossings, the TomTom Traffic API for the road segments approaching the crossing (~5-minute latency), and a static estimate from historical patterns when the other two are silent. The difference between "live" and "static" is explicit on every crossing page: a yellow banner flags whenever the figure is a fallback estimate rather than a real measurement.
What a wait at the crossing actually costs. Every minute spent in a queue means fuel burned at idle and, for those on fixed working hours, working time genuinely lost. Choosing the right crossing can make a measurable difference in minutes: compare this crossing's live wait time with the alternative crossings in the same area, listed further down, before you leave. The day's fuel price combined with time lost in queues gives a quick estimate of the real cost of cross-border commuting.
How to choose the right crossing in the Aargau–Germany area
The numbers in the Aargau–Germany table (7 crossings) are a Firestore snapshot fed by the TomTom cron (GitHub Actions workflow traffic-scheduler.yml), refreshed every 10–15 minutes during peak windows. When you open the page, a small hydration script requests the freshest reading via REST and swaps every "wait minutes" cell — the pill next to the date flips from "snapshot" to "live (Firestore, upd. HH:MM)". If hydration fails (browser offline, aggressive privacy extensions, corporate networks with strict CSP), you keep seeing the build-time snapshot: reload the page or check the console if you suspect a block.
To pick a crossing, weigh three factors in order: (1) travel time from your origin to the border exit; (2) live queue time in the table; (3) crossing type — motorway, main road or local. A main crossing with a longer queue is often still faster than a local one with an apparently shorter queue, because the secondary exit has lower capacity and urban access roads add extra time. Commuter rule of thumb: during peak hours (06:00–09:30 and 16:00–19:00), prefer whichever crossing shows the lowest live queue in the table, not necessarily the one that is geographically closest.
Table FAQ
What does "snapshot" vs "live" mean in the pill?
The "snapshot of YYYY-MM-DD" pill is the value at the time of the last deploy (4–8 deploys per day). When hydration completes the Firestore read, the pill flips to "live (Firestore, upd. HH:MM)" and the table numbers refresh to the latest measurements (~5-minute latency from the TomTom poll).
Why do some rows stay at "—" after hydration?
Minor crossings without TomTom or BAZG coverage show "—" until enough statistical data accumulates. In that case the value is a historical average over the last 30 days of observations: the crossing detail page shows the yellow "Historical averages" banner to flag that it is an estimate, not a live measurement.
Discover more