Skip to content
Offline

Coverage & accuracy

Which ports we cover, how well, and how our numbers compare with an independent public reference

Manifest updated Oct 16, 2026, 01:26 SGT

Single-source disclosure

Live positions come from one community AIS feed. If it drops messages or goes offline, our live numbers degrade for every port at once. We disclose it here rather than hide it.

AISStream.io

Ports

Live ports have the full workspace. Pilot ports are new and labeled as such. Calibrating ports are tracked for positions only while we measure coverage.

Coverage and validation per port
PortStageAreasCalibrationCoverageAgreement with PortWatch
SingaporeSGSIN SingaporeLive18 anchorages, 28 zonesBoundaries: OpenStreetMap seamarksSince Oct 15, 20262 hours of history161 reports per hour369 vessels in 24 hAccumulating
RotterdamNLRTM NetherlandsLive6 anchorages, 0 zonesBoundaries: Rijkswaterstaat (Netherlands)Since Oct 15, 20262 hours of history2,122 reports per hour1,569 vessels in 24 hAccumulating
Los Angeles / Long BeachUSLAX United StatesLive6 anchorages, 0 zonesBoundaries: US federal regulations (33 CFR 110)Since Oct 15, 20262 hours of history351 reports per hour319 vessels in 24 hAccumulating
AlgecirasESALG SpainCalibrating0 anchorages, 0 zonesNot started23 reports per hour51 vessels in 24 hAccumulating
ValenciaESVLC SpainPilot2 anchorages, 0 zonesBoundaries: OpenStreetMap seamarksSince Oct 15, 20262 hours of history217 reports per hour226 vessels in 24 hAccumulating
Antwerp-BrugesBEANR BelgiumCalibrating0 anchorages, 0 zonesNot started2,012 reports per hour1,578 vessels in 24 hAccumulating
HamburgDEHAM GermanyCalibrating0 anchorages, 0 zonesNot started1,290 reports per hour748 vessels in 24 hAccumulating
BarcelonaESBCN SpainCalibrating0 anchorages, 0 zonesNot started232 reports per hour251 vessels in 24 hAccumulating
PiraeusGRPIR GreeceCalibrating0 anchorages, 0 zonesNot started761 reports per hour699 vessels in 24 hAccumulating

How we validate

We detect port calls ourselves and compare our daily counts with IMF PortWatch, a free public dataset of port activity. The volume ratio says how many calls we count for each one they count (1.0 means the same). The correlation says whether the day-to-day ups and downs move together (1.0 means perfectly). PortWatch publishes with a delay of about ten days, so the comparison window trails today.

Sources and licences

Every value we publish traces back to these sources.

Data sources
SourceRoleLicence
AISStream.ioSingle sourceLive positionsno published terms (free API key, no SLA)
OpenStreetMapAnchorage areasODbL 1.0 (© OpenStreetMap contributors)
IMF PortWatchValidationunstated — daily aggregates stored for validation only; agreement score published, attributed IMF PortWatch
UN/LOCODEPort codesUNECE UN/LOCODE (free public use)
ITU country codesFlag statesITU Maritime Identification Digits table (public reference)
Open-MeteoWeatherCC BY 4.0 (Open-Meteo)
OFAC SDN listSanctions screeningpublic domain (US Treasury OFAC SDN list)

Known blind spots

What our data cannot see, stated up front.

  • One AIS feed

    High impact

    All live positions come from a single community feed with no service guarantee.

  • Shore-based reception only

    Medium impact

    Positions come from shore stations, so ships far offshore or in poorly covered areas can be missed.

  • Origins before coverage

    Medium impact

    When a ship enters our coverage from elsewhere we do not know where it came from, and say so.

  • Draught is self-reported

    Medium impact

    Crews type in draught by hand and often leave it stale, so load states are estimates.

  • Chinese ports not monitored

    Low impact

    China appears only as a declared destination; we do not monitor Chinese ports.

  • Validation lags

    Low impact

    The public reference publishes with a delay of about ten days, so validation trails the live data.

Read the methodology