Sources
Where every number on this site comes from. A made-up level is never shown: if a source gives nothing, nothing is shown.
Loading draught
PEGELONLINE — GlW and Fahrrinnentiefe below GlW
fixedPer German gauge the gleichwertiger Wasserstand (equivalent water level, GlW 2022, valid from 1 January 2023) and the verkehrsgesicherte Fahrrinnentiefe below GlW (TuGlW), as characteristic values of the gauge board. Taken over on 13 September 2026 with scripts/prepare-glw.ts; outside the Rhine PEGELONLINE gives them for no station at all.
The loading planner on /route: a gauge with both is decisive for the draught — 17 gauges on the Rhine. The difference between the two — the Fahrrinnentiefe below GlW minus the GlW — is the fixed rule of thumb shown there by default: the number added to the level. Anyone who sets their own rule calculates with that; the margin is subtracted separately.
View source →Rijkswaterstaat — OLR 2022 and the guaranteed water depth
fixedThe report “OLR 2022: Bepaling Overeengekomen Lage Rivierwaterstand 2022 voor de Nederlandse Rijntakken” (Van Putten and Vrijaldenhoven, RWS Oost-Nederland, 7 October 2022). It gives, per gauging station, the OLR (agreed low river level) in m above NAP, and the depth guaranteed in the fairway at that level: 2.80 m on the Boven-Rijn, the Waal, the Pannerdens Kanaal, the Neder-Rijn and the Lek, 2.50 m on the IJssel. The OLR is not in any API — Rijkswaterstaat's observation service gives measurements, not reference levels — so the table is recorded in scripts/brongegevens/ together with the SHA-256 of the PDF, and scripts/prepare-olr.ts fetches that PDF and stops if the fingerprint differs.
The Dutch counterpart of GlW and TuGlW, and thus the same relation between level and fairway depth on the Rhine branches as on the German Rhine. Ten gauges get a fixed rule of thumb from it: Lobith, Nijmegen, Dodewaard, Tiel, the IJsselkop, Doesburg, Zutphen, Deventer, Olst and Kampen. Not the impounded reaches of the Neder-Rijn and the Lek: there the weir holds the level up at low discharge, so the difference from the OLR says nothing about the depth. An OLR is relative to NAP and a GlW to the Pegelnull of a single gauge board; the two are never compared or converted anywhere.
View source →GDWS — schifffahrtspolizeiliche Hinweis Fahrrinnenverhältnisse Rhein
link onlyThe Hinweis (notice) of the Generaldirektion Wasserstraßen und Schifffahrt giving, per stretch of the Rhine, the Fahrrinnentiefe at GlW, the fifteen Bezugspegel and their kilometre range. From this PDF we take one table: the kilometre range per Bezugspegel, because it is stated nowhere else and without it there is no saying which gauge is decisive for which stretch of river. Recorded in scripts/brongegevens/ with the SHA-256 of the PDF; scripts/prepare-bezugspegel.ts fetches the PDF and stops if the fingerprint differs. Two checks make it solid: the GlW per Bezugspegel must exactly match PEGELONLINE's, and the Fahrrinnentiefe of the river stretch must match the TuGlW of that gauge board. All fifteen agree to the centimetre. Bingen and Rees get no range: the GDWS does not list them as Bezugspegel.
Reference for the loading planner. The relation the GDWS itself writes out (Fahrrinnentiefe = Fahrrinnentiefe bei GlW + (Wasserstand − GlW)) appears as a fixed rule of thumb per gauge in the loading planner: the difference between the two characteristic values, i.e. the number you add to the level. A skipper can replace it with their own rule, and the planner then calculates with that.
View source →Water levels and forecasts
PEGELONLINE (WSV)
livePublic API of the German Wasserstraßen- und Schifffahrtsverwaltung (Federal Waterways and Shipping Administration), refreshed every 15 minutes. Levels in cm above the Pegelnull of each individual station, so not comparable with one another.
Current water level at 35 German gauges, also in the water level block on /route:
- Rijn · Iffezheim, Maxau, Speyer, Mannheim, Worms, Mainz, Oestrich, Bingen, Kaub, Koblenz, Andernach, Bonn, Keulen (Köln), Düsseldorf, Duisburg-Ruhrort, Wesel, Rees, Emmerich
- Moezel · Cochem, Trier, Wincheringen, Perl
- Main · Raunheim, Frankfurt (Osthafen), Obernau, Kleinheubach, Wertheim, Steinbach, Würzburg, Astheim, Schweinfurt (Neuer Hafen), Trunstadt
- Donau · Pfelling, Regensburg (Eiserne Brücke)
- Neckar · Mannheim (Neckar)
Bundesanstalt für Gewässerkunde (BfG)
liveA 96-hour series — four days, one point every two hours — via PEGELONLINE. The BfG itself distinguishes "Vorhersage" (the first days) from "Abschätzung" (the further trend, rougher); PEGELONLINE passes this on as forecast and estimate, and we put the source's word next to every point — including the level at your passage time in the loading planner on /route.
Forecast for the German gauges for which PEGELONLINE publishes one. On the Rhine these are Oestrich, Kaub, Koblenz, Cologne, Düsseldorf, Duisburg-Ruhrort and Emmerich; for the other Bezugspegel ELWIS shows empty forecast columns, so the forecast ends earlier there. Which source a gauge uses is shown on the gauge page itself, below the chart.
View source →BfG — fourteen-day water level forecast
liveA probabilistic forecast for fourteen days, which the BfG issues every day as a CSV on vorhersage.bafg.de. Thirteen probabilities per day, from 5% to 95%. Three things are stated in the file header and we take them over as they stand: these are daily means and not levels at a given hour, the timestamp is the start of the day, and above 830 cm the BfG publishes nothing — so nothing is shown there on our side either, not 830. Which gauges are included is decided by the BfG: the file name carries the gauge number, and we link that to the number in our register. The source does not state the reference level. Checked: on 17 October 2026, day 1 was within 2 cm of the daily mean measured by PEGELONLINE that day at every linked gauge, so it is the Pegelnull of the same gauge board. scripts/controleer-bfg-14dagen.ts checks this again, and puts each gauge number next to the number PEGELONLINE itself gives.
The "Forecast for fourteen days" table on the gauge page, with the median per day and the band to which the BfG gives an eighty per cent probability (10% to 90%). Not yet in the loading planner on /route: a daily mean is not the level at the moment you are there, and that first needs a separate assessment. The six-week forecast is also available as a CSV, with the long-term mean; it is not connected yet.
View source →Hochwasservorhersagezentrale (HVZ) Baden-Württemberg, via hochwasser.rlp.de
liveThe same official Rhine forecast that the HVZ publishes itself, but machine-readable and with p10/p50/p90 percentiles: a 47-hour series, one point every hour. We use it as a replacement where PEGELONLINE has no BfG series, and otherwise as a range around it — checked that the two agree to within a few cm. The feed does not say per point whether it is a Vorhersage or an Abschätzung, so we do not add that word either. On its own site the HVZ looks further ahead, but it does not publish that series in machine-readable form; so we show two days, not ten.
Forecast or range for the 18 German gauges whose Pegelkennziffer we have: the Rhine from Maxau to Emmerich, plus Cochem.
View source →Rijkswaterstaat Waterinfo — WADAR
liveThe system that has replaced the old WaterWebservices since December 2025. Measurement and forecast (about 2.5 days ahead), in cm relative to NAP — a different datum from the German Pegelnull, so not comparable with a German figure.
Current water level at 29 Dutch gauges, with a forecast where Rijkswaterstaat publishes one. It does not do so on the Amsterdam-Rijnkanaal and the Noordzeekanaal, nor on the Maas at Maastricht and the Nederrijn at Arnhem. The whole forecast curve is passed to /route, which reads the expected level at your passage time from it — if the source publishes nothing around that moment, nothing is shown. Also in the water level block on /route:
- Rijn (Waal) · Lobith, Nijmegen, Dodewaard, Tiel, Zaltbommel, Dalem (bij Gorinchem)
- Maas · Maastricht (Sint Pieter), Roermond, Venlo, Grave, Lith
- IJssel · Westervoort (IJsselkop), Doesburg, Zutphen, Deventer, Olst, Kampen
- Merwede · Dordrecht (Beneden-Merwede)
- Nederrijn / Lek · Arnhem, Amerongen (beneden de stuw), Hagestein (beneden de stuw), Schoonhoven
- Amsterdam-Rijnkanaal · Weesp, Maarssen, Wijk bij Duurstede, Rijswijk (Betuwepand), Tiel (Amsterdam-Rijnkanaal)
- Noordzeekanaal · Velsen-Zuid (Velsertunnel), Buitenhuizen
Waterinfo Vlaanderen — Hydrologisch Informatiecentrum (HIC)
livePublic KiWIS API of De Vlaamse Waterweg. Values in metres relative to TAW, converted here to centimetres; TAW lies a good two metres below NAP. No forecast in this feed, so we do not show one.
Current water level at 10 gauges along the Albertkanaal, also in the water level block on /route:
- Albertkanaal · Kanne, Bilzen, Genk, Hasselt, Kwaadmechelen, Geel (Stelen), Olen, Grobbendonk, Viersel, Wijnegem
Open Data Basel-Stadt
liveRhine water level at the mouth of the Birs, updated every five minutes, on behalf of the Swiss FOEN (BAFU). No forecast available.
Current water level: Basel (Rheinhalle), also in the water level block on /route.
View source →Notices to skippers and object status
EuRIS — Notices to Skippers
liveThe official notices to skippers of Rijkswaterstaat, De Vlaamse Waterweg, the German WSV and VNF, in one public API. We fetch all notices that are still valid and filter on end date at the source — fetching only the most recent ones would miss long-running closures. For the same notice we also fetch the detail record on request: it contains the explanation written by the waterway authority itself and the times when a restriction applies. These are not in the title — the night closure of the Amsterdam-Rijnkanaal is called only “gedeeltelijke stremming, van km 1.6 tot km 69.8” there. When an authority updates a notice, it reissues it under a new sequence number and with new keys; we then still look it up by the number without the sequence number, so the link and the explanation keep working. The same detail record also states how much delay a notice announces — “ten hoogste een half uur” (at most half an hour) at Sluis Heumen; about half of the notices with a delay give no time, and then none is shown.
/scheepvaartberichten, /vaarwegen, /route and the home page; the explanation and the announced delay per notice on /route.
View source →EuRIS — Live status of locks and bridges
liveStatus per object, refreshed every quarter of an hour, filtered on "Blocked". Only a Dutch layer: EuRIS does not publish this status for the other countries, so there a reported closure from the notices is shown — labelled as a notice, not as live.
The locks and bridges block on /route and the home page.
View source →Rijkswaterstaat Waterkamer — least sounded depth
liveThe least sounded depth per waterway stretch on the Dutch Rhine branches, issued daily around 08:00 by the Waterkamer. In centimetres; the source gives no reference level with it, so neither do we. Fetched via the hydro-meteo data of EuRIS, the same infrastructure from which vaarweginformatie.nl fills its MGD map. A depth of zero is left out: on 29 September 2026 the source gave 0.0 cm with status “Actual” for two stretches on the Lek, while two weeks earlier it showed 1.70 m, and a fairway of zero centimetres is a gap in the measurement there, not a sounding. Such a stretch is therefore not shown, with a note of how many stretches gave nothing that day — no sounding is not the same as deep enough.
The "Fairway depth on this route" block on /route and the "Sounded depth on the Dutch Rhine branches" block on /aflaaddiepte, for the Waal, the Nederrijn and Lek, the IJssel and the Maas-Waalkanaal. Thirteen stretches. On /aflaaddiepte they are in a block of their own and not among the gauges: a stretch has no gauge board, no low reference level and no river kilometre, so there is nothing to add. If a sounding is shallower than the tightest gauge, the summary at the top says so, because a sounded depth takes precedence over a rule of thumb. It is what has been sounded and not a loading draught: how much under-keel clearance you keep is not included, because the source does not say. And the route itself: anyone who has entered their draught is routed around a stretch where the sounding gives less water than their draught plus their under-keel clearance, with the stretch, the sounding and the sounding date; if there is no way around, that is stated. It is the same sum by which the depth block calls a stretch "too shallow", so one threshold instead of two — and it consists of two numbers from the skipper themselves, not of a margin we make up.
View source →ELWIS — Fahrrinneneinschränkungen
liveStructurally shallow or narrow stretches of fairway on the Rhine, Moselle, Main and Main-Donau-Kanal, with the available depth or width in metres, because EuRIS never gives a dimension with such a notice. That depth is relative to the gleichwertiger Wasserstand (equivalent water level): checked on 29 September 2026, 68 of the 69 Rhine notices literally carry “Gleichwertiger Wasserstand (GLW)” as Bezugswasserstand, and the column heading is “Verfügbare Tiefe in der Fahrrinne”. Such a notice is therefore not a stand-alone depth but a locally reduced guaranteed depth. For the Dutch Rhine branches the Waterkamer above does the same. If EuRIS republishes the same restriction, we show only the ELWIS version, via the WSV reference number.
/route, as an advisory notice under "Show all". And on /aflaaddiepte in the calculation itself: if a notice falls within the kilometre range of a Bezugspegel and the reported depth is tighter than the guaranteed one, that gauge calculates with the reported depth, with the location, the kilometre range and the validity date. A notice that is more generous than the guarantee restricts nothing and is ignored.
View source →ELWIS — Schleuseninformationen
fixedWe take one thing from this: the lock number of 113 German locks, taken over on 28 August 2026. We do not fetch the operating hours themselves — they are at the source, and the source is always more up to date than a copy.
The "operating hours" link behind every German lock on /route. For Dutch, Belgian and French locks there is no counterpart, so there is no link there.
View source →Map, network and kilometres
EuRIS — Route planner (RouteCalculatorV2)
livePublic route planner on EuRIS' own network (about 27,000 km). We do not draw the line ourselves, because at EuRIS the notices are attached to that same geometry — so a notice by definition falls where it belongs. We only take over the sailing time outside the Rhine: there EuRIS has official speeds per waterway and includes locking time. On the Rhine it has none and knows no current, so upstream and downstream take equally long; we calculate that part with our own sailing times per river stretch (see /vaartijden).
The route line, the distance, the number of locks and the sailing time outside the Rhine on /route and in the daily report.
View source →EuRIS — Impact layers and ReverseGeocode
liveThe impact layers state per notice which points and stretches it applies to, so a notice appears on the map where EuRIS itself places it. ReverseGeocode links every selectable place to a real location code, then checked with a route calculation that actually produces a result.
The pins on the map and the location codes behind every place name on /route.
View source →EuRIS — Operating hours of locks and bridges
livePer object the windows in which it is operated, seven days ahead, in the object's own local time. We show only what the source calls “full operation”: that is when you can get through. Whatever is operated day and night gets no label — that is 98 of the 115 locks checked, and putting “24 hours” on every line turns information into wallpaper. For a fixed bridge the source gives nothing at all, and rightly so: it does not open.
The operating hours at the locks and bridges on /route, where they differ from day and night.
View source →EuRIS — RIS Index search service
liveSearching for a place name returns the objects the RIS Index knows there — junctions, ports, reporting points — each with its location code; a second request adds the coordinate, the waterway name and what the object is for. That way a new node comes from the register itself instead of from an estimate, and it is then checked with a real route calculation.
The location code and coordinate behind new places on /route, such as Delfzijl, Zwartsluis and Meppel. And recently also live in the search bar of /route: what we do not know ourselves is supplemented from this register under "Bij EuRIS" — places, ports and locks, without the bridges, waiting areas and reporting points the service also returns.
View source →Rijkswaterstaat — Kilometre markers (NWB Vaarwegen)
liveThe 2,886 posts along the Dutch waterways, with the value shown on them. For each bridge and lock we measure the kilometre between the two nearest posts — the object register counts from zero per waterway section, and so put the Waal bridge at Nijmegen at 24.9 instead of 884.
The kilometre at every Dutch bridge, lock and gauge on /route, and the km anchors for the Maas, Julianakanaal, Zuid-Willemsvaart and Kanaal Wessem-Nederweert.
View source →Rijkswaterstaat — Waterway network (FIS/VNDS)
liveThe object register of the Dutch waterways itself, with the air draught clearance and the width per passage opening. That height refers to a fixed level and not to today's level: for a river bridge the design high water level, for a canal bridge the target level — the source states this itself. Where a bridge has no fixed passage opening, the height with the bridge closed applies, and that is then stated too.
The air draught clearance and the name of 3,389 Dutch bridges on /route.
View source →RIS Index — EURIS Inland Fairway Graph
liveThe published waterway network behind EuRIS: 282,766 objects with location code, waterway name and hectometre. From it come 10,603 bridges with name, place and waterway, and for Germany, Belgium and France also the air draught clearance. Rijkswaterstaat leaves the Dutch height field empty here; that comes from its own waterway network, below. Version 0.2.1, CC BY 4.0.
The bridges on /route with their air draught clearance outside the Netherlands, the km anchors for the Albertkanaal and the Kempen canals, the list of places, and the destinations in the search bar of /route: all ports, port zones, locks, terminals and city objects from the register, each with the place name the register gives it and each checked beforehand with a real route calculation (scripts/prepare-euris-bestemmingen.ts). The search bar searches there first and then also asks EuRIS live.
View source →GeoNames
livePlace names and coordinates, CC BY 4.0. Also used to name a bridge that only carries a code name after the place where it lies — only within two kilometres, because along the German Moselle 41 of the 50 bridges would otherwise simply be called “Brug”.
The coordinates behind the nodes, the 400-plus smaller places on /route, and bridge names the source itself does not give.
View source →OpenStreetMap
liveThe map background, with the OpenSeaMap nautical chart layer on top. Also used as an independent cross-check of the kilometre marking. ODbL; the map credits the contributors on screen.
The base map on /route.
View source →News
Binnenschifffahrt Online
livePublic RSS feed of the German trade magazine.
Inland shipping news Germany.
View source →Flows.be
livePublic RSS feed of the Belgian shipping medium. Also covers maritime shipping and ports, so we filter on inland shipping keywords ourselves.
Inland shipping news Belgium.
View source →Official portals
Where you can read the notice, lock or bridge yourself — always check the source before departure; this remains a tool and not navigational advice.
EuRIS open (new tab)
Live lock and bridge status and official notices to skippers for all of Europe.
Vaarweginformatie.nl open (new tab)
Official operating hours, malfunctions and notices to skippers for Dutch waterways.
ELWIS open (new tab)
Official German waterway information (WSV), incl. lock and bridge notices (NfB).
VisuRIS (Flanders) open (new tab)
Flemish waterway portal of De Vlaamse Waterweg: current situation at locks, bridges and waterways.
VNF (France) open (new tab)
Voies Navigables de France — official information on French locks and canals.
How /route sorts things
Notices and live object status are listed per waterway segment of your route, with a status per notice: closed, restricted or info, determined by the restriction codes in the notice itself.
The order within a segment reads the kilometre from the title (“rkm 862”, “Rhein-km 480”), because EuRIS provides no kilometre field. If that fails, the notice simply stays in the list — just less precisely placed.
Notices affecting draught, height or width get a label, from the category EuRIS provides. A dimension is never included, not even in the full notice — you will only find it at the source. Such measurements and general warnings are listed under “Show all”.