Skip to content

Crimson Kingdom

Bulk carrier · Singapore · built 2016 · AIS Class A

IMO9748033MMSI564895000Call sign9V3468Last AIS position Oct 6, 2026, 13:21 UTC

In short

Crimson Kingdom (Bulk carrier, Singapore flag) was last seen on AIS on , moored, near Gent (Ghent) (North Sea). Its crew-entered AIS destination is BE GNE (Gent (Ghent)); its reported draught is 12.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:48 UTC). ISM manager: MARUFLEET MANAGEMENT PTE. LTD. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Terneuzen (departed Oct 2, 2026, 19:08 UTC) to BE GNE (Gent (Ghent))

Vessel type
Bulk carrier
Year built
2016
Gross tonnage
45,223
Size (length × beam)
229 m × 35 m

Watch this ship

Get an email when Crimson Kingdom reaches Gent (Ghent), and when it 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 CRIMSON KINGDOM
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
51.1749° N, 3.7998° E
Area
North Sea
Speed
0.2 kn
Course
13°
Heading
203°
51.1749° N, 3.7998° E
Open the full live map →

Last 30 days: 2 port calls (Terneuzen and Nieuwdorp).

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
Crimson Kingdom
IMO numberWhat is an IMO number?
9748033
MMSIWhat is an MMSI?
564895000
Call signWhat is a call sign?
9V3468
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
45,223
Length overall
228.9 m
Beam
35 m
Year built
2016

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
Left TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Left NieuwdorpAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at NieuwdorpAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from PORT OF KALAMA, WAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at AstoriaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PORT OF KALAMA, WAAuthority-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
20183,696 t1,184 t50 days276 kg
20194,140 t1,323 t91 days284 kg
20208,518 t2,706 t117 days269 kg
202110,654 t3,394 t136 days272 kg
20229,910 t3,139 t139 days253 kg
20235,908 t1,865 t72 days312 kg
20248,358 t2,661 t107 days288 kg
20255,852 t1,867 t83 days264 kg

Technical efficiency: EEDI (3.4 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Terneuzen NLTNZOct 2, 2026, 17:24 UTCOct 2, 2026, 19:08 UTC1 h 44 min
Nieuwdorp NLNIUOct 1, 2026, 05:06 UTCOct 2, 2026, 16:35 UTC35 h 29 min

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
PORT OF KALAMA, WADepartureNov 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalNov 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WADepartureAug 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalAug 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WADepartureJun 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalJun 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WADepartureApr 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalApr 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 15, 2016.

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 2, 2026, 14:30 UTC
Draught change

Reported draught went from 14.4 m to 12.3 m while in port at Nieuwdorp. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)

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 Crimson Kingdom now?
Crimson Kingdom (Bulk carrier, Singapore flag) was last seen on AIS on Oct 6, 2026, 13:21 UTC, moored, near Gent (Ghent) (North Sea). The crew-entered destination was BE GNE (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:48 UTC). This report does not confirm the ship’s current route.
What kind of ship is Crimson Kingdom?
Crimson Kingdom is a bulk carrier sailing under the flag of Singapore, built in 2016 by Imabari Shipbuilding. The vessel is 228.9 m long with a beam of 35 m and has a gross tonnage of 45,223.
Who is recorded as the owner or manager of Crimson Kingdom?
MARUFLEET MANAGEMENT PTE. LTD. is recorded as ISM manager for Crimson Kingdom (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 Crimson Kingdom?
Voydar has no matched sanctions record displayed for Crimson Kingdom 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 Crimson Kingdom. 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/9748033
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