Port of Saint-Seuri-de-Bourg
In short
Saint-Seuri-de-Bourg: no ships detected in port from AIS in the last 3 days (as of Oct 6, 2026, 12:01 UTC). Coverage depends on AIS reception in the area.
Get port alerts
Get an email when Saint-Seuri-de-Bourg is busier than usual or is named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
- In port now
- 0
- Arrivals, last 24 h
- 0
- Departures, last 24 h
- 0
- Ships nearby, last 6 h
- 0
Vessels near Saint-Seuri-de-Bourg
Ships Voydar received on AIS near the port in the last 6 hours, most recent first. Being near a port is not a port call; the board above lists calls.
No vessels detected near Saint-Seuri-de-Bourg in the last 6 hours. As our AIS coverage grows, arrivals and departures will appear here live.
Tide and water level
Latest readings at gauges within 20 km of Saint-Seuri-de-Bourg, as published by each water authority, with the last 48 hours. Times in UTC.
| Gauge | Level | Change (3 h) | Last 48 h | Reading (UTC) |
|---|---|---|---|---|
| Ambesrelative to chart datum (zéro hydrographique) · 3.1 km away | 2.34 m | +1.19 m | ||
| Le Marquisrelative to chart datum (zéro hydrographique) · 5.2 km away | 2.12 m | +1.08 m | ||
| Fort Medocrelative to chart datum (zéro hydrographique) · 12.9 km away | 2.87 m | +1.55 m |
Source: SHOM REFMAR / RONIM tide gauges (live sea level). Sea level: SHOM / REFMAR (Licence Ouverte 2.0). Licence: etalab-2.0 (Licence Ouverte 2.0).
Gauges are matched to this port by distance (within 20 km of the port position), a link derived by Voydar, not stated by the authority. Levels are relative to each gauge's own reference level: they are not water depths. Not for navigation.
Forecast
Model forecast for Saint-Seuri-de-Bourg over the next 72 hours, every 6 hours: wind, gusts, waves and visibility. Times in UTC.
| Time (UTC) | Wind (kn) | From | Gusts (kn) | Waves (m) | Period (s) | Visibility (km) |
|---|---|---|---|---|---|---|
| 6 | 140° | 16 | 0.8 | 12 | 24 | |
| 6 | 140° | 11 | 0.8 | 11 | 17 | |
| 3 | 187° | 9 | 0.9 | 11 | 17 | |
| 4 | 193° | 7 | 1 | 11 | 24 | |
| 8 | 251° | 15 | 1 | 11 | 13 | |
| 9 | 304° | 15 | 1.6 | 6 | 24 | |
| 10 | 335° | 17 | 2.1 | 8 | 24 | |
| 8 | 339° | 14 | 2.6 | 10 | 24 | |
| 10 | 338° | 20 | 2 | 10 | 24 | |
| 5 | 337° | 10 | 1.8 | 9 | 24 | |
| 4 | 345° | 7 | 1.5 | 10 | 24 |
Forecast: ECMWF IFS 0.25° + ECMWF WAM, run of Oct 6, 2026, 00:00 UTC. Visibility: NOAA GFS 0.25° + GFS-Wave (WAVEWATCH III), run of Oct 6, 2026, 06:00 UTC. Waves are taken from the wave model's nearest sea point, 54 km away.
Source: ECMWF open data (IFS 0.25° forecasts, ECMWF WAM waves). This service is based on data and products of the European Centre for Medium-Range Weather Forecasts (ECMWF). Source: www.ecmwf.int. Licence: CC BY 4.0. Licence: CC-BY-4.0 + ECMWF Terms of Use.
Source: NOAA GFS 0.25° and GFS-Wave (WAVEWATCH III) forecasts. Forecast: NOAA NCEP GFS / GFS-Wave (WAVEWATCH III). Licence: US Government work (public domain); NOAA Open Data Dissemination.
A model forecast, not an observation. Not for navigation.
Marine accidents investigated nearby Authority-reported
1 accident or incident within 100 km of the port in the published records of national accident-investigation boards since Apr 22, 2016, located where the board states a position. The most recent:
- Apr 22, 2016死傷等運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)15 km away
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典：運輸安全委員会「船舶事故等調査報告書」（https://jtsb.mlit.go.jp/）。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
Tools for this port
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/ports/FRUQJUsing this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.