Skip to content

IMO 7930137

Bulk carrier · built 1982

IMO7930137No AIS position on record

In short

IMO 7930137 (Bulk carrier) has no AIS position on record with Voydar.

Vessel type
Bulk carrier
Flag
—
Year built
1982
Gross tonnage
25,846
Size (length × beam)
182 m × 29 m
Registered owner
—

Watch this ship

IMO 7930137 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 IMO 7930137
Photo: NTSB · Licence: Public domain · via Wikimedia Commons

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
IMO 7930137
IMO numberWhat is an IMO number?
7930137
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
25,846
Length overall
182 m
Beam
29 m
Year built
1982

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
Reported departure from CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PISCATAQUA RIVER, ME AND NEW HAMPSHIREAuthority-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.

Incidents & investigations Authority-reported

Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.

  • Occurred Jan 23, 2010ACC · Cargo, Liquid BulkNTSB marine investigations (CAROL)Port Arthur, TX, USA

    Eagle Otome / Gull Arrow / Dixie Vengeance, Port Arthur, TX, USA (NTSB DCA10FM010)Report published Sep 27, 2011

    The National Transportation Safety Board determines that the probable cause of the collision of tankship Eagle Otome with cargo vessel Gull Arrow and the subsequent collision with the Dixie Vengeance tow was the failure of the first pilot, who had navigational control of the Eagle Otome, to correct the sheering motions that began as a result of the late initiation of a turn at a mild bend in the w

Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.

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
Charleston USCHSDepartureMar 11, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalMar 10, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PISCATAQUA RIVER, ME AND NEW HAMPSHIREDepartureFeb 25, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PISCATAQUA RIVER, ME AND NEW HAMPSHIREArrivalFeb 24, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureJan 16, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalJan 10, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureDec 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
HUMBOLDT HARBOR AND BAY, CAArrivalDec 7, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureOct 17, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalOct 12, 2012(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJul 31, 2012(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJul 26, 2012(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is IMO 7930137 now?
Voydar has no displayable AIS position for IMO 7930137 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IMO 7930137?
IMO 7930137 is a bulk carrier, built in 1982 by Sanoyas Hishino Meisho. The vessel is 182 m long with a beam of 29 m and has a gross tonnage of 25,846.
What sanctions and inspection records does Voydar hold for IMO 7930137?
Voydar has no matched sanctions record displayed for IMO 7930137 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 IMO 7930137. 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/7930137
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