Skip to content

Vafaa M

Bulk carrier · built 1997

IMO9162409No AIS position on record

In short

Vafaa M (Bulk carrier) has no AIS position on record with Voydar. ISM manager: Mansour Management Gemi Acent (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Flag
—
Year built
1997
Gross tonnage
15,660
Size (length × beam)
159 m × 26 m

Watch this ship

Get an email when Vafaa M 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 Vafaa M.

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.

Last reported position

No AIS position on record for this vessel. Identity and particulars are 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
Vafaa M
IMO numberWhat is an IMO number?
9162409
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
15,660
Length overall
159 m
Beam
26 m
Year built
1997

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 · confidence 0.9 · retrieved Sep 28, 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 arrival at OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from VancouverAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at VancouverAuthority-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
20199,856 t3,131 t182 days226 kg
2022670 t212 t28 days244 kg
2024297 t94 t5 days229 kg
20252,834 t895 t50 days211 kg

Technical efficiency: EIV (8.1 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
OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET)ArrivalNov 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANDepartureOct 3, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalOct 1, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANDepartureJun 6, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalMay 28, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Stockton USSCKDepartureMay 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Stockton USSCKArrivalMay 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureMay 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalMay 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureJan 23, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalJan 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXDepartureNov 12, 2013(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Vafaa M now?
Voydar has no displayable AIS position for Vafaa M in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Vafaa M?
Vafaa M is a bulk carrier, built in 1997 by Imabari Shipbuilding. The vessel is 159 m long with a beam of 26 m and has a gross tonnage of 15,660.
Who is recorded as the owner or manager of Vafaa M?
Mansour Management Gemi Acent is recorded as ISM manager for Vafaa M (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 Vafaa M?
Voydar has no matched sanctions record displayed for Vafaa M 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 Vafaa M. 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/9162409
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