Skip to content
voydar.com

IDASSA

Oil tanker · Croatia · built 2019 · AIS Class A

IMO9825477MMSI238066000Call sign9AB3231Last AIS position Nov 17, 2026, 17:34 UTC

In short

IDASSA (Oil tanker, Croatia flag) was last seen on AIS on , under way at 11.4 kn, in the North Atlantic Ocean. Its crew-entered AIS destination is GBTRA (Tranmere), with an ETA of Nov 21, 2026, 01:00 UTC; its reported draught is 12.3 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 17:29 UTC). ISM manager: SAMOS STEAMSHIP CO. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Genova (departed Nov 7, 2026, 14:18 UTC) to GBTRA (Tranmere)

Data: AISHub contributors

Vessel type
Oil tanker
Year built
2019
Gross tonnage
63,500
Size (length × beam)
250 m × 44 m

Last reported position: 36.4978° N, 8.5656° W · North Atlantic Ocean · See on the map

Watch this ship

Get an email when IDASSA reaches Tranmere, 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 17, 2026, 17:40 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for IDASSA 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
36.4978° N, 8.5656° W
Area
North Atlantic Ocean
Status
Under way using engineWhat do AIS statuses mean?
Speed
11.4 kn
Course
291°
Heading
291°
Compass: course over ground 291°, heading 291°
NArrow: course. Hull: heading. As broadcast on AIS.
36.4978° N, 8.5656° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
36.4978° N, 8.5656° W
See it live in 3D →

Last 30 days: 2 port calls (Genova and Piraeus).

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

Data: AISHub contributors

Pro shows IDASSA's track before the last 30 days. Voydar has recorded its port calls since June 12, 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 250 mone tick every 25 m

Beam 44 mPlan outline, to scale

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
IDASSA
IMO numberWhat is an IMO number?
9825477
MMSIWhat is an MMSI?
238066000
Call signWhat is a call sign?
9AB3231
Gross tonnageGross tonnage vs deadweight
63,500
Length overall
250 m
Beam
44 m
Year built
2019

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 years 2024–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 GenovaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at GenovaAIS-detectedVoydar port-call detector (AIS geofence)
Left PiraeusAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at PiraeusAIS-detectedVoydar port-call detector (AIS geofence)
Left Vado LigureAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Vado LigureAIS-detectedVoydar port-call detector (AIS geofence)
Call sign changed from 9AB3231 to DATAHUBAIS, seen by Voydar
Inspection at CORPUS CHRISTI, TexasUSCG PSIX / CGMIX inspections
Port State Control inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Inspection at San Francisco, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at PHILADELPHIA, PennsylvaniaUSCG PSIX / CGMIX inspections
Inspection at PHILADELPHIA, PennsylvaniaUSCG PSIX / CGMIX inspections

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.

Incidents & investigations Authority-reported

Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.

  • Occurred Oct 14, 2024Cargo, Liquid BulkNTSB marine investigations (CAROL)Martinez, CA, USA

    PLATANOS, Martinez, CA, USA (NTSB DCA25FM001)Report published Mar 12, 2026

    The National Transportation Safety Board determines that the probable cause of the contact of the tanker Platanos with the Martinez Refining Company Wharf pier was the pilot transposing the tug positions on his reference card and subsequently issuing orders to each tug that were intended for the other while maneuvering the tanker off a dock.

Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.

Safety & inspections

15
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Jan 28, 2026Vessel InspectionCORPUS CHRISTI, Texasclean
Nov 3, 2025Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Oct 29, 2025Vessel InspectionSTATEN ISLAND, New Yorkclean
Oct 14, 2024Vessel InspectionSan Francisco, Californiaclean
Oct 14, 2024Incident InvestigationWASHINGTON, District of Columbiaclean
Oct 1, 2024Vessel InspectionPSCSan Pedro, Californiaclean
Aug 25, 2024BoardingSan Pedro, Californiaclean
Sep 14, 2023Vessel InspectionPSCSan Pedro, Californiaclean
Feb 7, 2023BoardingPHILADELPHIA, Pennsylvaniaclean
Feb 7, 2023Vessel InspectionPHILADELPHIA, Pennsylvaniaclean
Nov 18, 2022Vessel InspectionMobile, Alabamaclean
Sep 13, 2022Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Sep 12, 2022BoardingSTATEN ISLAND, New Yorkclean
Sep 4, 2022Vessel Operational ControlSTATEN ISLAND, New Yorkclean
Jul 19, 2020Vessel InspectionPSCTEXAS CITY, Texasclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

