Skip to content

ATLANTICA CARRIER

Other · Cyprus · built 2006 · AIS Class A

IMO9365104MMSI209644000Call sign5BGN6Last AIS position Oct 6, 2026, 02:26 UTC

In short

ATLANTICA CARRIER (Other, Cyprus flag) was last seen on AIS on , under way at 6.5 kn, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is DURANGO FIELD, with an ETA of Oct 6, 2026, 03:00 UTC; its reported draught is 4.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 01:49 UTC). ISM manager: OSM Offshore Bergen AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Great Yarmouth (departed Oct 5, 2026, 21:07 UTC) to DURANGO FIELD

Vessel type
Other
Flag
Cyprus
Year built
2006
Gross tonnage
2,579
Size (length × beam)
74 m

Watch this ship

ATLANTICA CARRIER has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

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

Photo of E.R.Arendal
Photo: John Lucas · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

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

Last 30 days: 7 port calls (Great Yarmouth and Teesport).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
ATLANTICA CARRIER
IMO numberWhat is an IMO number?
9365104
MMSIWhat is an MMSI?
209644000
Call signWhat is a call sign?
5BGN6
Flag
Cyprus
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
2,579
Length overall
74 m
Beam
—
Year built
2006

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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
Builder
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 Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Left Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Left Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Great YarmouthAIS-detectedVoydar port-call detector (AIS geofence)
Former name: AeolusWikidata
Former name: Ocean EnterpriseWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
AeolusFormer nameJan 1, 2006Wikidata
Ocean EnterpriseFormer nameJan 1, 2006Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
2025961 t300 t30 days263 kg

Technical efficiency: Not Applicable. Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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
Great Yarmouth GBGTYOct 5, 2026, 16:24 UTCOct 5, 2026, 21:07 UTC4 h 43 min
Great Yarmouth GBGTYOct 4, 2026, 05:44 UTCOct 4, 2026, 13:27 UTC7 h 43 min
Great Yarmouth GBGTYOct 1, 2026, 06:28 UTCOct 1, 2026, 19:19 UTC12 h 50 min
Great Yarmouth GBGTYSep 28, 2026, 13:45 UTCSep 28, 2026, 18:34 UTC4 h 49 min
Great Yarmouth GBGTYSep 26, 2026, 11:17 UTCSep 26, 2026, 14:04 UTC2 h 47 min
Great Yarmouth GBGTYSep 24, 2026, 13:14 UTCSep 24, 2026, 21:20 UTC8 h 5 min
Teesport GBTEESep 23, 2026, 14:30 UTCSep 23, 2026, 20:54 UTC6 h 24 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 24, 2026, 20:38 UTC
Draught change

Reported draught went from 4.2 m to 4.7 m while in port at Great Yarmouth. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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

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 ATLANTICA CARRIER now?
ATLANTICA CARRIER (Other, Cyprus flag) was last seen on AIS on Oct 6, 2026, 02:26 UTC, under way at 6.5 kn, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was DURANGO FIELD (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 01:49 UTC). This report does not confirm the ship’s current route.
What kind of ship is ATLANTICA CARRIER?
ATLANTICA CARRIER is a other sailing under the flag of Cyprus, built in 2006 by Kleven Verft. The vessel is 74 m long and has a gross tonnage of 2,579.
Who is recorded as the owner or manager of ATLANTICA CARRIER?
OSM Offshore Bergen AS is recorded as ISM manager for ATLANTICA CARRIER (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for ATLANTICA CARRIER?
Voydar has no matched sanctions record displayed for ATLANTICA CARRIER 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 ATLANTICA CARRIER. 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/9365104
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