Sonoma
Container ship · United States · built 1997 · AIS Class A
In short
Sonoma (Container ship, United States flag) was last seen on AIS on , not moving, near Sausalito (North Pacific Ocean). Its crew-entered AIS destination is XX XXX>US 0VC6; its reported draught is 2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 03:16 UTC).
Current voyage: from San Francisco (departed Oct 1, 2026, 03:24 UTC) to XX XXX>US 0VC6
- Vessel type
- Container ship
- Flag
- United States
- Year built
- 1997
- Gross tonnage
- 16,252
- Size (length × beam)
- 56 m × 10 m
- Registered owner
- —
Last reported position
received- Position
- 37.9454° N, 122.5086° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way sailing
- Speed
- 0 kn
- Course
- 252°
- Heading
- 318°
Last 30 days: 11 port calls (San Francisco and Tiburon).
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
- Sonoma
- IMO numberWhat is an IMO number?
- 9123520
- MMSIWhat is an MMSI?
- 366969970
- Call signWhat is a call sign?
- WZC8517
- Flag
- United States
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 16,252
- Deadweight (DWT)
- Source: Wikidata, record Q115573903. Added to Voydar on September 23, 2026. Licence: CC0 1.0.22,384 t
- Length overall
- 56 m
- Beam
- 10 m
- Year built
- 1997
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 |
|---|---|---|
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from OaklandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at OaklandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at Houston, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at Savannah, Georgia | USCG PSIX / CGMIX inspections | |
| Inspection at Savannah, Georgia | USCG PSIX / CGMIX inspections | |
| Inspection at Savannah, Georgia | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Jul 31, 2002 | Vessel Inspection | San Pedro, California | clean |
| Feb 9, 2002 | Vessel Inspection | San Pedro, California | clean |
| May 2, 2001 | Vessel Inspection | San Pedro, California | clean |
| Dec 6, 2000 | Vessel Inspection | San Pedro, California | clean |
| May 9, 2000 | Vessel Inspection | San Pedro, California | clean |
| Apr 14, 1999 | Vessel Inspection | Houston, Texas | clean |
| Nov 26, 1997 | Vessel Inspection | Savannah, Georgia | clean |
| May 15, 1997 | Vessel Transfer Monitor | Savannah, Georgia | clean |
| May 14, 1997 | Vessel Inspection | Savannah, Georgia | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 |
|---|---|---|---|
| San Francisco USSFO | Sep 30, 2026, 16:23 UTC | Oct 1, 2026, 03:24 UTC | 11 h 0 min |
| San Francisco USSFO | Sep 28, 2026, 17:01 UTC | Sep 29, 2026, 03:15 UTC | 10 h 14 min |
| San Francisco USSFO | Sep 27, 2026, 18:06 UTC | Sep 28, 2026, 00:57 UTC | 6 h 52 min |
| San Francisco USSFO | Sep 26, 2026, 16:57 UTC | Sep 27, 2026, 01:34 UTC | 8 h 36 min |
| San Francisco USSFO | Sep 25, 2026, 17:02 UTC | Sep 26, 2026, 03:21 UTC | 10 h 19 min |
| San Francisco USSFO | Sep 22, 2026, 18:23 UTC | Sep 23, 2026, 03:18 UTC | 8 h 55 min |
| Tiburon USXTN | Sep 17, 2026, 23:48 UTC | Sep 18, 2026, 01:07 UTC | 1 h 19 min |
| Tiburon USXTN | Sep 15, 2026, 17:59 UTC | Sep 15, 2026, 23:35 UTC | 5 h 36 min |
| Tiburon USXTN | Sep 14, 2026, 23:41 UTC | Sep 15, 2026, 00:51 UTC | 1 h 10 min |
| Tiburon USXTN | Sep 14, 2026, 18:46 UTC | Sep 14, 2026, 23:38 UTC | 4 h 52 min |
| Tiburon USXTN | Sep 6, 2026, 21:48 UTC | Sep 6, 2026, 22:32 UTC | 44 min |
| Tiburon USXTN | Sep 2, 2026, 19:48 UTC | Sep 2, 2026, 20:37 UTC | 49 min |
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 |
|---|---|---|---|---|
| Oakland USOAK | Departure | Sep 8, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Sep 8, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Sep 6, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Sep 6, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Aug 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Aug 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Jul 31, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Jul 30, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Jul 1, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Jun 29, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Departure | Jun 27, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Arrival | Jun 27, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 8, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Sep 22, 2026, 02:48 UTC | AIS gap No AIS position received for 10 h 19 min while our receivers kept hearing other ships there (8 of 10 hours in coverage). Heard again 10 km away. Method seadar.behaviour.ais_gap v1 | High (84%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- Where is Sonoma now?
- Sonoma (Container ship, United States flag) was last seen on AIS on Oct 3, 2026, 03:40 UTC, not moving, near Sausalito (North Pacific Ocean). The crew-entered destination was XX XXX>US 0VC6 (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 03:16 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Sonoma?
- Sonoma is a container ship sailing under the flag of United States, built in 1997 by Szczecin Shipyard. The vessel is 56 m long with a beam of 10 m and has a gross tonnage of 16,252.
- What sanctions and inspection records does Voydar hold for Sonoma?
- Voydar has no matched sanctions record displayed for Sonoma 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. Sonoma has 9 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9123520Using 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.