Available now
One reconciled ETA for every container still at sea
Every managed vessel carrying your boxes on one screen. One reconciled arrival time you can dispatch against, not four conflicting numbers to guess between.
Why it matters
Know the real ETA — not the one that's wrong.
Every source tells a different arrival time. The steamship line's published schedule, the terminal's berth window, and the raw AIS (vessel position signal) rarely agree. Pick the wrong one and you send a truck to a closed gate or leave a container burning free days at the yard. So someone on the desk opens three websites per vessel just to decide which number to believe.
On-Water replaces the guesswork with a trust ladder. Conterminal reconciles the conflicting ETAs in a fixed precedence: carrier (SSL, steamship line) published ETA first, then terminal ETA, then berth schedule, then raw AIS, then paper docs last. Each vessel collapses to a single verdict row. Identity is pinned by MMSI and IMO, so a name collision or a stale next-voyage record can't quietly swap the wrong ship onto your board.
And it keeps up with the desk. The on-water working set stays close to the browser. Live updates patch the open view, so repeat filters and page returns never rebuild the whole board. The interface moves with the operator instead of waiting on a fresh report.
How it works
From signal to action.
- 01
Resolve the vessel
Every container is matched to the ship actually carrying it, identity locked by MMSI and IMO. Name collisions and stale next-voyage records can't swap the wrong hull for the right one.
- 02
Reconcile the ETAs
Conflicting arrival times run through the trust ladder: carrier (SSL) published ETA over terminal ETA over berth schedule over raw AIS over paper docs. The highest-trust source that's plausible wins. Documents never override live signal.
- 03
Guard against stale data
A berth-anchor plausibility guard checks each arrival against reality. An AIS-derived date that's physically inconsistent with the active carrier and terminal window gets demoted, not trusted.
- 04
Read one verdict row
Each vessel collapses to a single line: 'Arrives in 12h · tomorrow 4:00 AM · PNCT'. One arrival, one window, one terminal, instead of four competing figures to interpret.
What's inside
The details that carry the weight.
The trust ladder
A precedence engine that ranks every ETA source: carrier (SSL) published ETA, then terminal ETA, then berth schedule, then raw AIS, then paper docs. It settles the disagreement for you instead of leaving it on the desk.
Verdict rows
One reconciled line per vessel: 'Arrives in 12h · tomorrow 4:00 AM · PNCT'. It fuses time-to-arrival, calendar window, and destination terminal into a single scannable read.
MMSI + IMO identity
Vessels are resolved by their MMSI and IMO identifiers, not by name. The box on your board is tied to the exact ship at sea, not a same-named vessel or a leftover prior voyage.
Berth-anchor plausibility guard
A sanity check that flags physically impossible arrivals before they reach your screen. It catches the transposed dates and stale voyage records that raw AIS feeds routinely emit.
Live fleet view
A live picture of the managed vessels carrying your containers, each with its own ETA. Source and lane coverage are confirmed during onboarding.
Operational safeguards
Built into the workflow.
- 01
Stale next-voyage dates are demoted when higher-trust carrier and terminal signals support the active arrival.
- 02
Source disagreements stay visible, including which signal won and why.
- 03
Available now in early-access production, including the berth-anchor plausibility guard.
- 04
A browser-local working set keeps repeat filtering and navigation responsive while live updates refresh the open view.
Freight forwarders and BCOs (Beneficial Cargo Owners) get the most from it. Their whole job turns on arrival accuracy. But carriers planning drayage against the same vessels benefit too.
Questions
Good to know.
When three sources disagree on arrival, which one do I actually see?
The highest-trust source that's still plausible. The trust ladder ranks carrier (SSL) published ETA above terminal ETA, above berth schedule, above raw AIS, above paper docs. A plausibility guard rejects any winner that's physically impossible. You see one reconciled verdict, not the raw conflict.
How does it know it's tracking the right ship?
Vessels are resolved by MMSI and IMO, the durable identifiers assigned to a hull, rather than by ship name. That keeps a same-named vessel or stale next-voyage record from quietly taking over the active container record.
Is on-water tracking live, or on the roadmap?
Available now in supported early-access rollouts, including the plausibility guard. Live coverage depends on the sources and lanes confirmed during onboarding.
See it live
See On-Water Vessel Tracking on your own freight.
Bring a handful of container numbers and we'll show you this capability working on your real operation.