Emissions & fuel consumption

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

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20204,876 t1,544 t47 days340 kg
20222,963 t939 t27 days386 kg
20231,574 t499 t11 days617 kg
20240 t0 t0 days—
20259,338 t2,992 t94 days340 kg

Technical efficiency: EEDI (3.13 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 “Oil tanker”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile7.76 g per tonne-nautical mile
Lowest reportedHighest reported

48% of the 1,692 ships in this group reported a lower figure.

Group: lower quartile 5.83 · median 7.97 · upper quartile 13.91

CO₂ per nautical mile sailed339.9 kg per nautical mile
Lowest reportedHighest reported

29% of the 1,763 ships in this group reported a lower figure.

Group: lower quartile 316.7 · median 404.7 · upper quartile 492.7

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 159 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
Genova ITGOANov 5, 2026, 08:56 UTCNov 7, 2026, 14:18 UTC2 d 5 h
Piraeus GRPIROct 25, 2026, 08:40 UTCOct 26, 2026, 00:31 UTC15 h 51 min
Vado Ligure ITVDLOct 5, 2026, 10:53 UTCOct 6, 2026, 21:47 UTC34 h 54 min
Punta Cugno ITPUCSep 20, 2026, 13:44 UTCSep 22, 2026, 12:08 UTC46 h 24 min
Muggia ITUGGSep 7, 2026, 08:47 UTCSep 8, 2026, 17:17 UTC32 h 31 min
Trieste ITTRSJul 31, 2026, 04:07 UTCAug 3, 2026, 12:07 UTC3 d 8 h
Augusta ITAUGJul 11, 2026, 19:00 UTCJul 13, 2026, 19:24 UTC2 d 0 h
Trieste ITTRSJun 12, 2026, 21:49 UTCJun 14, 2026, 12:55 UTC39 h 6 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
Nov 7, 2026, 14:29 UTC
Draught change

Reported draught went from 12.8 m to 8.2 m after leaving Genova. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 6, 2026, 18:47 UTC
Draught change

Reported draught went from 12.6 m to 8.1 m while in port at Vado Ligure. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Oct 5, 2026, 06:31 UTC
Two positions

This MMSI was reported in two places 928 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 01:16 UTC
Two positions

This MMSI was reported in two places 805 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 00:32 UTC
Two positions

This MMSI was reported in two places 789 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 00:17 UTC
Two positions

This MMSI was reported in two places 783 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 00:02 UTC
Two positions

This MMSI was reported in two places 778 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 23:17 UTC
Two positions

This MMSI was reported in two places 762 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 22:16 UTC
Two positions

This MMSI was reported in two places 739 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 22:01 UTC
Two positions

This MMSI was reported in two places 733 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 21:46 UTC
Two positions

This MMSI was reported in two places 726 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 21:32 UTC
Two positions

This MMSI was reported in two places 722 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 21:19 UTC
Two positions

This MMSI was reported in two places 716 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 21:02 UTC
Two positions

This MMSI was reported in two places 710 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 20:46 UTC
Two positions

This MMSI was reported in two places 704 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 20:31 UTC
Two positions

This MMSI was reported in two places 698 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 20:01 UTC
Two positions

This MMSI was reported in two places 686 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 19:46 UTC
Two positions

This MMSI was reported in two places 681 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 19:31 UTC
Two positions

This MMSI was reported in two places 675 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 4, 2026, 19:01 UTC
Two positions

This MMSI was reported in two places 663 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)

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

What kind of ship is IDASSA?
IDASSA is an oil tanker sailing under the flag of Croatia, built in 2019. The vessel is 250 m long with a beam of 44 m and has a gross tonnage of 63,500.
Who is recorded as the owner or manager of IDASSA?
SAMOS STEAMSHIP CO. is recorded as ISM manager for IDASSA (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for IDASSA?
Voydar has no matched sanctions record displayed for IDASSA 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. IDASSA has 15 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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

Cite this page

IDASSA. Voydar (voydar.com). https://www.voydar.com/vessel/9825477-idassa. Retrieved November 17, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • 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/9825477-idassa

Generated from voydar.com on Nov 17, 2026, 17:40 UTC