Skip to content

XING FU HAI

Bulk carrier · Singapore · AIS Class A

IMO9949302MMSI563174700Call sign9V8307Last AIS position Oct 6, 2026, 11:28 UTC

In short

XING FU HAI (Bulk carrier, Singapore flag) was last seen on AIS on , moored, in the South Pacific Ocean. Its crew-entered AIS destination is NEWCASTLE; its reported draught is 7.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:15 UTC). ISM manager: Dalian Hairun Ship Management Co.,Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Year built
—
Gross tonnage
—
Size (length × beam)
—

Watch this ship

Get an email when XING FU HAI arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

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

Photo of IMO 9949302
Photo: CP842c · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
32.887° S, 151.7648° E
Area
South Pacific Ocean
Speed
0 kn
Course
357°
Heading
110°
32.887° S, 151.7648° E
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
XING FU HAI
IMO numberWhat is an IMO number?
9949302
MMSIWhat is an MMSI?
563174700
Call signWhat is a call sign?
9V8307
AIS ship type
Cargo
Length overall
—
Beam
—
Year built
—

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

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 Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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
20235,058 t1,618 t65 days288 kg
20241,056 t338 t12 days286 kg
20255,034 t1,609 t70 days271 kg

Technical efficiency: EEXI (3.22 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
Hong Kong HKHKGArrivalMar 29, 2026, 16:24 UTCCLPHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalOct 17, 2025, 12:50 UTCSOUTH EAST LAMMA ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jun 16, 2024, 13:40 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: June 16, 2024.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Frequently asked questions

Where is XING FU HAI now?
XING FU HAI (Bulk carrier, Singapore flag) was last seen on AIS on Oct 6, 2026, 11:28 UTC, moored, in the South Pacific Ocean. The crew-entered destination was NEWCASTLE (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:15 UTC). This report does not confirm the ship’s current route.
What kind of ship is XING FU HAI?
XING FU HAI is a bulk carrier sailing under the flag of Singapore.
Who is recorded as the owner or manager of XING FU HAI?
Dalian Hairun Ship Management Co.,Ltd. is recorded as ISM manager for XING FU HAI (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 XING FU HAI?
Voydar has no matched sanctions record displayed for XING FU HAI 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 XING FU HAI. 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/9949302
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