Skip to content

MSC Masha 3

Container ship · Portugal · built 1998 · AIS Class A

IMO9188219MMSI255806109Call signCQIZ3Last AIS position Oct 5, 2026, 11:16 UTC

In short

MSC Masha 3 (Container ship, Portugal flag) was last seen on AIS on , under way at 9.2 kn, in the Mediterranean 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 DZALG (Alger (Algiers)); its reported draught is 8.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 09:53 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Year built
1998
Gross tonnage
21,583
Size (length × beam)
184 m × 30 m

Watch this ship

MSC Masha 3 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.

Last reported position

received
Position
40.8656° N, 2.1427° E
Area
Mediterranean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
9.2 kn
Course
182°
Heading
184°
40.8656° N, 2.1427° E
Open the full live map →

Voydar detected no port call in the last 30 days.

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
MSC Masha 3
IMO numberWhat is an IMO number?
9188219
MMSIWhat is an MMSI?
255806109
Call signWhat is a call sign?
CQIZ3
AIS ship type
Cargo (hazardous cat. C)
Gross tonnageGross tonnage vs deadweight
21,583
Length overall
183.6 m
Beam
29.8 m
Year built
1998

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.

Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
MSC Shipmanagement(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–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
Reported departure from OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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
201814,042 t4,470 t192 days329 kg
201911,816 t3,786 t185 days263 kg
202013,101 t4,151 t190 days277 kg
202114,169 t4,487 t182 days309 kg
202211,333 t3,590 t191 days277 kg
202311,127 t3,525 t166 days280 kg
20249,337 t2,986 t150 days300 kg
202511,677 t3,719 t214 days267 kg

Technical efficiency: EEXI (15.13 gCO₂/t·nm). 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Oakland USOAKDepartureJan 21, 2006(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalJan 21, 2006(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureDec 15, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalDec 15, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureNov 8, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalNov 7, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureNov 3, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalNov 3, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureSep 30, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalSep 30, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXDepartureAug 21, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXArrivalAug 21, 2005(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 20, 2002.

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 29, 2026, 08:14 UTC
Draught change

Reported draught went from 8.1 m to 11.2 m while in port at Lerici. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)

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 MSC Masha 3 now?
MSC Masha 3 (Container ship, Portugal flag) was last seen on AIS on Oct 5, 2026, 11:16 UTC, under way at 9.2 kn, in the Mediterranean 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 DZALG (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 09:53 UTC). This report does not confirm the ship’s current route.
What kind of ship is MSC Masha 3?
MSC Masha 3 is a container ship sailing under the flag of Portugal, built in 1998 by Flender Werke. The vessel is 183.6 m long with a beam of 29.8 m and has a gross tonnage of 21,583.
Who is recorded as the owner or manager of MSC Masha 3?
MSC Shipmanagement Ltd is recorded as ISM manager for MSC Masha 3 (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 MSC Masha 3?
Voydar has no matched sanctions record displayed for MSC Masha 3 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 MSC Masha 3. 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/9188219
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