Skip to content

JUNGJIN

Bulk carrier · South Korea · built 2003 · AIS Class A

IMO9268564MMSI440414520Call sign160049Last AIS position Oct 2, 2026, 17:22 UTC

In short

JUNGJIN (Bulk carrier, South Korea flag) was last seen on AIS on , not moving, near Incheon (Yellow Sea). Its crew-entered AIS destination is KRIC; its reported draught is 7.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:48 UTC).

Vessel type
Bulk carrier
Year built
2003
Gross tonnage
7,189
Size (length × beam)
122 m
Registered owner
—

Watch this ship

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

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.

Photo of JUNGJIN
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
37.4354° N, 126.6129° E
Area
Yellow Sea
StatusWhat do AIS statuses mean?
Under way sailing
Speed
0 kn
Course
0°
Heading
206°
37.4354° N, 126.6129° E
Open the full live map →

Voydar detected no port call in the last 30 days.

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls 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
JUNGJIN
IMO numberWhat is an IMO number?
9268564
MMSIWhat is an MMSI?
440414520
Call signWhat is a call sign?
160049
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
7,189
Length overall
121.9 m
Beam
—
Year built
2003

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.

DateEventSource
Reported departure from DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-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.

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
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIADepartureMar 30, 2011(date only)—USACE foreign traffic vessel entrances & clearances
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIAArrivalMar 30, 2011(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VADepartureMar 28, 2011(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VAArrivalMar 26, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHDepartureDec 20, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHArrivalDec 19, 2008(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureDec 8, 2008(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalDec 2, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTDepartureApr 14, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalApr 14, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureSep 22, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalSep 21, 2007(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 13, 2004.

Frequently asked questions

Where is JUNGJIN now?
JUNGJIN (Bulk carrier, South Korea flag) was last seen on AIS on Oct 2, 2026, 17:22 UTC, not moving, near Incheon (Yellow Sea). The crew-entered destination was KRIC (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:48 UTC). This report does not confirm the ship’s current route.
What kind of ship is JUNGJIN?
JUNGJIN is a bulk carrier sailing under the flag of South Korea, built in 2003. The vessel is 121.9 m long and has a gross tonnage of 7,189.
What sanctions and inspection records does Voydar hold for JUNGJIN?
Voydar has no matched sanctions record displayed for JUNGJIN 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 JUNGJIN. 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/9268564
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