Skip to content

PACIFIC CONQUEST

Fishing vessel · United States · built 1985 · AIS Class B

IMO8600741MMSI367161930Call signWDD5675Last AIS position Oct 3, 2026, 01:47 UTC

In short

PACIFIC CONQUEST (Fishing vessel, United States flag) was last seen on AIS on , not moving, near Astoria (North Pacific Ocean).

Vessel type
Fishing vessel
Year built
1985
Gross tonnage
—
Size (length × beam)
15 m × 6 m
Registered owner
—

Watch this ship

Get an email when PACIFIC CONQUEST 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 CONQUEST.

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
46.1656° N, 123.9221° W
Area
North Pacific Ocean
Speed
0.2 kn
Course
240°
Heading
—
46.1656° N, 123.9221° W
Open the full live map →

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-up

Identity & particulars

Name
PACIFIC CONQUEST
IMO numberWhat is an IMO number?
8600741
MMSIWhat is an MMSI?
367161930
Call signWhat is a call sign?
WDD5675
Vessel type
Fishing vessel
AIS ship type
Fishing
Length overall
15 m
Beam
6 m

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.

No owner, operator or manager is recorded for this vessel yet.

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.

WhenWhat we observedConfidence
Oct 3, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,417 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 2, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,415 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 1, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,473 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 30, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,503 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 29, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,503 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 28, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,439 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 27, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,440 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 26, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,476 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 25, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,503 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 24, 2026, 00:00 UTC
IMO used twice

IMO 8600741 was broadcast by two ships (MMSI 367161930 and 503304000) 11,503 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)

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.

How these are computed →

Frequently asked questions

Where is PACIFIC CONQUEST now?
PACIFIC CONQUEST (Fishing vessel, United States flag) was last seen on AIS on Oct 3, 2026, 01:47 UTC, not moving, near Astoria (North Pacific Ocean).
What kind of ship is PACIFIC CONQUEST?
PACIFIC CONQUEST is a fishing vessel sailing under the flag of United States, built in 1985. The vessel is 15 m long with a beam of 6 m.
What sanctions and inspection records does Voydar hold for PACIFIC CONQUEST?
Voydar has no matched sanctions record displayed for PACIFIC CONQUEST 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 CONQUEST. 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/8600741
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans