Skip to content

SKULD VII

Sailing vessel · Denmark · built 2010 · AIS Class B

IMO9548354MMSI219015003Call signXPE2911Last AIS position Oct 4, 2026, 22:09 UTC

In short

SKULD VII (Sailing vessel, Denmark flag) was last seen on AIS on , not moving, near Helsingor (Baltic Sea).

Vessel type
Sailing vessel
Year built
2010
Gross tonnage
641
Size (length × beam)
33 m
Registered owner
—

Watch this ship

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

We email you a link and a code. That creates a free account, no password or card, and follows SKULD VII.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Photo of SVITZER TRYM
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
56.0426° N, 12.6138° E
Area
Baltic Sea
Speed
0.4 kn
Course
—
Heading
—
56.0426° N, 12.6138° 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)

Try the live demo, no sign-up

Identity & particulars

Name
SKULD VII
IMO numberWhat is an IMO number?
9548354
MMSIWhat is an MMSI?
219015003
Call signWhat is a call sign?
XPE2911
Vessel type
Sailing vessel
AIS ship type
Sailing
Length overall
32.6 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.

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 HonoluluAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Port State Control inspection at Honolulu, HawaiiUSCG PSIX / CGMIX inspections
Reported arrival at HonoluluAuthority-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.

Safety & inspections

1
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Dec 9, 2010Vessel InspectionPSCHonolulu, Hawaiiclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
Honolulu USHNLDepartureDec 10, 2010(date only)—USACE foreign traffic vessel entrances & clearances
Honolulu USHNLArrivalDec 9, 2010(date only)—USACE foreign traffic vessel entrances & clearances

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

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 4, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 3, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 2, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 1, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 30, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 29, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 103 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 28, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 113 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 27, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 69 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 26, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 69 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Sep 25, 2026, 00:00 UTC
IMO used twice

IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 64 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)

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 SKULD VII now?
SKULD VII (Sailing vessel, Denmark flag) was last seen on AIS on Oct 4, 2026, 22:09 UTC, not moving, near Helsingor (Baltic Sea).
What kind of ship is SKULD VII?
SKULD VII is a sailing vessel sailing under the flag of Denmark, built in 2010. The vessel is 32.6 m long and has a gross tonnage of 641.
What sanctions and inspection records does Voydar hold for SKULD VII?
Voydar has no matched sanctions record displayed for SKULD VII 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. SKULD VII has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.

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/9548354
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