The river's logbook for cruise travellers Waterlogged River Cruise Watch

River conditions

Every report Waterlogged River Cruise Watch produces rests on these feeds. When one of them falls behind its freshness target, archive verification fails, or one required station is missing, the affected assessment is withdrawn. A healthy station on the same feed cannot mask the failure.

Where the monitored water is low

This river-system view makes the latest accepted readings easier to place. It is schematic, not geographic: station order follows each river, while spacing and river shape are not to scale.

Schematic gauge context — not a navigation chart. Where a depth model exists, colours apply the latest accepted observation to a 1.60 m reference draught plus 0.20 m clearance. Budapest uses a labelled band set from the measured record and Dresden a labelled judgment band; context-only gauges remain neutral. These states do not forecast a sailing or report operator action.

Rhine

downstream to upstream
  1. Cologne 63 cm Low
  2. Kaub 21 cm Low
  3. Maxau 302 cm Context only

Danube

upstream to downstream
  1. Pfelling 223 cm Low
  2. Hofkirchen 153 cm Low
  3. Kienstock 133 cm Context only
  4. Budapest 86 cm Low
  5. Novo Selo -60 cm Context only
  6. Lom -14 cm Context only
  7. Oryahovo -101 cm Context only
  8. Nikopol -18 cm Context only
  9. Svishtov -69 cm Context only
  10. Ruse -125 cm Context only
  11. Silistra -117 cm Context only

Elbe

upstream to downstream
  1. Schöna 77 cm Context only
  2. Dresden 61 cm Low

Moselle

upstream to downstream
  1. Trier 223 cm Context only
  2. Cochem 219 cm Context only

Main

downstream to upstream
  1. Würzburg 146 cm Context only
workable for reference vessel limited margin below reference threshold context only unknown or withheld

“Workable” is a current-state model result for the stated reference vessel, not a declaration that every ship can pass. Budapest uses a Waterlogged band set from the measured record and Dresden a Waterlogged judgment band; Maxau and Kienstock are low-water context only. High-water rules remain separate.

Canonical current condition record behind the schematic
LocationReadingState BasisObservedSource and meaning
Kaub
Rhine · KAUB		 21 cm Low Reference-depth model 20 Sep 2026, 09:30 CEST 57 cm below the level that keeps 1.90 m in the fairway. PEGELONLINE (WSV).
Maxau
Rhine · MAXAU		 302 cm Context only Context only 20 Sep 2026, 09:30 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. PEGELONLINE (WSV).
Cologne
Rhine · KOELN		 63 cm Low Reference-depth model 20 Sep 2026, 09:30 CEST 76 cm below the level that keeps 2.50 m in the fairway. PEGELONLINE (WSV).
Pfelling
Danube · PFELLING		 223 cm Low Reference-depth model 20 Sep 2026, 09:30 CEST 67 cm below the level that keeps 2.00 m in the fairway. PEGELONLINE (WSV).
Hofkirchen
Danube · HOFKIRCHEN		 153 cm Low Reference-depth model 20 Sep 2026, 09:30 CEST 54 cm below the level that keeps 2.00 m in the fairway. PEGELONLINE (WSV).
Dresden
Elbe · DRESDEN		 61 cm Low Waterlogged judgment bands 20 Sep 2026, 09:30 CEST 29 cm below the 90 cm level where sailings on this stretch are usually disrupted. That band is our judgment, not a measured depth. PEGELONLINE (WSV).
Schöna
Elbe · SCHOENA		 77 cm Context only Context only 20 Sep 2026, 09:30 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. PEGELONLINE (WSV).
Trier
Moselle · TRIER		 223 cm Context only Context only 20 Sep 2026, 09:30 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. PEGELONLINE (WSV).
Cochem
Moselle · COCHEM		 219 cm Context only Context only 20 Sep 2026, 09:30 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. PEGELONLINE (WSV).
Würzburg
Main · WUERZBURG		 146 cm Context only Context only 20 Sep 2026, 09:30 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. PEGELONLINE (WSV).
Budapest
Danube · BUDAPEST		 86 cm Low Waterlogged judgment bands 20 Sep 2026, 09:00 CEST between the 60 cm and 100 cm marks where sailings on this stretch start to be affected. Those bands are set from the measured record, not a measured depth. EuRIS Hydrometeo v3.
Kienstock
Danube · KIENSTOCK		 133 cm Context only Context only 20 Sep 2026, 09:15 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Novo Selo
Danube · NOVOSELO		 -60 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Lom
Danube · LOM		 -14 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Oryahovo
Danube · ORYAHOVO		 -101 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Nikopol
Danube · NIKOPOL		 -18 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Svishtov
Danube · SVISHTOV		 -69 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Ruse
Danube · RUSE		 -125 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.
Silistra
Danube · SILISTRA		 -117 cm Context only Context only 20 Sep 2026, 07:00 CEST This location is shown for river context. Its low stage does not create a low-water route call in the current model. EuRIS Hydrometeo v3.

Feeds

Feed freshness against each feed's maximum age target
Feed Last success Age Target State Detail
pegelonline 20 Sep 2026, 10:35 CEST 52 minutes ago 8 hours fresh last success 52 min ago (within the 500 min SLA)
euris 20 Sep 2026, 10:36 CEST 50 minutes ago 8 hours fresh last success 51 min ago (within the 500 min SLA)
openmeteo_weather 20 Sep 2026, 07:16 CEST 4 hours ago 26 hours fresh last success 251 min ago (within the 1560 min SLA)

Per-gauge acquisition and storage health

A gauge is fresh only when its own observation is current and its raw source response has a verified archive receipt. Feed-wide green status is not enough.

GaugeFeedObservation ArchiveStateDetail
KAUB pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
MAXAU pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
KOELN pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
PFELLING pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
HOFKIRCHEN pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
DRESDEN pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
SCHOENA pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
TRIER pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
COCHEM pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
WUERZBURG pegelonline 20 Sep 2026, 10:30 CEST verified fresh acquired 52 min ago; observation 58 min old; raw archive verified
BUDAPEST euris 20 Sep 2026, 09:00 CEST verified fresh acquired 105 min ago; observation 148 min old; raw archive verified
KIENSTOCK euris 20 Sep 2026, 10:15 CEST verified fresh acquired 52 min ago; observation 73 min old; raw archive verified

Which parts of this build are real

Waterlogged River Cruise Watch is assembled from four independent parts. This table says, honestly, which of them are wired to live data right now and which are running on built-in demonstration content.

Backend resolution per component
ComponentBackendWhy
Gauge readings live waterlogged.ingest.get_current_levels
Scoring engine live waterlogged.engine.sailing.check_sailing
Ships and itineraries live waterlogged.refdata.loader
Feed freshness live waterlogged.staleness.feed_status

Freshness targets in this build: PEGELONLINE 500 minutes and EuRIS (Budapest and Kienstock) 500 minutes. The direct OVF and DoRIS adapters are dormant because EuRIS is the selected transport during the pilot, not for licence reasons (see Legal & disclaimers). Page generated 20 Sep 2026, 11:27 CEST.

API/Service Hydrometeo v3 incorporated from EuRIS (eurisportal.eu).