US GOV VESSEL
Cargo ship · United States · built 2000 · AIS Class A
In short
US GOV VESSEL (Cargo ship, United States flag) was last seen on AIS on , under way at 14.6 kn, in the South Pacific Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is PER ORDERS; its reported draught is 9.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:00 UTC).
Current voyage: from Port Melbourne (departed Sep 29, 2026, 07:21 UTC) to PER ORDERS
- Vessel type
- Cargo ship
- Flag
- United States
- Year built
- 2000
- Gross tonnage
- 72,737
- Size (length × beam)
- 290 m
- Registered owner
- —
Watch this ship
US GOV VESSEL 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.
We email you a link and a code. That creates a free account, no password or card, and follows US GOV VESSEL.
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
received- Position
- 35.6967° S, 153.4328° E
- Area
- South Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 14.6 kn
- Course
- 54°
- Heading
- 50°
Last 30 days: 1 port call (Port Melbourne).
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-upIdentity & particulars
- Name
- US GOV VESSEL
- IMO numberWhat is an IMO number?
- 9145449
- MMSIWhat is an MMSI?
- 338931000
- Call signWhat is a call sign?
- NEHM
- Flag
- United States
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 72,737
- Length overall
- 289.6 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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- 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.
| Date | Event | Source |
|---|---|---|
| Left Port MelbourneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port MelbourneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from CharlestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BeaumontAuthority-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.
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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Port Melbourne AUPOR | Sep 25, 2026, 19:29 UTC | Sep 29, 2026, 07:21 UTC | 3 d 11 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Charleston USCHS | Departure | Jan 28, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Feb 21, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Dec 20, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Jul 18, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Feb 9, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Nov 10, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Jun 28, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Apr 9, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Apr 5, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Jan 16, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILM | Departure | Jan 30, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Jul 23, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 23, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
About US GOV VESSEL
USNS Red Cloud (T-AKR 313) is one of Military Sealift Command's nineteen Large, Medium-Speed Roll-on/Roll-off (LMSR) Ships and is one of the 49 ships in the prepositioning program. She is a Watson-class vehicle cargo ship named for Corporal Mitchell Red Cloud, Jr., a Medal of Honor recipient, after whom Camp Red Cloud in Korea is also named. Laid down on 29 June 1998 and launched on 7 August 1999, Red Cloud was put into service on 18 January 2000. In 2003 Red Cloud was deployed to transport U.S. Army vehicles to Kuwait to support Operation Iraqi Freedom. On 12 August 2015, an Army UH-60 Black Hawk helicopter crashed on the deck of the Red Cloud when demonstrating capabilities to the Japan Ground Self-Defense Force. The Red Cloud was operating approximately eight miles east of Ukibaru Island.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is US GOV VESSEL now?
- US GOV VESSEL (Cargo ship, United States flag) was last seen on AIS on Oct 2, 2026, 12:28 UTC, under way at 14.6 kn, in the South Pacific Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PER ORDERS (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:00 UTC). This report does not confirm the ship’s current route.
- What kind of ship is US GOV VESSEL?
- US GOV VESSEL is a cargo ship sailing under the flag of United States, built in 2000 by National Steel and Shipbuilding Company. The vessel is 289.6 m long and has a gross tonnage of 72,737.
- What sanctions and inspection records does Voydar hold for US GOV VESSEL?
- Voydar has no matched sanctions record displayed for US GOV VESSEL 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 US GOV VESSEL. 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/9145449Using 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.