Skip to content

Mehmet Aga

General cargo ship · built 1989

IMO8914312No AIS position on record

In short

Mehmet Aga (General cargo ship) has no AIS position on record with Voydar. ISM manager: Unimarin Denizcilik Sanayi ve Tic.Ltd.Sti (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Flag
—
Year built
1989
Gross tonnage
6,065
Size (length × beam)
131 m

Watch this ship

Mehmet Aga 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 Mehmet Aga
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

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

Try the live demo, no sign-up

Identity & particulars

Name
Mehmet Aga
IMO numberWhat is an IMO number?
8914312
Flag
—
Gross tonnageGross tonnage vs deadweight
6,065
Length overall
130.9 m
Beam
—
Year built
1989

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 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 BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from FERNANDINA HARBOR, FLAuthority-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
20181,330 t425 t62 days120 kg
20192,921 t931 t199 days119 kg
20203,470 t1,082 t149 days116 kg
20211,595 t497 t68 days122 kg
20221,660 t520 t66 days134 kg
20232,640 t833 t107 days123 kg
20241,599 t509 t61 days135 kg
20252,165 t681 t65 days123 kg

Technical efficiency: EIV (17.08 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
Baltimore USBALDepartureJan 31, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalJan 25, 2011(date only)—USACE foreign traffic vessel entrances & clearances
FERNANDINA HARBOR, FLDepartureDec 17, 2010(date only)—USACE foreign traffic vessel entrances & clearances
FERNANDINA HARBOR, FLArrivalDec 16, 2010(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureMar 28, 2005(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalMar 28, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureNov 15, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureNov 13, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalNov 13, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRDepartureNov 2, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRArrivalOct 31, 2002(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Mehmet Aga now?
Voydar has no displayable AIS position for Mehmet Aga in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Mehmet Aga?
Mehmet Aga is a general cargo ship, built in 1989 by Vard Brăila. The vessel is 130.9 m long and has a gross tonnage of 6,065.
Who is recorded as the owner or manager of Mehmet Aga?
Unimarin Denizcilik Sanayi ve Tic.Ltd.Sti is recorded as ISM manager for Mehmet Aga (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 Mehmet Aga?
Voydar has no matched sanctions record displayed for Mehmet Aga 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 Mehmet Aga. 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/8914312
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