E.R. AMSTERDAM
Container ship · built 2000
In short
E.R. AMSTERDAM (Container ship) has no AIS position on record with Seadar.
- Vessel type
- Container ship
- Flag
- —
- Year built
- 2000
- Gross tonnage
- 66,289
- Size (length × beam)
- 277 m
- Registered owner
- —
Watch this ship
Get an email when E.R. AMSTERDAM 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 E.R. AMSTERDAM.
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-upIdentity & particulars
- Name
- Source: EU MRV (THETIS-MRV) emissions, record 9213571:2018. Added to Seadar on September 24, 2026. Licence: EC reuse (Decision 2011/833/EU).E.R. AMSTERDAM
- IMO numberWhat is an IMO number?
- 9213571
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Container ship
- Gross tonnageGross tonnage vs deadweight
- 66,289
- Length overall
- 277 m
- Beam
- —
- Year built
- 2000
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from CharlestonAuthority-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 |
|---|---|---|---|---|
| 2018 | 0 t | 0 t | 0 days | — |
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 Seadar 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 |
|---|---|---|---|---|
| Seattle USSEA | Departure | May 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | May 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Jan 27, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Jan 27, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Jan 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Jan 25, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Jan 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Jan 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Jan 18, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Jan 18, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jan 15, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jan 15, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 20, 2002.
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 E.R. AMSTERDAM now?
- Seadar has no displayable AIS position for E.R. AMSTERDAM in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is E.R. AMSTERDAM?
- E.R. AMSTERDAM is a container ship, built in 2000 by Samsung Heavy Industries. The vessel is 277 m long and has a gross tonnage of 66,289.
- What sanctions and inspection records does Seadar hold for E.R. AMSTERDAM?
- Seadar has no matched sanctions record displayed for E.R. AMSTERDAM 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 E.R. AMSTERDAM. 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/9213571Using 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.