Skip to content

ARIEL

Other · Norway · AIS Class A

IMONo IMOMMSI259017940Call signLG6235Last AIS position Oct 5, 2026, 02:18 UTC

In short

ARIEL (Other, Norway flag) was last seen on AIS on , not moving, in the Norwegian Sea. Its crew-entered AIS destination is HELLIGVAER; its reported draught is 1 m (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 01:57 UTC).

Current voyage: from Ballstad (departed Sep 22, 2026, 10:57 UTC) to HELLIGVAER

Vessel type
Other
Flag
Norway
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

Get an email when ARIEL arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

That creates your free account and follows ARIEL. Free forever. No card.

Free forever. No card. A free account follows up to 5 ships and ports.

By continuing you accept the Terms and the Privacy policy.

Last reported position

received
Position
67.4068° N, 13.9052° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0.1 kn
Course
—
Heading
—
67.4068° N, 13.9052° E
Open the full live map →

Last 30 days: 5 port calls (Ballstad).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows ARIEL's track before the last 30 days. Voydar has recorded its port calls since July 30, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
ARIEL
MMSIWhat is an MMSI?
259017940
Call signWhat is a call sign?
LG6235
Flag
Norway
Vessel type
Other
Length overall
—
Beam
—
Year built
—

A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.

Ownership & management

Each line shows where the fact comes from. Links backed by an identifier point to the company page.

No owner, operator or manager is recorded for this vessel yet.

Timeline

Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Left BallstadAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BallstadAIS-detectedVoydar port-call detector (AIS geofence)
Left BallstadAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BallstadAIS-detectedVoydar port-call detector (AIS geofence)
Left BallstadAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BallstadAIS-detectedVoydar port-call detector (AIS geofence)

Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.

Port calls

Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Ballstad NOBSDSep 18, 2026, 11:20 UTCSep 22, 2026, 10:57 UTC3 d 23 h
Ballstad NOBSDSep 17, 2026, 08:02 UTCSep 18, 2026, 11:18 UTC27 h 16 min
Ballstad NOBSDSep 16, 2026, 13:13 UTCSep 17, 2026, 07:31 UTC18 h 18 min
Ballstad NOBSDSep 14, 2026, 07:04 UTCSep 14, 2026, 14:51 UTC7 h 47 min
Ballstad NOBSDSep 11, 2026, 04:21 UTCSep 12, 2026, 18:21 UTC38 h 1 min
Ballstad NOBSDJul 30, 2026, 05:35 UTCJul 30, 2026, 07:34 UTC1 h 58 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 22, 2026, 12:33 UTC
Position jump

Reported position moved 12 km in 4 min, faster than any ship can travel. The broadcast position was wrong for a time; GNSS interference, equipment faults and manipulation are all possible causes.

Method seadar.behaviour.position_jump v1

Medium (60%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is ARIEL now?
ARIEL (Other, Norway flag) was last seen on AIS on Oct 5, 2026, 02:18 UTC, not moving, in the Norwegian Sea. The crew-entered destination was HELLIGVAER (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 01:57 UTC). This report does not confirm the ship’s current route.
What kind of ship is ARIEL?
ARIEL is a other sailing under the flag of Norway.
What sanctions and inspection records does Voydar hold for ARIEL?
Voydar has no matched sanctions record displayed for ARIEL from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for ARIEL. Missing records do not establish whether the ship has been detained.

Use this data

This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.

GET /api/v1/vessels/mmsi-259017940
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.

See plans