Skip to content

SM LONG BEACH

Container ship · South Korea · built 2007 · AIS Class A

IMO9312755MMSI441701000Call signD7FPLast AIS position Sep 5, 2026, 17:00 UTC

In short

SM LONG BEACH (Container ship, South Korea flag) was last seen on AIS on , under way at 20 kn, in the Gulf of Alaska. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Long Beach: arrived Aug 31, 2026, left Sep 4, 2026.

Vessel type
Container ship
Year built
2007
Gross tonnage
74,962
Size (length × beam)
304 m
Registered owner
—

Watch this ship

SM LONG BEACH 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 SM LONG BEACH
Photo: davitydave from San Francisco, CA, USA · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
50.1045° N, 135.2173° W
Area
Gulf of Alaska
StatusWhat do AIS statuses mean?
Under way using engine
Speed
20 kn
Course
294°
Heading
296°
50.1045° N, 135.2173° W
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.

Pro shows SM LONG BEACH's track before the last 30 days. Voydar has recorded its port calls since August 31, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
SM LONG BEACH
IMO numberWhat is an IMO number?
9312755
MMSIWhat is an MMSI?
441701000
Vessel type
Container ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
74,962
Length overall
304 m
Beam
—
Year built
2007

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 Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Left Long BeachAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Long BeachAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from SavannahAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at SavannahAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from WilmingtonAuthority-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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Long Beach USLGBAug 31, 2026, 11:00 UTCSep 4, 2026, 08:24 UTC3 d 21 h

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Savannah USSAVDepartureAug 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalAug 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMDepartureAug 23, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMArrivalAug 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureAug 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalAug 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalMar 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureMar 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureFeb 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalFeb 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureDec 8, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalDec 8, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 27, 2010.

Frequently asked questions

Where is SM LONG BEACH now?
SM LONG BEACH (Container ship, South Korea flag) was last seen on AIS on Sep 5, 2026, 17:00 UTC, under way at 20 kn, in the Gulf of Alaska. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is SM LONG BEACH?
SM LONG BEACH is a container ship sailing under the flag of South Korea, built in 2007 by HD Hyundai Heavy Industries. The vessel is 304 m long and has a gross tonnage of 74,962.
What sanctions and inspection records does Voydar hold for SM LONG BEACH?
Voydar has no matched sanctions record displayed for SM LONG BEACH 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 SM LONG BEACH. 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/9312755
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