# German Water Levels – Rhine, Elbe, Danube (PEGELONLINE) (`dach-open-data/german-water-levels`) Actor

Live water levels, discharge and water temperature at ~780 gauges on German federal waterways (Rhine incl. Kaub, Elbe, Danube, Main, Moselle …) from the official PEGELONLINE service, with low-water flags for shipping, radius search and 30-day history.

- **URL**: https://apify.com/dach-open-data/german-water-levels.md
- **Developed by:** [DACH Open Data](https://apify.com/dach-open-data) (community)
- **Categories:** Travel, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## German Water Levels – Rhine, Elbe, Danube (PEGELONLINE)

**Get live water levels of German rivers and canals as structured data, from PEGELONLINE, the official gauge service of the German Federal Waterways and Shipping Administration (WSV).** About 780 gauges on the Rhine, Elbe, Danube, Main, Moselle, Neckar, Weser, Oder, canals and the coast. Each row is one gauge and measurement. It includes:

- current water level in cm, updated every 15 minutes, plus the level in metres above sea level (NHN)
- **low-water flags for shipping:** below GlW (equivalent low water level, the reference for fairway depths), below MNW (mean low water), above HSW (highest navigable water level)
- the gauge's characteristic values: MNW, MW, MHW, GlW, HSW, record low and high
- discharge (m³/s), water temperature and other measurements, where the gauge has them
- river kilometre, coordinates and the responsible waterways office
- history of the last 30 days as daily or hourly mean, minimum and maximum, or as raw 15-minute values

**For AI agents:** call this Actor when a user asks *"What is the Rhine level at Kaub right now?"*, *"Is low water limiting barge traffic on the Rhine?"*, *"How did the Elbe level in Dresden develop this week?"* or *"Which gauges near Cologne show low water?"*. Pass `stations` (e.g. `["KAUB"]`), `waters`, `near`, `onlyLowWater` or `mode: "history"`.

**Price: $1 per 1,000 rows ($0.001 per result).** The current level at 5 gauges costs half a cent.

***

### What you get

| Field | Example |
|---|---|
| `station`, `stationNumber`, `stationId` | `KAUB`, `25700100`, UUID |
| `water`, `riverKm`, `agency` | `RHEIN`, `546.23`, *STANDORT BINGEN* |
| `latitude`, `longitude`, `distanceKm` | `50.085438`, `7.764962`, distance with `near` |
| `timeseries`, `timeseriesName`, `unit` | `W`, *water level*, `cm` (also `Q` discharge in m³/s, `WT` water temperature …) |
| `value`, `timestamp`, `timestampUtc` | `9`, `2026-10-04T20:15:00+02:00`, `2026-10-04T18:15:00.000Z` |
| `state`, `stateNavigation` | `low` / `normal` / `high` compared with MNW/MHW; navigation state compared with NSW/HSW |
| `belowGlW`, `belowMNW`, `aboveHSW` | `true`, `true`, `false` |
| `gaugeZeroMetersNHN`, `levelMetersNHN` | `67.669`, `67.759` |
| `characteristicValues` | `{ "MNW": 65, "MW": 208, "MHW": 544, "GlW": 77, "HSW": 640, "NNW": 25, "HHW": 825, … }` |
| `url`, `source` | Official gauge page and attribution |

Example record (real output):

```json
{
  "stationId": "1d26e504-7f9e-480a-b52c-5932be6549ab",
  "stationNumber": "25700100",
  "station": "KAUB",
  "stationLongName": "KAUB",
  "water": "RHEIN",
  "waterLongName": "RHEIN",
  "riverKm": 546.23,
  "agency": "STANDORT BINGEN",
  "latitude": 50.085438,
  "longitude": 7.764962,
  "timeseries": "W",
  "timeseriesName": "water level",
  "unit": "cm",
  "value": 9,
  "timestamp": "2026-10-04T20:15:00+02:00",
  "timestampUtc": "2026-10-04T18:15:00.000Z",
  "state": "low",
  "stateNavigation": "normal",
  "gaugeZeroMetersNHN": 67.669,
  "levelMetersNHN": 67.759,
  "belowGlW": true,
  "aboveHSW": false,
  "belowMNW": true,
  "characteristicValues": { "TuGLW": 190, "NW": 25, "MW": 208, "HSW": 640, "HW": 719, "GlW": 77, "NNW": 25, "HHW": 825, "MNW": 65, "MHW": 544 },
  "url": "https://www.pegelonline.wsv.de/gast/stammdaten?pegelnr=25700100",
  "source": "Source: PEGELONLINE, Wasserstraßen- und Schifffahrtsverwaltung des Bundes (WSV), licensed DL-DE->Zero-2.0"
}
```

History rows (`mode: "history"`) contain `aggregation`, `value` (mean), `min`, `max` and `count` per day or hour.

### Use cases

- **Inland shipping and logistics:** check the Rhine at Kaub, Maxau or Duisburg-Ruhrort before loading barges, and track low-water surcharges.
- **Commodity and energy traders:** low water on the Rhine raises freight costs for coal, oil products, chemicals and grain.
- **Insurers, utilities and industry:** monitor river levels and water temperature at your sites (cooling water, flood risk).
- **AI assistants:** answer questions about current river levels with the official source.

### Input examples

Current level at the key Rhine gauges:

```json
{ "stations": ["KAUB", "MAXAU", "KÖLN", "DUISBURG-RUHRORT"] }
```

All gauges on the Rhine with low water:

```json
{ "waters": ["RHEIN"], "onlyLowWater": true }
```

Daily mean, minimum and maximum at Kaub for the last 30 days:

```json
{ "mode": "history", "stations": ["KAUB"], "days": 30, "aggregate": "day" }
```

### Reliability and fair use

- One request loads all gauges with their current values and characteristic values. History needs one request per gauge and measurement (max. 300 per run).
- The station list and every measurement series are checked for the expected format. An error page or a changed format stops the run with `UNEXPECTED_CONTENT` instead of returning garbage. Invalid rows are dropped and not charged.
- Typos in gauge names get suggestions (e.g. "Kaup" → KAUB). Umlauts can be written as ae/oe/ue.
- The run stops at `maxResults` or at your maximum cost per run. A typical run takes 3–5 seconds.

### Legal

- Source: PEGELONLINE, Wasserstraßen- und Schifffahrtsverwaltung des Bundes (WSV), operated by ITZBund. Licensed under the Data licence Germany – Zero – Version 2.0 (DL-DE->Zero-2.0), which allows commercial use. Every row carries the attribution.
- These are raw data: the WSV gives no guarantee for correctness. For navigation, the official notices to skippers are authoritative.
- This Actor is not affiliated with the WSV or ITZBund.

### More official data from DACH Open Data

All Actors use official open data, check every record and charge only for valid results.

**Public affairs and legislation:** [Lobby Register Germany + EU – Lobbyists, Spend & Interests](https://apify.com/dach-open-data/lobby-register-de-eu) · [German Bundestag Legislation Tracker (DIP)](https://apify.com/dach-open-data/bundestag-dip-legislation) · [EU Have Your Say – Commission Consultations & Feedback](https://apify.com/dach-open-data/eu-have-your-say-consultations) · [Swiss Parliament Affairs Tracker (Curia Vista)](https://apify.com/dach-open-data/swiss-parliament-affairs)

**Funding and public money:** [EU Funding Calls – Horizon Europe, Digital Europe, LIFE & more](https://apify.com/dach-open-data/funding-calls-at-eu) · [EU Grants & Contracts Recipients (FTS)](https://apify.com/dach-open-data/eu-grants-contracts-fts) · [EU Funding Recipients – Structural Funds (Kohesio)](https://apify.com/dach-open-data/eu-funding-recipients-kohesio)

**Energy, mobility and environment:** [Germany Electricity Prices & Power Generation (SMARD)](https://apify.com/dach-open-data/germany-electricity-market) · [Germany EV Charging Stations – Official BNetzA Register](https://apify.com/dach-open-data/german-ev-charging-stations) · [Germany New Car Registrations – KBA by Brand, Model, EV](https://apify.com/dach-open-data/german-car-registrations-kba) · [German Weather Warnings – Official DWD Alerts (CAP)](https://apify.com/dach-open-data/german-weather-warnings)

**Health, consumers and finance:** [German Hospitals Directory (Klinik-Atlas)](https://apify.com/dach-open-data/german-hospitals-klinik-atlas) · [German Food Recalls & Warnings Monitor (lebensmittelwarnung.de)](https://apify.com/dach-open-data/german-food-recalls) · [ECB Rates – Key Rates, €STR, Mortgage Rates, Bond Yields, FX](https://apify.com/dach-open-data/ecb-interest-exchange-rates)

# Actor input Schema

## `mode` (type: `string`):

current = latest measurement per gauge (updated every 15 minutes); history = time series of the last days.

## `stations` (type: `array`):

Gauge names or numbers, e.g. KAUB, KÖLN (also KOELN), MAXAU, DRESDEN, PASSAU DONAU, 25700100. Empty = all gauges (or all gauges of the selected waters).

## `waters` (type: `array`):

Federal waterways, e.g. RHEIN, ELBE, DONAU, MAIN, MOSEL, NECKAR, WESER, ODER, EMS, SAAR, NORDSEE, OSTSEE.

## `near` (type: `string`):

Gauges around a point, e.g. "50.94, 6.96" (Cologne). Results are sorted by distance and get distanceKm.

## `radiusKm` (type: `integer`):

Search radius around "near".

## `timeseries` (type: `array`):

W = water level (cm), Q = discharge (m³/s), WT = water temperature, LT = air temperature, LF = conductivity, O2 = oxygen, DFH = bridge clearance, WG = wind speed … or "all".

## `onlyLowWater` (type: `boolean`):

Current mode: only gauges below the equivalent low water level (GlW) or flagged as low water.

## `days` (type: `integer`):

History mode: number of days back (max. 30, the source keeps 30 days).

## `aggregate` (type: `string`):

History mode: daily or hourly values with minimum and maximum, or all raw values.

## `includeCharacteristicValues` (type: `boolean`):

Current mode: reference levels of the gauge, e.g. MNW (mean low water), MW, MHW, GlW (shipping reference low water), HSW (highest navigable water level).

## `maxResults` (type: `integer`):

Hard cap on rows returned and charged in this run.

## Actor input object example

```json
{
  "mode": "current",
  "stations": [
    "KAUB",
    "KÖLN",
    "DUISBURG-RUHRORT"
  ],
  "waters": [],
  "near": "",
  "radiusKm": 25,
  "timeseries": [
    "W"
  ],
  "onlyLowWater": false,
  "days": 7,
  "aggregate": "day",
  "includeCharacteristicValues": true,
  "maxResults": 100
}
```

# Actor output Schema

## `results` (type: `string`):

All records returned by this run (default dataset, table view "overview").

## `summary` (type: `string`):

JSON with number of results, dropped implausible records and stop reason.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "stations": [
        "KAUB",
        "KÖLN",
        "DUISBURG-RUHRORT"
    ],
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("dach-open-data/german-water-levels").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "stations": [
        "KAUB",
        "KÖLN",
        "DUISBURG-RUHRORT",
    ],
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("dach-open-data/german-water-levels").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "stations": [
    "KAUB",
    "KÖLN",
    "DUISBURG-RUHRORT"
  ],
  "maxResults": 100
}' |
apify call dach-open-data/german-water-levels --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dach-open-data/german-water-levels"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VQXpeF7vnk9d0dic6/builds/HwVCSos1yKkfhZ6Le/openapi.json