Pacific Discovery
Fishing vessel · Canada · built 2014 · AIS Class A
In short
Pacific Discovery (Fishing vessel, Canada flag) was last seen on AIS on , not moving, near New Westminster (North Pacific Ocean). Its last detected port call was at Robert's Bank: arrived Aug 22, 2026, left Oct 17, 2026. ISM manager: Tidewater Marine UK Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Fishing vessel
- Flag
- Canada
- Year built
- 2014
- Gross tonnage
- 6,641
- Size (length × beam)
- 19 m × 7 m
- ISM manager
- Tidewater Marine UK Ltd
Last reported position: 49.0856° N, 123.1099° W · North Pacific Ocean · See on the map
Watch this ship
Get an email when Pacific Discovery arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 18, 2026, 18:50 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Pacific Discovery reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 49.0856° N, 123.1099° W
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
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.
Pro shows Pacific Discovery's track before the last 30 days. Voydar has recorded its port calls since June 13, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 19 mone tick every 2 m
Beam 7 mPlan outline, to scale
- Name
- Pacific Discovery
- IMO numberWhat is an IMO number?
- 9456202
- MMSIWhat is an MMSI?
- 316004787
- Call signWhat is a call sign?
- MREA9
- Flag
- Canada
- Vessel type
- Fishing vessel
- Gross tonnageGross tonnage vs deadweight
- 6,641
- Deadweight (DWT)
- Source: Wikidata, record Q84256652. Added to Voydar on November 14, 2026. Licence: CC0 1.0.4,449 t
- Length overall
- 19 m
- Beam
- 7 m
- Year built
- 2014
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 Robert's BankAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Robert's BankAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Robert's BankAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Robert's BankAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Prince RupertAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Prince RupertAIS-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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2025 | 8,354 t | 2,606 t | 125 days | 482 kg |
Technical efficiency: Not Applicable. Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Other ship types (Offshore)”. Lower is less CO₂.
- CO₂ per nautical mile sailed482 kg per nautical mile
- Lowest reportedHighest reported
64% of the 582 ships in this group reported a lower figure.
Group: lower quartile 197 · median 341.3 · upper quartile 630.9
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Robert's Bank CARTB | Aug 22, 2026, 19:45 UTC | Oct 17, 2026, 23:10 UTC | 56 d 3 h |
| Robert's Bank CARTB | Aug 17, 2026, 10:31 UTC | Aug 18, 2026, 22:07 UTC | 35 h 37 min |
| Prince Rupert CAPRR | Aug 3, 2026, 06:13 UTC | Aug 17, 2026, 10:31 UTC | 14 d 4 h |
| Prince Rupert CAPRR | Jul 27, 2026, 21:00 UTC | Jul 28, 2026, 19:27 UTC | 22 h 27 min |
| Prince Rupert CAPRR | Jul 18, 2026, 17:27 UTC | Jul 23, 2026, 22:15 UTC | 5 d 4 h |
| Port Simpson CAPSI | Jul 15, 2026, 20:18 UTC | Jul 17, 2026, 13:31 UTC | 41 h 13 min |
| Prince Rupert CAPRR | Jul 9, 2026, 23:20 UTC | Jul 11, 2026, 17:32 UTC | 42 h 13 min |
| Prince Rupert CAPRR | Jul 4, 2026, 21:07 UTC | Jul 6, 2026, 02:01 UTC | 28 h 54 min |
| Robert's Bank CARTB | Jun 13, 2026, 00:23 UTC | Jun 25, 2026, 12:20 UTC | 12 d 11 h |
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.
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 |
|---|---|---|
| Nov 18, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 17, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,869 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 16, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,869 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 15, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,869 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 14, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 13, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 12, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 11, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 10, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 9, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 8, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 6, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 4, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 3, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 2, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 1, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,872 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 31, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 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 30, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 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 28, 2026, 00:00 UTC | IMO used twice IMO 9456202 was broadcast by two ships (MMSI 232057812 and 316004787) 8,873 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.
Frequently asked questions
- What kind of ship is Pacific Discovery?
- Pacific Discovery is a fishing vessel sailing under the flag of Canada, built in 2014. The vessel is 19 m long with a beam of 7 m and has a gross tonnage of 6,641.
- Who is recorded as the owner or manager of Pacific Discovery?
- Tidewater Marine UK Ltd is recorded as ISM manager for Pacific Discovery (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Pacific Discovery?
- Voydar has no matched sanctions record displayed for Pacific Discovery 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 Pacific Discovery. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
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/9456202Cite this page
Pacific Discovery. Voydar (voydar.com). https://www.voydar.com/vessel/9456202-pacific-discovery. Retrieved November 18, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.