IMO 9232383
Container ship · built 2002
In short
IMO 9232383 (Container ship) has no AIS position on record with Voydar.
- Vessel type
- Container ship
- Flag
- —
- Year built
- 2002
- Gross tonnage
- 25,630
- Size (length × beam)
- 206 m
- Registered owner
- —
Watch this ship
Get an email when IMO 9232383 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 IMO 9232383.
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-upIdentity & particulars
- Name
- IMO 9232383
- IMO numberWhat is an IMO number?
- 9232383
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Container ship
- Gross tonnageGross tonnage vs deadweight
- 25,630
- Length overall
- 206 m
- Beam
- —
- Year built
- 2002
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.
| Date | Event | Source |
|---|---|---|
| Former name: Wehr Alster | Wikidata | |
| Reported departure from San FranciscoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at San FranciscoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Former name: CSAV Rio Baker | Wikidata | |
| Former name: CCNI Arica | Wikidata |
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.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Wehr Alster | Former name | Jan 1, 2009 | Wikidata |
| CSAV Rio Baker | Former name | Jan 1, 2004 | Wikidata |
| CCNI Arica | Former name | Jan 1, 2002 | Wikidata |
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 Voydar saw them.
Source: Wikidata. Licence: CC0 1.0.
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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| San Francisco USSFO | Departure | Mar 12, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Arrival | Mar 12, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Mar 11, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Mar 11, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Dec 27, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Dec 27, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Dec 24, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Dec 24, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Nov 23, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Nov 23, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Oct 16, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 15, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 8, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is IMO 9232383 now?
- Voydar has no displayable AIS position for IMO 9232383 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 9232383?
- IMO 9232383 is a container ship, built in 2002 by P+S Werften. The vessel is 206 m long and has a gross tonnage of 25,630.
- What sanctions and inspection records does Voydar hold for IMO 9232383?
- Voydar has no matched sanctions record displayed for IMO 9232383 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 IMO 9232383. 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/9232383Using 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.