Where is ER Maden now?

Voydar has no displayable AIS position for ER Maden in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is ER Maden?

ER Maden is a bulk carrier, built in 2012. The vessel is 190 m long and has a gross tonnage of 32,983.

What sanctions and inspection records does Voydar hold for ER Maden?

Voydar has no matched sanctions record displayed for ER Maden 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 ER Maden. Missing records do not establish whether the ship has been detained.

ER Maden

Bulk carrier · built 2012

IMO9611993No AIS position on record

Open in Terminal

In short

ER Maden (Bulk carrier) has no AIS position on record with Voydar.

Vessel type: Bulk carrier
Flag: —
Year built: 2012
Gross tonnage: 32,983
Size (length × beam): 190 m
Registered owner: —

Watch this ship

Get an email when ER Maden 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 ER Maden.

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: ER Maden
IMO numberWhat is an IMO number?: 9611993
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: Detailed type from EU MRV (THETIS-MRV) emissionsBulk carrier
Gross tonnageGross tonnage vs deadweight: 32,983
Length overall: 190 m
Beam: —
Year built: 2012

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.

No owner, operator or manager is recorded for this vessel yet.

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.

Date	Event	Source
Feb 10, 2016	Reported departure from BaltimoreAuthority-reported	USACE foreign traffic vessel entrances & clearances
Feb 8, 2016	Reported arrival at BaltimoreAuthority-reported	USACE foreign traffic vessel entrances & clearances
Dec 15, 2014	Reported departure from New OrleansAuthority-reported	USACE 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.

Year	CO₂ emitted	Fuel burned	Time at sea	CO₂ / n mile
2021	5,154 t	1,627 t	61 days	315 kg
2022	2,321 t	735 t	25 days	335 kg

Technical efficiency: EIV (5.98 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

Port	Record	Date (UTC)	Berth	Source
Baltimore USBAL	Departure	Feb 10, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Baltimore USBAL	Arrival	Feb 8, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Dec 15, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Arrival	Dec 11, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
Tampa USTPA	Departure	Dec 7, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
Tampa USTPA	Arrival	Dec 6, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: December 6, 2014.

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is ER Maden now?: Voydar has no displayable AIS position for ER Maden in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is ER Maden?: ER Maden is a bulk carrier, built in 2012. The vessel is 190 m long and has a gross tonnage of 32,983.
What sanctions and inspection records does Voydar hold for ER Maden?: Voydar has no matched sanctions record displayed for ER Maden 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 ER Maden. 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/9611993

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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