Explainer
Destinations, ETAs and UN/LOCODEs
“Where is this ship going, and when does it get there?” is the question people most often bring to a ship tracker, and the one AIS answers least reliably. This page explains where the destination and ETA come from, how we turn a line of typed text into a link to a port, and how to read the lists on a port page.
Last reviewed
Destination and ETA are typed by hand
A ship’s position is measured. Her destination and ETA are not: an officer types them into the transponder, and they go out unchanged in the static and voyage data every six minutes until somebody types something else.
The destination field holds 20 characters and accepts anything. Looking at what ships actually send, you will find full port names, abbreviations, UN/LOCODEs, pairs of codes joined with > for “from” and “to”, anchorages and pilot stations, canal transits, and notes that are not places at all. You will also find last week’s destination on a ship that has since sailed somewhere else.
The ETA is four numbers — month, day, hour, minute — in UTC. There is no year, and each part can be left as “not available”, so some ships send a date with no time. It is the crew’s own estimate, entered once and often not revised when the ship slows down or waits at anchor.
Class B transponders send neither field. Only vessels with Class A equipment have a destination to show.
What a UN/LOCODE is
UN/LOCODE, the United Nations Code for Trade and Transport Locations, is a code list maintained by the United Nations Economic Commission for Europe. Each place used in trade and transport gets five characters: a two-letter country code (the same ISO codes used elsewhere), then three characters for the place. NLRTM is Rotterdam in the Netherlands; SGSIN is Singapore; NZAKL is Auckland.
The list covers far more than seaports: airports, rail terminals and inland depots have codes too. Each entry carries a marker for what the place is used for, and one of those markers means “port”. Our port directory is built from the entries marked as ports, and every port page is addressed by its code, as in /ports/NLRTM.
Two properties of the list matter when you read a port page. A UN/LOCODE entry gives one position for the place, to the nearest minute of latitude and longitude, and it usually marks the town rather than the berths. And some entries have no position at all. Where that is so, the port page says it cannot list vessels in port.
How VesselTrack matches a destination to a port
When a ship’s destination text arrives, we try to resolve it to one port in the directory. There are two rules, tried in order:
- The whole text is a known name. Case, accents and punctuation are ignored, and the result is compared with the port names in the directory and with a list of alternative spellings we have approved.
- The text contains a UN/LOCODE. We look for five-character words shaped like a code — two letters, then three letters or digits — that belong to a port we know. If there are several, the last one wins.
If neither rule applies, the destination stays unmatched. We do not guess from part of a name.
| As broadcast | Matched to | Why |
|---|---|---|
| NLRTM | RotterdamA UN/LOCODE on its own. | A UN/LOCODE on its own. |
| DEHAM>NLRTM | RotterdamTwo codes, “from” then “to”. The last one is taken as the destination. | Two codes, “from” then “to”. The last one is taken as the destination. |
| NLRTM PILOT | RotterdamThe code stands as a separate word, so it is still found. | The code stands as a separate word, so it is still found. |
| ROTTERDAM | RotterdamThe whole text is a spelling of the port’s name that we recognise. | The whole text is a spelling of the port’s name that we recognise. |
| ROTTERDAM VIA KIEL | No matchNot a code, and the whole text is not a recognised name. | Not a code, and the whole text is not a recognised name. |
| NL RTM | No matchThe space splits the code into two words that mean nothing on their own. | The space splits the code into two words that mean nothing on their own. |
| RTM | No matchThree letters are not a UN/LOCODE, and many places share them. | Three letters are not a UN/LOCODE, and many places share them. |
| FOR ORDERS | No matchNot a place. The ship is waiting to be told where to go. | Not a place. The ship is waiting to be told where to go. |
The rule is deliberately strict. A looser match — on part of a name, say — would link more ships to ports and link more of them to the wrong one. The cost is that a perfectly clear destination written in an unusual way goes unmatched until its spelling is added to the approved list.
A match says what the crew typed, not what the ship will do. A stale destination produces a confident, wrong link.
How to read an ETA
- It is labelled “crew-entered” wherever it appears. VesselTrack does not calculate arrival times; it shows the one the ship broadcasts.
- The year is inferred. Since the broadcast has none, we take the nearest occurrence of that month and day that is not more than 60 days in the past. An ETA of 2 January seen on 30 December is next week; an ETA of 30 December seen on 2 January is three days ago.
- A passed ETA is shown as passed. An ETA a few days old usually means the crew have not updated it, or the ship is waiting off the port. We show it as overdue rather than hiding it.
- Precision follows the broadcast. If the crew entered a date but no time, you see a date.
- Times are UTC. A ship’s ETA is not in the port’s local time or in yours.
A useful sanity check is on the vessel page itself: the distance to go, divided by the current speed, against the time left until the ETA. When the two disagree badly, trust the arithmetic.
Reading a port page
Each port page — Rotterdam, for example — has a small map and three lists. Each list has a precise rule behind it.
In port now
Vessels within 10 km of the port’s UN/LOCODE position that are stopped, heard in the last 24 hours, nearest first. “Stopped” means slower than 0.5 knots, or reporting moored or at anchor with no speed that contradicts it. The destination plays no part: this list answers “what is here”, whatever the crew typed.
The radius is a compromise. Because the position usually marks the town, much less than 10 km would miss ships that are plainly alongside in a large harbour; much more would merge neighbouring ports and sweep in outer anchorages. A ship anchored further out than that, waiting for a berth, is not counted as in port.
Expected arrivals
Vessels whose destination has been matched to this port, that are under way, and that have been heard in the last 7 days — long enough to keep a ship on the list while she crosses a stretch with no receivers. They are ordered by ETA, soonest first; vessels with no usable ETA follow.
This list depends entirely on the matching described above. A ship bound for the port that typed something we could not match is not on it, and a ship that never updated its destination may be on it wrongly.
The map
Every vessel heard in the last 24 hours within 25 km of the port, moving or not. It is wider than the “in port” circle on purpose, so you can see the anchorage and the approaches.
Recent port calls
A log of arrivals and departures we have recorded at the port. Everyone sees the last 7 days; Pro shows the full 90 days that we keep.
How port calls are recorded
A port call is something we work out from positions; no ship broadcasts “I have arrived”.
- Arrival is recorded when a vessel is seen stopped within about 10 km of a port’s position. If more than one port is that close, the one the vessel declared as its destination is chosen, otherwise the nearest.
- Departure is recorded when the vessel is next seen about 15 km or more from that position. Moving around inside that distance — shifting berth, swinging at anchor — is part of the same call.
- Only what was witnessed is logged. A vessel that was already in port when we started listening gets no arrival time. A vessel that vanishes from a port and turns up somewhere else after a gap in reception has its call closed without a departure time.
So the call log is a record of what our receivers happened to hear, with honest holes. An empty log does not mean no ship called: the port may have no receiver in range, or our data feed may have been offline. For why that happens, see How AIS ship tracking works.
If you want to be told about arrivals rather than look them up, the alerts guide shows how.
Sources
Statements about AIS and maritime standards on this page were checked against the following. Statements about what VesselTrack does describe the software as it runs today.
- US Coast Guard Navigation Center — Class A AIS position report and static/voyage dataField-by-field contents of AIS messages 1, 2, 3 and 5, reproduced from Recommendation ITU-R M.1371-5: navigational status codes, ship-type codes, “not available” values.
- UNECE — UN/LOCODE (United Nations Code for Trade and Transport Locations)Code structure (two-letter country + three-character location) and the function classifier that marks a location as a port.
- UNECE — Recommendation No. 16: UN/LOCODE (PDF)The recommendation that defines the code list.
- ITU — Recommendation ITU-R M.1371 (technical characteristics of AIS)The AIS standard itself. We checked its tables as reproduced by the US Coast Guard Navigation Center pages listed here.
Found a mistake? Email support@vesseltrack.net or see how to contact us. Corrections are made on this page and the review date is updated.