WSF CHIMACUM
Passenger ship · United States · built 2017 · AIS Class A
In short
WSF CHIMACUM (Passenger ship, United States flag) was last seen on AIS on , under way at 11.4 kn, near Seattle (North Pacific Ocean). Its reported AIS draught is 7.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 07:21 UTC). Its last detected port call was at Seattle: arrived Oct 4, 2026, left Oct 4, 2026.
- Vessel type
- Passenger ship
- Flag
- United States
- Year built
- 2017
- Gross tonnage
- —
- Size (length × beam)
- 110 m × 25 m
- Registered owner
- —
Watch this ship
Get an email when WSF CHIMACUM 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 WSF CHIMACUM.
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
- 47.6017° N, 122.3533° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.4 kn
- Course
- 272°
- Heading
- 272°
Last 30 days: at least 12 port calls (Seattle and Bremerton).
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
- WSF CHIMACUM
- IMO numberWhat is an IMO number?
- 9801770
- MMSIWhat is an MMSI?
- 367712660
- Call signWhat is a call sign?
- WDI5854
- Flag
- United States
- Vessel type
- Passenger ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 110 m
- Beam
- 25 m
- Year built
- 2017
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 SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BremertonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BremertonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SeattleAIS-detected | Voydar port-call detector (AIS geofence) |
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 |
|---|---|---|---|
| Seattle USSEA | Oct 4, 2026, 05:08 UTC | Oct 4, 2026, 06:02 UTC | 54 min |
| Bremerton USPWT | Oct 4, 2026, 03:48 UTC | Oct 4, 2026, 04:28 UTC | 39 min |
| Seattle USSEA | Oct 4, 2026, 00:15 UTC | Oct 4, 2026, 00:57 UTC | 42 min |
| Bremerton USPWT | Oct 3, 2026, 22:50 UTC | Oct 3, 2026, 23:33 UTC | 42 min |
| Seattle USSEA | Oct 3, 2026, 21:33 UTC | Oct 3, 2026, 22:18 UTC | 45 min |
| Seattle USSEA | Oct 3, 2026, 14:18 UTC | Oct 3, 2026, 15:03 UTC | 44 min |
| Bremerton USPWT | Oct 3, 2026, 08:52 UTC | Oct 3, 2026, 13:38 UTC | 4 h 45 min |
| Seattle USSEA | Oct 3, 2026, 04:57 UTC | Oct 3, 2026, 06:00 UTC | 1 h 3 min |
| Bremerton USPWT | Oct 2, 2026, 22:51 UTC | Oct 2, 2026, 23:40 UTC | 50 min |
| Seattle USSEA | Oct 2, 2026, 21:30 UTC | Oct 2, 2026, 22:22 UTC | 52 min |
| Seattle USSEA | Oct 2, 2026, 16:47 UTC | Oct 2, 2026, 17:28 UTC | 41 min |
| Bremerton USPWT | Oct 2, 2026, 15:31 UTC | Oct 2, 2026, 16:05 UTC | 34 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.
About WSF CHIMACUM
MV Chimacum is the third vessel of the Olympic-class auto ferries for the Washington State Ferries system. The ship was built by Vigor Industrial at their shipyard in Seattle, Washington and entered service on the Seattle–Bremerton route in 2017.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is WSF CHIMACUM now?
- WSF CHIMACUM (Passenger ship, United States flag) was last seen on AIS on Oct 4, 2026, 07:56 UTC, under way at 11.4 kn, near Seattle (North Pacific Ocean).
- What kind of ship is WSF CHIMACUM?
- WSF CHIMACUM is a passenger ship sailing under the flag of United States, built in 2017 by Vigor Marine Group. The vessel is 110 m long with a beam of 25 m.
- What sanctions and inspection records does Voydar hold for WSF CHIMACUM?
- Voydar has no matched sanctions record displayed for WSF CHIMACUM 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 WSF CHIMACUM. 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/9801770Using 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.