Skip to content

PACIFIC EGRET

Cargo ship · United Kingdom · built 2010 · AIS Class A

IMO9464871MMSI235076846Call sign2CYF9Last AIS position Sep 6, 2026, 00:43 UTC

In short

PACIFIC EGRET (Cargo ship, United Kingdom flag) was last seen on AIS on , moored, near Barrow in Furness (Irish Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. ISM manager: AW SHIP MANAGEMENT LIMITED (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Cargo ship
Year built
2010
Gross tonnage
6,776
Size (length × beam)
104 m

Watch this ship

PACIFIC EGRET has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
54.0998° N, 3.2124° W
Area
Irish Sea
Speed
0 kn
Course
350°
Heading
62°
54.0998° N, 3.2124° 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
PACIFIC EGRET
IMO numberWhat is an IMO number?
9464871
MMSIWhat is an MMSI?
235076846
Call signWhat is a call sign?
2CYF9
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
6,776
Length overall
103.9 m
Beam
—
Year built
2010

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 years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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.

DateEventSource
Reported departure from CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from CharlestonAuthority-reportedUSACE 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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20192,640 t823 t50 days196 kg
2020706 t220 t13 days203 kg
20223,892 t1,214 t76 days184 kg
20232,036 t635 t64 days130 kg
20240 t0 t0 days—
20250 t0 t0 days—

Technical efficiency: EIV (33.84 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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

PortRecordDate (UTC)BerthSource
Charleston USCHSDepartureJun 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalJun 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSDepartureMar 19, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalMar 19, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSDepartureFeb 6, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalFeb 6, 2014(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 6, 2014.

About PACIFIC EGRET

Pacific Egret is an INF Class 3 nuclear waste carrier launched in January 2010.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is PACIFIC EGRET now?
PACIFIC EGRET (Cargo ship, United Kingdom flag) was last seen on AIS on Sep 6, 2026, 00:43 UTC, moored, near Barrow in Furness (Irish Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is PACIFIC EGRET?
PACIFIC EGRET is a cargo ship sailing under the flag of United Kingdom, built in 2010 by Mitsui Tamano Shipyard. The vessel is 103.9 m long and has a gross tonnage of 6,776.
Who is recorded as the owner or manager of PACIFIC EGRET?
AW SHIP MANAGEMENT LIMITED is recorded as ISM manager for PACIFIC EGRET (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for PACIFIC EGRET?
Voydar has no matched sanctions record displayed for PACIFIC EGRET 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 EGRET. 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/9464871
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