Skip to content

SEA1 SAPPHIRE

Cargo ship · Norway · built 2010 · AIS Class A

IMO9417696MMSI257544000Call signLDTO3Last AIS position Sep 30, 2026, 07:47 UTC

In short

SEA1 SAPPHIRE (Cargo ship, Norway flag) was last seen on AIS on , under way at 10 kn, near Keelung (Chilung) (East China Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is OPEN SEA; its reported draught is 7 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 06:43 UTC). Its last detected port call was at Keelung (Chilung): arrived Sep 28, 2026, left Sep 30, 2026.

Vessel type
Cargo ship
Flag
Norway
Year built
2010
Gross tonnage
7,473
Size (length × beam)
91 m
Registered owner
—

Watch this ship

SEA1 SAPPHIRE 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 SEA1 SAPPHIRE
Photo: Alan Jamieson from Aberdeen, Scotland · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
25.2484° N, 121.9703° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10 kn
Course
81°
Heading
85°
25.2484° N, 121.9703° E
Open the full live map →

Last 30 days: 1 port call (Keelung (Chilung)).

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
SEA1 SAPPHIRE
IMO numberWhat is an IMO number?
9417696
MMSIWhat is an MMSI?
257544000
Call signWhat is a call sign?
LDTO3
Flag
Norway
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
7,473
Length overall
91 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.

Registered owner
Q107472717(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
Siem AHTS Pool AS(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 2026
Operator
Q107472865(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
Siem Offshore AS(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 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 Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Former name: Siem PearlWikidata
Former name: Siem SapphireWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
Siem PearlFormer nameJan 1, 2010Wikidata
Siem SapphireFormer nameJan 1, 2009Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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
Keelung (Chilung) TWKELSep 28, 2026, 23:58 UTCSep 30, 2026, 06:57 UTC30 h 59 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.

Frequently asked questions

Where is SEA1 SAPPHIRE now?
SEA1 SAPPHIRE (Cargo ship, Norway flag) was last seen on AIS on Sep 30, 2026, 07:47 UTC, under way at 10 kn, near Keelung (Chilung) (East China Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was OPEN SEA (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 06:43 UTC). This report does not confirm the ship’s current route.
What kind of ship is SEA1 SAPPHIRE?
SEA1 SAPPHIRE is a cargo ship sailing under the flag of Norway, built in 2010 by Kleven Verft. The vessel is 91 m long and has a gross tonnage of 7,473.
What sanctions and inspection records does Voydar hold for SEA1 SAPPHIRE?
Voydar has no matched sanctions record displayed for SEA1 SAPPHIRE 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 SEA1 SAPPHIRE. 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/9417696
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