Skip to content

Home/Alternatives/Towage & pilotage

The alternative to Kpler for Towage and Pilotage

Most maritime data evaluations begin with one of the large analytics platforms, which is a reasonable starting point. This page addresses the stage that follows. We are an independent AIS data provider operating our own network, and towage sits close enough to our strengths to warrant a place on the same shortlist.

100,000+

Vessels tracked / day

49M+

AIS positions / day

40+

Countries covered

<5s

Antenna to your API

Who we are, and what sits behind the feed.

We own and operate the physical infrastructure the data originates on. Nothing is procured or blended from a third party feed.

  • AIS position data is the only product we sell.Worldwide AIS Network ApS is a Danish company based in Copenhagen, CVR 45911748, backed by Den Danske Maritime Fond, approved under the Startup Denmark scheme, and building with peaq. We supply position data to towage operators, tug and workboat fleets, pilotage authorities and marine services businesses.

  • Every position is assessed, not merely collected.Terrestrial and ship-borne receivers, plus satellite feeds for open ocean. Every station runs the same dedicated standardised hardware and encrypts each message at the instant of capture. Every position is nanosecond time-stamped and carries a trust score from our anomaly detection models.

  • Delivery is deliberately conventional.Raw NMEA over TCP, a REST API for job reconstruction and utilisation reporting, a WebSocket stream for live dispatch, and SAPIENT compliant output to the BSI Flex 335 interface. Across the network that is 100,000+ vessels tracked a day, 49M+ positions a day, 40+ countries, and under five seconds from antenna to your API.

Evaluate us on your own harbour.Send a polygon covering the approaches, turning basin and berth pockets you work, together with a date range, and we will return what our network collected within it.

Check coverage in your port

What to look for in an AIS data provider for towage and pilotage.

These are the questions we would put to a supplier if we were procuring rather than supplying. Put all of them to every provider under consideration, including us. Where another supplier answers them better for the harbours you work, act on that.

  • Provenance: a single position should trace back to the receiver that collected it.

    Take one record from a sample and establish which receiver collected it, and when. Some products are built to deliver a finished vessel track, others retain the collection record beneath it. Both are legitimate. An operator who may have to defend a made fast time in a tariff dispute, or produce continuous data for a safety investigation, should determine which of the two the contract provides before the question becomes urgent.

  • Latency: define where the clock starts and where it stops.

    Latency figures are comparable only when both endpoints are defined identically. Antenna to API, API to your screen, and the refresh interval of a map view are three distinct measurements, and each supplier will quote the one that belongs to it. Ship assist turns on events lasting seconds, so fix the definition and then verify it live during a busy hour rather than accepting the figure on paper. Ours is under five seconds from antenna to API.

  • Delivery formats: the output has to reach dispatch, job logging and billing.

    Decide early whether you require raw records or a processed product, because that choice governs everything built on top of it. Traffic display and VTS work requires raw NMEA over TCP, job reconstruction and tender analysis requires a REST API and a bulk history export, live dispatch requires a WebSocket stream. Establish what is provided when you need the raw messages rather than the processed output, whether that attracts a further charge, and whether embedding the output within your own software is licensed.

  • Coverage is decided in the harbours you actually work.

    Global totals, ours included, establish very little about one port. VHF is line of sight, roughly 20 to 40 nautical miles in open water and considerably less behind terrain, and dense harbour traffic causes message collision. What counts is reception in the approach channel, the pilot boarding place, the turning basin and alongside. Issue every provider the same polygon and the same dates, request the raw result rather than a coverage map, and establish precisely when their history for that area begins.

  • Independence: ownership of the receivers determines continuity.

    Establish who owns its network behind the feed. Commercial AIS supply has consolidated into fewer hands, so a source licensed today may sit under a different owner at renewal, and for a towage business tied to a long terminal contract that is a continuity question as much as a technical one. Confirm what happens to your terms should ownership change, and settle in writing whether the pilot service, the agent and the terminal on the same quay may use the same positions or must each licence separately.

  • Spoofing and interference: a doubtful position should arrive flagged, not corrected.

    GNSS jamming and AIS manipulation introduce false positions and phantom movements into operating pictures, and in a harbour a poor position is equally likely to be a Class B unit on a workboat reporting sparsely or a message lost to collision. The material difference between products is whether a doubtful position reaches you with an indicator attached or is smoothed away before you see it. Establish what informs the assessment and whether the score travels with the data into your systems. We score every position and pass it through rather than adjudicating on your behalf.

How the positions
are actually produced.

Every station runs the same dedicated, standardised hardware, encrypting each message the instant it is captured.

Collect

On receivers we own

Terrestrial and ship-borne receivers, plus satellite feeds for open ocean run by us rather than licensed from somebody else, covering 100,000+ vessels a day across 40+ countries, with terrestrial reception aimed at approaches and inner harbours where towage work happens.

