The Shipping Forecast is a familiar marine forecast format. Its original job is practical: concise, unambiguous information received over VHF, written down and usable without a map. Text-based, standardised, divided into areas. Essentially the NAVTEX data layer without storage limitations.
A short message covers Beaufort wind, sea state, precipitation and visibility for the next day. Commercial fleets still use these reports in navigation decisions alongside modern models and displays.
The task
That was what I wanted: an area forecast, readable text.
The problem wasn’t access, but retention. Most services show now and the next few days. History disappears or costs extra.
Telegram became delivery channel and archive: searchable messages to revisit.
An unexpected effect: forecasts stopped being just a pre-departure action. Reading twice daily, I gradually saw weather systems changing, beyond individual forecasts.
The solution
I built a bot that:
• downloads DWD and Met Office forecasts several times daily
• splits them by area
• offers subscriptions to selected areas
• sends updates when text changes
• shows a map of area names
• suggests nearby areas from your location
Coverage: Atlantic Spain to Iceland, North Sea Amsterdam to Bergen, Baltic Oslo to Klaipėda.
Using it
Open the bot chat, send
With that forecast, particularly 2.5m seas, I’d open Windy and examine conditions before deciding to leave.
What changed
I began using it beyond departure planning.
The message history became more useful than the forecast itself. Return to any day, see exactly what was issued. I’ve used it in passage notes rather than relying on memory.
Weather checks rarely become a complete habit. Even daily checks often mean wind alone. Not enough in the North Sea: waves can matter more, especially in German waters receiving long swell without obstacles.
One short text contains wind, sea state, rain and visibility. Repetition builds a complete picture.
Bot: @ShippingForecastBot
#notes
A short message covers Beaufort wind, sea state, precipitation and visibility for the next day. Commercial fleets still use these reports in navigation decisions alongside modern models and displays.
The task
That was what I wanted: an area forecast, readable text.
The problem wasn’t access, but retention. Most services show now and the next few days. History disappears or costs extra.
Telegram became delivery channel and archive: searchable messages to revisit.
An unexpected effect: forecasts stopped being just a pre-departure action. Reading twice daily, I gradually saw weather systems changing, beyond individual forecasts.
The solution
I built a bot that:
• downloads DWD and Met Office forecasts several times daily
• splits them by area
• offers subscriptions to selected areas
• sends updates when text changes
• shows a map of area names
• suggests nearby areas from your location
Coverage: Atlantic Spain to Iceland, North Sea Amsterdam to Bergen, Baltic Oslo to Klaipėda.
Using it
Open the bot chat, send
/start and choose an area. New forecasts arrive privately. For example:DWD North and Baltic Sea
Issued: 05.04.2026, 12:30 CEST
Western Baltic:
Sunday:
wind: westerly winds 5 to 6.
visibility/weather: rain or shower with moderate visibility.
sea: eastern part 2 meter.
Monday:
wind: west to northwest about 6, later decreasing about 5.
visibility/weather: first rain or shower with moderate visibility.
sea: at times 2,5 meter.
With that forecast, particularly 2.5m seas, I’d open Windy and examine conditions before deciding to leave.
What changed
I began using it beyond departure planning.
The message history became more useful than the forecast itself. Return to any day, see exactly what was issued. I’ve used it in passage notes rather than relying on memory.
Weather checks rarely become a complete habit. Even daily checks often mean wind alone. Not enough in the North Sea: waves can matter more, especially in German waters receiving long swell without obstacles.
One short text contains wind, sea state, rain and visibility. Repetition builds a complete picture.
Bot: @ShippingForecastBot
#notes
Original and discussionOpen post in Telegram ↗
