Skip to content

Pacific Sea

Bulk carrier · built 2004

IMO9293674No AIS position on record

In short

Pacific Sea (Bulk carrier) has no AIS position on record with Voydar. ISM manager: VULCANUS TECHNICAL MARITIME ENTERPRISES S.A. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Flag
—
Year built
2004
Gross tonnage
31,144
Size (length × beam)
190 m

Watch this ship

Pacific Sea 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.

Photo of Pacific Sea
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

No AIS position on record for this vessel. Identity and particulars are 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 Sea
IMO numberWhat is an IMO number?
9293674
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
31,144
Length overall
190 m
Beam
—
Year built
2004

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 Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from BeaumontAuthority-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
20182,804 t900 t31 days338 kg
20194,231 t1,347 t50 days309 kg
20202,325 t743 t29 days301 kg
20211,098 t346 t11 days365 kg
20221,833 t583 t23 days328 kg
20232,334 t741 t27 days351 kg
20240 t0 t0 days—
20250 t0 t0 days—

Technical efficiency: EEXI (4.27 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
Corpus Christi USCRPDepartureDec 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalDec 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTDepartureSep 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalSep 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureApr 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalApr 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureApr 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalMar 30, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPADepartureJun 26, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPAArrivalJun 25, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTDepartureMar 13, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalMar 5, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: December 2, 2004.

Frequently asked questions

Where is Pacific Sea now?
Voydar has no displayable AIS position for Pacific Sea in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Pacific Sea?
Pacific Sea is a bulk carrier, built in 2004 by Xiamen Shipbuilding Industry. The vessel is 190 m long and has a gross tonnage of 31,144.
Who is recorded as the owner or manager of Pacific Sea?
VULCANUS TECHNICAL MARITIME ENTERPRISES S.A. is recorded as ISM manager for Pacific Sea (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 Sea?
Voydar has no matched sanctions record displayed for Pacific Sea 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 Sea. 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/9293674
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