PACIFIC TRACKER
Crane vessel · United States · built 1965 · AIS Class A
In short
PACIFIC TRACKER (Crane vessel, United States flag) was last seen on AIS on , moored, near Portland (North Pacific Ocean). Its crew-entered AIS destination is USPDX (Portland); its reported draught is 9.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:58 UTC).
- Vessel type
- Crane vessel
- Flag
- United States
- Year built
- 1965
- Gross tonnage
- 15,018
- Size (length × beam)
- 203 m
- Registered owner
- —
Watch this ship
Get an email when PACIFIC TRACKER 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 PACIFIC TRACKER.
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
- 45.5686° N, 122.7226° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 0°
- Heading
- 104°
Voydar detected no port call in the last 30 days.
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
- PACIFIC TRACKER
- IMO numberWhat is an IMO number?
- 6507921
- MMSIWhat is an MMSI?
- 368949000
- Call signWhat is a call sign?
- WQVZ
- Flag
- United States
- Vessel type
- Detailed type from WikidataCrane vessel
- AIS ship type
- Other
- Gross tonnageGross tonnage vs deadweight
- 15,018
- Length overall
- 203 m
- Beam
- —
- Year built
- 1965
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 |
|---|---|---|
| Reported departure from HonoluluAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HonoluluAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HonoluluAuthority-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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Honolulu USHNL | Departure | Aug 6, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Departure | Oct 5, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Departure | Sep 28, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Mar 29, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Departure | Nov 9, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 9, 2011.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
About PACIFIC TRACKER
SS Pacific Tracker is a United States Maritime Administration (MARAD) missile range instrumentation ship that monitors tests conducted by the Missile Defense Agency. It was formerly a crane ship named SS Beaver State (T-ACS-10) was named for the state of Oregon, which is also known as the Beaver State. As of 30 September, 2023, Pacific Tracker was listed in the National Defense Reserve Fleet, Pacific division assigned to Portland, OR.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is PACIFIC TRACKER now?
- PACIFIC TRACKER (Crane vessel, United States flag) was last seen on AIS on Oct 1, 2026, 20:52 UTC, moored, near Portland (North Pacific Ocean). The crew-entered destination was USPDX (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:58 UTC). This report does not confirm the ship’s current route.
- What kind of ship is PACIFIC TRACKER?
- PACIFIC TRACKER is a crane vessel sailing under the flag of United States, built in 1965 by Ingalls Shipbuilding. The vessel is 203 m long and has a gross tonnage of 15,018.
- What sanctions and inspection records does Voydar hold for PACIFIC TRACKER?
- Voydar has no matched sanctions record displayed for PACIFIC TRACKER 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 PACIFIC TRACKER. 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/6507921Using 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.