Molsa Pre-departure data checklist The survey →

Twenty minutes ashore, gigabytes saved at sea.

Most satellite data isn't spent by people - it's spent by devices doing things nobody asked for that day: photo backups, app updates, game launchers, cloud sync. All of it can wait for port. These are the settings that make it wait.

Printable · no signup · updated Sep 2026

The day before, on shore Wi-Fi

Anything you update ashore won't try to update itself mid-passage.

Every phone aboard - iPhone

One crew phone left on defaults can quietly eat a day of plan. The boat's Wi-Fi feels like home Wi-Fi to the phone, so tell it otherwise.

Every phone aboard - Android

WhatsApp - worth its own section

It's how crews talk to home, and its defaults assume data is free.

Laptops - the silent heavyweights

What actually burns the data

Typical figures - they vary, but the proportions don't. Notice where the things you actually need offshore sit.

ActivityTypical data
Weather GRIB file for a passage1–20 MB
Text messages & email home, per day< 50 MB
Voice call, per hour~30–60 MB
Social feed with video autoplay, per hour200–500 MB
Video call, per hour300–700 MB
Cloud photo backup after a day of photos/video0.5–2 GB
One skipped OS or app update, catching up at sea0.5–3 GB
HD streaming, per hour1–3 GB
The pattern: everything a passage actually depends on - weather, messages, tracking - is measured in megabytes. What empties the plan is background traffic nobody chose. That gap is the whole reason this checklist works.

Underway

This checklist exists because we're researching where offshore data really goes. If you sail with a satellite link, your numbers would help:

Take the 3-minute offshore data survey

Compiled by Molsa - an application-aware data layer for satellite-connected vessels, in development. Print this page and pin it by the nav station; your crew will find the boxes strangely satisfying to tick.