Skip to content
Sanctioned vessel

Nam Dae Chon appears on the OFAC SDN list under DPRK. Verify at OFAC.

Every vessel on:OFAC SDN list

Nam Dae Chon

Bulk carrier · North Korea · built 1997

IMO9138680No AIS position on record

In short

Nam Dae Chon (Bulk carrier, North Korea flag) has no AIS position on record with Seadar. It appears on a sanctions list (details below).

Vessel type
Bulk carrier
Year built
1997
Gross tonnage
15,888
Size (length × beam)
160 m × 25 m
Registered owner
—

Watch this ship

Get an email when Nam Dae Chon 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 Nam Dae Chon.

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
Nam Dae Chon
IMO numberWhat is an IMO number?
9138680
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
15,888
Length overall
160 m
Beam
25 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.

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

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.

DateEventSource
Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at ELIZABETH RIVER, VAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from BaltimoreAuthority-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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
SOUTH HILL 5Name on a sanctions list—OFAC Specially Designated Nationals list

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Seadar saw them.

Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).

Sanctions listings

Every listing of this ship on the sanctions lists Seadar tracks, current and past.

ListProgrammeListed asListedStatus
OFAC SDN list (US)DPRKSOUTH HILL 5not published by the listIn force

Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).

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

PortRecordDate (UTC)BerthSource
ELIZABETH RIVER (SOUTHERN BRANCH) VADepartureMar 29, 2011(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VAArrivalMar 24, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureMar 22, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalMar 7, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureJan 27, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalJan 26, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureJan 11, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalJan 10, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRDepartureJan 7, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRArrivalJan 3, 2011(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureSep 17, 2010(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalSep 15, 2010(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Nam Dae Chon now?
Seadar has no displayable AIS position for Nam Dae Chon in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Nam Dae Chon?
Nam Dae Chon is a bulk carrier sailing under the flag of North Korea, built in 1997. The vessel is 160 m long with a beam of 25 m and has a gross tonnage of 15,888.
What sanctions and inspection records does Seadar hold for Nam Dae Chon?
Nam Dae Chon appears on the OFAC SDN list under DPRK. No matched inspection records are displayed for Nam Dae Chon. 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/9138680
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