Skip to content

Crimson Knight

Bulk carrier · Singapore · built 2013 · AIS Class A

IMO9638836MMSI566715000Call sign9V9733Last AIS position Sep 22, 2026, 23:50 UTC

In short

Crimson Knight (Bulk carrier, Singapore flag) was last seen on AIS on , under way at 8.9 kn, in the South China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.

Vessel type
Bulk carrier
Year built
2013
Gross tonnage
33,193
Size (length × beam)
197 m × 32 m
Registered owner
—

Watch this ship

Crimson Knight 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
14.4555° N, 120.717° E
Area
South China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
8.9 kn
Course
211°
Heading
209°
14.4555° N, 120.717° 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
Crimson Knight
IMO numberWhat is an IMO number?
9638836
MMSIWhat is an MMSI?
566715000
Call signWhat is a call sign?
9V9733
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
33,193
Length overall
197 m
Beam
32 m
Year built
2013

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.

No owner, operator or manager is recorded for this vessel yet.

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 PORT OF KALAMA, WAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at AstoriaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Baton RougeAuthority-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
20180 t0 t0 days—

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
PORT OF KALAMA, WADepartureApr 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalApr 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRDepartureAug 14, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalAug 12, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Newport News USNNSDepartureMay 1, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Newport News USNNSArrivalMay 1, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Boston USBOSDepartureApr 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Boston USBOSArrivalApr 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMDepartureJan 23, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMArrivalJan 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureJul 18, 2013(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJul 15, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 27, 2013.

Frequently asked questions

Where is Crimson Knight now?
Crimson Knight (Bulk carrier, Singapore flag) was last seen on AIS on Sep 22, 2026, 23:50 UTC, under way at 8.9 kn, in the South China 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 Crimson Knight?
Crimson Knight is a bulk carrier sailing under the flag of Singapore, built in 2013. The vessel is 197 m long with a beam of 32 m and has a gross tonnage of 33,193.
What sanctions and inspection records does Voydar hold for Crimson Knight?
Voydar has no matched sanctions record displayed for Crimson Knight 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 Knight. 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/9638836
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