Skip to content
voydar.com

OPTIMAR

General cargo ship · Cyprus · built 2000 · AIS Class A

IMO9199402MMSI209730000Call sign5BJH5Last AIS position Nov 16, 2026, 14:51 UTC

In short

OPTIMAR (General cargo ship, Cyprus flag) was last seen on AIS on , under way at 9.4 kn, in the Baltic Sea. Its crew-entered AIS destination is FI RAU (Rauma (Raumo)), with an ETA of Nov 16, 2026, 04:00 UTC; its reported draught is 4.7 m (voyage report via Digitraffic marine AIS, received Nov 16, 2026, 14:33 UTC). ISM manager: GoTa Ship Management AB (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Roomassaare (departed Nov 14, 2026, 21:40 UTC) to FI RAU (Rauma (Raumo))

Flag
Cyprus
Year built
2000
Gross tonnage
3,244
Size (length × beam)
100 m
Photo of OPTIMAR
Photo: Pjotr Mahhonin · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position: 60.9445° N, 20.4268° E · Baltic Sea · See on the map

Watch this ship

Get an email when OPTIMAR reaches Rauma (Raumo), and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 16, 2026, 14:51 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for OPTIMAR reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: Voydar for iPhone

Last reported position

received
Position
60.9445° N, 20.4268° E
Area
Baltic Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
9.4 kn
Course
61°
Heading
61°
Compass: course over ground 61°, heading 61°
NArrow: course. Hull: heading. As broadcast on AIS.
60.9445° N, 20.4268° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
60.9445° N, 20.4268° E
See it live in 3D →

Last 30 days: 8 port calls (Roomassaare, Hango (Hanko), Sunila, Harnosand, Husum, and Liepaja).

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

Pro shows OPTIMAR's track before the last 30 days. Voydar has recorded its port calls since September 29, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 100 mone tick every 10 m

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
OPTIMAR
IMO numberWhat is an IMO number?
9199402
MMSIWhat is an MMSI?
209730000
Call signWhat is a call sign?
5BJH5
Flag
Cyprus
Gross tonnageGross tonnage vs deadweight
3,244
Length overall
100 m
Year built
2000

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.

AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via Digitraffic marine AIS on November 16, 2026.

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 · high confidence · retrieved Nov 16, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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 RoomassaareAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RoomassaareAIS-detectedVoydar port-call detector (AIS geofence)
Left RoomassaareAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RoomassaareAIS-detectedVoydar port-call detector (AIS geofence)
Left Hango (Hanko)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hango (Hanko)Authority-reportedDigitraffic Port Call API
Reported arrival at Hango (Hanko)Authority-reportedDigitraffic Port Call API
Arrived at Hango (Hanko)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from KotkaAuthority-reportedDigitraffic Port Call API
Reported arrival at KotkaAuthority-reportedDigitraffic Port Call API
Reported departure from Brahestad (Raahe)Authority-reportedDigitraffic Port Call API
Reported arrival at Brahestad (Raahe)Authority-reportedDigitraffic Port Call API

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.

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
20253,527 t1,100 t159 days99 kg

Technical efficiency: EEXI (12.35 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.

CO₂ per nautical mile sailed98.6 kg per nautical mile
Lowest reportedHighest reported

45% of the 2,956 ships in this group reported a lower figure.

Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 49 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Roomassaare EERMSNov 14, 2026, 06:29 UTCNov 14, 2026, 21:40 UTC15 h 11 min
Roomassaare EERMSNov 8, 2026, 17:24 UTCNov 9, 2026, 20:50 UTC27 h 26 min
Hango (Hanko) FIHKONov 1, 2026, 06:22 UTCNov 3, 2026, 21:20 UTC2 d 14 h
Sunila FISULOct 30, 2026, 18:13 UTCOct 31, 2026, 14:37 UTC20 h 24 min
Harnosand SEHNDOct 27, 2026, 21:06 UTCOct 28, 2026, 21:36 UTC24 h 30 min
Husum SEHUSOct 27, 2026, 04:45 UTCOct 27, 2026, 11:48 UTC7 h 3 min
Husum SEHUSOct 21, 2026, 03:34 UTCOct 21, 2026, 20:02 UTC16 h 28 min
Liepaja LVLPXOct 18, 2026, 03:34 UTCOct 19, 2026, 19:15 UTC39 h 40 min
Oxelosund SEOXEOct 15, 2026, 21:28 UTCOct 17, 2026, 08:10 UTC34 h 42 min
Rautaruukki FIRTROct 11, 2026, 08:52 UTCOct 13, 2026, 13:31 UTC2 d 4 h
Sunila FISULOct 3, 2026, 20:54 UTCOct 5, 2026, 01:27 UTC28 h 33 min
Rauma (Raumo) FIRAUSep 29, 2026, 18:35 UTCSep 30, 2026, 13:42 UTC19 h 7 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hango (Hanko) FIHKOArrivalNov 1, 2026, 06:30 UTCRoro 4Digitraffic Port Call API
Kotka FIKTKArrivalOct 30, 2026, 18:20 UTCHALU2Digitraffic Port Call API
Brahestad (Raahe) FIRAAArrivalOct 11, 2026, 09:00 UTCRautaruukki laituri 4Digitraffic Port Call API
Kaskinen (Kasko) FIKASArrivalOct 8, 2026, 16:00 UTCSyvä07Digitraffic Port Call API

Records published by the authority named on each row. Earliest record for this ship: October 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
Nov 14, 2026, 20:06 UTC
Draught change

Reported draught went from 3.2 m to 4.7 m while in port at Roomassaare. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Nov 3, 2026, 13:24 UTC
Draught change

Reported draught went from 3.2 m to 4.8 m while in port at Hango (Hanko). Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 28, 2026, 23:09 UTC
Draught change

Reported draught went from 4.7 m to 4.2 m after leaving Harnosand. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 28, 2026, 12:07 UTC
Draught change

Reported draught went from 3.2 m to 4.7 m while in port at Harnosand. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 27, 2026, 05:55 UTC
Draught change

Reported draught went from 4.7 m to 3.2 m while in port at Husum. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 21, 2026, 22:04 UTC
Draught change

Reported draught went from 4.7 m to 3.2 m after leaving Husum. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 18, 2026, 20:50 UTC
Draught change

Reported draught went from 3.5 m to 4.7 m while in port at Liepaja. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 16, 2026, 14:14 UTC
Draught change

Reported draught went from 4.2 m to 3.2 m while in port at Oxelosund. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 12, 2026, 21:59 UTC
Draught change

Reported draught went from 3.3 m to 3.8 m while in port at Rautaruukki. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 4, 2026, 21:37 UTC
Draught change

Reported draught went from 4.5 m to 3.2 m while in port at Sunila. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.

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

What kind of ship is OPTIMAR?
OPTIMAR is a general cargo ship sailing under the flag of Cyprus, built in 2000. The vessel is 100 m long and has a gross tonnage of 3,244.
Who is recorded as the owner or manager of OPTIMAR?
GoTa Ship Management AB is recorded as ISM manager for OPTIMAR (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 OPTIMAR?
Voydar has no matched sanctions record displayed for OPTIMAR 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 OPTIMAR. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

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/9199402
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

OPTIMAR. Voydar (voydar.com). https://www.voydar.com/vessel/9199402-optimar. Retrieved November 16, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

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

Sources and attribution

  • Source: Fintraffic / digitraffic.fi, license CC 4.0 BY (CC BY 4.0)
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9199402-optimar

Generated from voydar.com on Nov 16, 2026, 14:51 UTC