Skip to content

FARMAR ARES

Tug · Norway · built 2016 · AIS Class A

IMO9790945MMSI258199000Call sign3YIOLast AIS position Oct 1, 2026, 21:35 UTC
Open in Terminal

In short

FARMAR ARES (Tug, Norway flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is FARSUND, with an ETA of Oct 1, 2026, 07:00 UTC; its reported draught is 4.8 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:25 UTC).

Current voyage: from Stathelle (departed Sep 20, 2026, 17:30 UTC) to FARSUND

Vessel type
Tug
Flag
Norway
Year built
2016
Gross tonnage
437
Size (length × beam)
32 m
Registered owner
—

Watch this ship

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

We email you a link and a code. That creates a free account, no password or card, and follows FARMAR ARES.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Photo of FARMAR ARES
Photo: Kolforn (Kolforn) I'd appreciate if you could mail me (Kolforn@gmail.com) if you want to use this picture out of the Wikimedia project scope. This file is licensed under the Creative Commons Attributi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
58.082° N, 6.7862° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
24°
Heading
314°
58.082° N, 6.7862° E
Open the full live map →

Last 30 days: 4 port calls (Stathelle, Svartebukt, and Moss).

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

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)

Try the live demo, no sign-up

Identity & particulars

Name
FARMAR ARES
IMO numberWhat is an IMO number?
9790945
MMSIWhat is an MMSI?
258199000
Call signWhat is a call sign?
3YIO
Flag
Norway
Vessel type
Tug
Gross tonnageGross tonnage vs deadweight
437
Length overall
31.5 m
Beam
—
Year built
2016

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.

Builder
Astilleros Armón Vigo
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

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 StathelleAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at StathelleAIS-detectedVoydar port-call detector (AIS geofence)
Left SvartebuktAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SvartebuktAIS-detectedVoydar port-call detector (AIS geofence)
Left StathelleAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at StathelleAIS-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
Stathelle NOSTASep 19, 2026, 12:31 UTCSep 20, 2026, 17:30 UTC28 h 58 min
Svartebukt NOSVBSep 16, 2026, 13:57 UTCSep 19, 2026, 12:01 UTC2 d 22 h
Stathelle NOSTASep 16, 2026, 12:01 UTCSep 16, 2026, 13:48 UTC1 h 47 min
Moss NOMSSSep 15, 2026, 06:56 UTCSep 15, 2026, 19:17 UTC12 h 21 min
Skjerkoya NOSKIAug 20, 2026, 15:07 UTCAug 25, 2026, 08:38 UTC4 d 17 h
Brevik NOBVKAug 20, 2026, 11:25 UTCAug 20, 2026, 15:01 UTC3 h 36 min
Agnefest NOAFTAug 19, 2026, 05:49 UTCAug 19, 2026, 07:58 UTC2 h 9 min
Brevik NOBVKAug 17, 2026, 13:14 UTCAug 19, 2026, 05:44 UTC40 h 29 min
Kristiansand NOKRSAug 2, 2026, 16:40 UTCAug 5, 2026, 05:29 UTC2 d 12 h
Farsund NOFANJul 30, 2026, 13:53 UTCJul 30, 2026, 14:32 UTC39 min
Farsund NOFANJul 27, 2026, 09:11 UTCJul 27, 2026, 13:00 UTC3 h 48 min
Farsund NOFANJul 22, 2026, 12:42 UTCJul 22, 2026, 17:54 UTC5 h 13 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.

Frequently asked questions

Where is FARMAR ARES now?
FARMAR ARES (Tug, Norway flag) was last seen on AIS on Oct 1, 2026, 21:35 UTC, not moving, in the North Sea. The crew-entered destination was FARSUND (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is FARMAR ARES?
FARMAR ARES is a tug sailing under the flag of Norway, built in 2016 by Astilleros Armón Vigo. The vessel is 31.5 m long and has a gross tonnage of 437.
What sanctions and inspection records does Voydar hold for FARMAR ARES?
Voydar has no matched sanctions record displayed for FARMAR ARES from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for FARMAR ARES. 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/9790945
View JSONAPI documentationFree without a key for occasional use; use an API key for more.
Follow by RSSOpen data

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