Verify

Scored before it reaches you

Each position is nanosecond time-stamped and given a trust score by our anomaly detection models, so a manipulated position is flagged rather than written into a job record you later bill on.

Deliver

Into the tools you already run

Raw NMEA over TCP, a REST API, a WebSocket stream, or SAPIENT compliant output to BSI Flex 335, in under five seconds from antenna to your API. Your dispatch, job logging and billing stay exactly where they are.

How Worldwide AIS Network compares.

The questions worth putting to every provider on your shortlist, including us.

What to checkWhat to ask any providerWorldwide AIS Network
Where the data comes fromDo you operate the receivers yourselves, or buy and blend feeds from others?Our own independent physical infrastructure. Terrestrial and ship-borne, plus satellite feeds.
Provenance on each positionCan you tell me which receiver collected this specific position, and when?Every position carries its originating receiver and a nanosecond time stamp.
Handling of spoofingHow do you detect a manipulated or spoofed position before it reaches me?Anomaly detection models assess the validity of every position in real time.
LatencyWhat is the delay from reception to the data being available in my system?Under five seconds, antenna to API.
Delivery formatsWhich formats do you deliver, and will they drop into what I already run?Raw NMEA over TCP, REST API, WebSocket stream, and SAPIENT compliant output to BSI Flex 335.
Coverage where it matters to youCan you show me real data for my specific waters before I commit?100,000+ vessels a day across 40+ countries. Ask for a sample of your own area.
Running alongside what you haveCan I add you next to my current provider rather than replacing it?Yes. Running side by side is the intended pattern, not a compromise.

We have deliberately not filled in a column for any other provider. Coverage, latency and sourcing change, and a claim we cannot evidence is worth nothing to you. Put these questions to everyone you are evaluating and compare the answers yourself.

Questions we get from towage and pilotage teams comparing providers.

Can we run Worldwide AIS Network alongside our existing provider?

Yes. It is the arrangement we expect rather than one we merely permit. Two independent sources over the same stretch of water is how a disputed made fast time or a contested track through the turning basin gets resolved, and it removes the single point of failure in a feed you may be billing against. Most engagements begin as a second source alongside something already in place, and a substantial number remain that way. We would rather run beside your current supply and be judged on the overlap than ask an operator to withdraw a working system on trust.

How much integration work is a second AIS feed for a tug fleet?

That depends on where it lands. If your traffic display already accepts raw NMEA and AIVDM over TCP, we present as another receiver and the work is configuration rather than development. If the feed enters dispatch, job logging, billing or a reporting warehouse, the effort is normally mapping our fields onto an existing schema and determining precedence when two sources describe the same tug. Budget for a parallel run and a reconciliation pass rather than a same day cutover. Where we judge an integration to be among the harder ones, we will say so before you begin.

If we did switch, do we have to move everything at once?

No, and we would advise against it. The sensible sequence is a coverage sample over one harbour polygon first, reconciled against job records you already trust, then a live feed run in parallel through a busy period including night moves and adverse weather, then a decision on what migrates and what remains. Nothing in our delivery depends on exclusivity, so if you do consolidate later, the timing is yours rather than ours.

Do you cover our harbour, and how do we check?

Send a polygon and we will answer precisely, including where reception is thin. We supply only what our own network collected, so the answer is specific to that water rather than to a global figure. The network covers 40+ countries, but that is a headline number, and your harbour is one specific body of water with its own terrain and its own traffic density. If a tender study needs more than our network collected there, you will be told before you commit rather than afterwards.

Do you detect the jobs for us, or do we build that ourselves?

These are two distinct purchases and worth separating at the outset. We are a data provider. Our product is verified AIS position data carrying its provenance and trust score, delivered as raw NMEA, a REST API, a WebSocket stream or SAPIENT compliant output, dense enough and fast enough that mob, made fast, push or pull and let go can be derived from it. Converting those positions into job records, tariffs and utilisation reporting is work undertaken by you or your software partner, and we license the data for precisely that. If you require a finished workflow product with screens and alerts built in, assess that separately. A platform and an independent data source are not mutually exclusive, and plenty of operators run both.

Past the comparison stage?

This page is written for teams mid evaluation. If your requirement is already settled and you want the detail on reconstructing ship assist jobs from position records, pricing a towage tender on recorded traffic, evidencing a safety case, escort policy review, tug utilisation and pilot dispatch planning, the main page for the sector treats each in greater depth: AIS data for towage operators.

AIS data for towage operators

Comparing providers for another sector?

Put us on the shortlist and test us.

Name the harbour, define the geofence, set the dates. We will return the positions our network collected there, the receiver each message came from, and where our coverage is thin, so the comparison is settled on data rather than on assertion.

Check coverage in your port