Explainer
How accurate are AIS positions? Errors, delays and spoofing
An AIS position is usually a good fix from the ship’s own satellite-navigation receiver — but it is the position of one antenna, measured a little while ago, relayed through several systems and sometimes disturbed on purpose. Knowing how each of those steps can go wrong tells you how far to trust a dot on a map, and what the odd shapes in a track mean.
Last reviewed
The 10-metre accuracy flag
Every AIS position report carries one bit about its own quality: the position accuracy flag. A 1 means high accuracy, 10 metres or better; a 0 means low accuracy, worse than 10 metres. The default is 0, so a set that never works it out reports “low”.
The flag is the equipment’s opinion of itself, not a measurement by anyone else. It is set from two things the ship’s GNSS receiver knows: whether the fix has been differentially corrected, and whether the receiver is running RAIM, an integrity check that estimates how big its error could be. A second bit, the RAIM flag, says whether that check is in use. The standard’s rules, judged for 95% of position fixes:
| Integrity check (RAIM) | Correction | Accuracy flag |
|---|---|---|
| No integrity check available | Uncorrected | Low (more than 10 m) |
| No integrity check available | Differentially corrected | High (10 m or better) |
| Expected error under 10 m | Either | High (10 m or better) |
| Expected error over 10 m | Either | Low (more than 10 m) |
On our feed, 58% of the 20,655 vessels heard in the hour to flagged their latest position as high accuracy. The rest reported low accuracy — which is also what the flag says when the equipment does not set it at all.
For a tracker the practical meaning is modest. “Low” does not mean the position is wrong: as the table shows, a set that runs no integrity check and receives no corrections reports “low” however good its fix happens to be. At the scale of a ship-tracking map either is usually good enough. What the flag cannot do is warn you about a fix that is confidently wrong, which is the spoofing case below.
Which part of the ship the position is
The position in an AIS report is where the ship’s position-fixing antenna is, not the middle of the ship. When the set is installed it is programmed with four distances from that antenna: A to the bow, B to the stern, C to the port side and D to the starboard side. They double as the ship’s size — length is A + B and beam is C + D — which is where the dimensions on a vessel page come from.
On many large ships the antenna is on or near the bridge, which can be well aft, so the dot for a long ship can be a couple of hundred metres from her bow. That is why a ship moored at a quay can seem to sit on the quay, or two ships side by side can look as if they overlap. The IMO guidelines note that the antenna location may also change on ships fitted with more than one antenna, if the crew switch between them.
How old a position is when you see it
A position report records the UTC second at which the position was fixed — only the second, not the minute or the date. The same 6-bit field doubles as a warning when the fix is not a real measurement:
| Value | Meaning |
|---|---|
| 0–59 | The UTC second at which the position was fixed |
| 60 | Time stamp not available |
| 61 | Position entered by hand |
| 62 | Estimated by dead reckoning, not measured |
| 63 | Positioning system inoperative |
Between that second and the dot on your screen, several delays add up:
- The reporting interval. A moving Class A ship reports every 2 to 10 seconds, a ship at anchor every 3 minutes, a Class B set every 30 seconds or more (see Class A vs Class B).
- The relay. A shore receiver passes the message to a network, the network to a feed, and the feed to the tracker’s own servers.
- The tracker. Positions are stored in batches and the map reloads periodically. What that adds up to on this site is set out under what VesselTrack receives.
Each step is seconds, but at sea seconds are distance: a ship making 20 knots covers about 617 metres a minute. A position a minute old is a long ship-length behind a fast ship, and nowhere at all behind one at anchor. Every vessel page shows when its latest position was received, so you can make that allowance yourself.
Tracks: sampled, straight and sometimes broken
A track is not every report a ship sent. VesselTrack stores at most one point per vessel every five minutes and keeps them for 30 days, and draws straight lines between the points. At 15 knots five minutes is about 2.3 km, so a track cuts the corner of every turn and can look as if it crosses a headland that the ship actually sailed round.
Where no position was received for a while — the ship was out of range, or the feed was down — the track is drawn dashed across the gap. A straight dashed line says only “she was here, then there”, not which way she went (see reading the map).
Heading, course and the arrow
AIS carries two directions. Heading is where the bow points, from the ship’s compass. Course over ground is the direction she is actually moving, calculated by the GNSS receiver from successive fixes. In a cross-current or a strong wind the two differ by several degrees, and a ship crabbing up a river can point noticeably across her own track.
When a ship is stopped, course over ground is meaningless: the receiver is working out a direction from movements of a metre or two, so it wanders at random. A moored ship’s course can swing all the way round while she has not moved. A ship with no compass connected sends heading 511, “not available”; the map then points her arrow along the course over ground instead.
Jumps, impossible positions and spoofing
Some positions are simply wrong. The usual causes, roughly from most to least common:
- Two transponders, one MMSI. The US Coast Guard warns that vessels sending the same MMSI “will appear as one vessel (jumping from position-to-position or line-to-line)”. A track that zigzags between two distant places is almost always this.
- A degraded fix. A receiver with poor satellite visibility, or one that has fallen back to dead reckoning (time stamp 62), drifts. The accuracy flag should then say “low”, but not every set sets it honestly.
- Jamming. A jammed receiver cannot fix a position at all, so the ship’s AIS reports no position, or an estimated one flagged by the time stamp (62 or 63 in the table above).
- GNSS spoofing. Signals that imitate satellite navigation make a receiver calculate a false position — the ITU, ICAO and IMO defined it in exactly those terms when they jointly warned about interference in March 2025. The ship’s AIS then broadcasts that false position in good faith. On a map this looks like a ship on land, a ship far from where her neighbours are, or several ships showing the same impossible spot at once.
- AIS spoofing. Someone transmits AIS messages directly — a ship that does not exist, or a real ship’s identity in the wrong place. AIS has no authentication, so a receiver cannot tell.
What to trust, field by field
| Field | How far to trust it |
|---|---|
| PositionThe ship’s satellite-navigation receiver | Good at map scale, for where the antenna is; can be badly wrong under jamming or spoofing |
| Speed and course over groundThe same receiver | Good while moving; course is meaningless when stopped |
| HeadingThe ship’s compass | Good when connected; 511 means none |
| Time of the positionReceiver clock, then each step of the relay | Shown as the time we received it; seconds to minutes behind |
| DimensionsProgrammed at installation | Set once; all four distances are zero if nobody programmed them |
| Navigational status, destination, ETA, draughtTyped by the crew | Often out of date |
The measured fields are generally good and the typed ones generally stale — the opposite of how much they seem to say. For the typed fields, see navigation status codes and destinations and ETAs; for ships that stop reporting altogether, see why ships disappear.
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.
- US Coast Guard Navigation Center — Class B AIS position and static data reportsField-by-field contents of Class B messages 18, 19 and 24 from ITU-R M.1371-5, including the “CS” / “SO” unit flag, the position-accuracy flag and the RAIM flag.
- US Coast Guard Navigation Center — Shipborne AIS class comparison (PDF)Transmit power and position-reporting intervals for Class A, Class B-SO and Class B-CS.
- International Maritime Organization — Resolution A.1106(29), Revised guidelines for the onboard operational use of shipborne AIS (PDF)Paragraph 22: when a master may switch AIS off, what must be logged and reported, and the two-minute restart. Paragraph 3: ships that are not required to carry AIS.
- US Coast Guard Navigation Center — AIS frequently asked questionsWhy names arrive later than positions, invalid MMSIs, and that AIS is unencrypted and can be spoofed.
- ITU — “Protect satellite navigation from interference, UN agencies urge” (25 March 2025)The joint ITU, ICAO and IMO statement on jamming and spoofing of satellite navigation, including its definition of spoofing as signals that make a receiver calculate a false position.
- 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.