SKULD VII
Sailing vessel · Denmark · built 2010 · AIS Class B
In short
SKULD VII (Sailing vessel, Denmark flag) was last seen on AIS on , under way at 1.3 kn, near Helsingor (Baltic Sea).
- Vessel type
- Sailing vessel
- Flag
- Denmark
- Year built
- 2010
- Gross tonnage
- 641
- Size (length × beam)
- 33 m
- Registered owner
- —
Last reported position: 55.9915° N, 12.7431° E · Baltic Sea · See on the map
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.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 12:33 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for SKULD VII reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 55.9915° N, 12.7431° E
- Area
- Baltic Sea
- Status
- UndefinedWhat do AIS statuses mean?
- Speed
- 1.3 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
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. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 32.6 mone tick every 5 m
- Name
- SKULD VII
- IMO numberWhat is an IMO number?
- 9548354
- MMSIWhat is an MMSI?
- 219015003
- Call signWhat is a call sign?
- XPE2911
- Flag
- Denmark
- Vessel type
- Sailing vessel
- Gross tonnageGross tonnage vs deadweight
- 641
- Length overall
- 32.6 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.5 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.
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.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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.
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
| Date | Type | Port | Findings |
|---|---|---|---|
| Dec 9, 2010 | Vessel InspectionPSC | Honolulu, Hawaii | clean |
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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Honolulu USHNL | Departure | Dec 10, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Arrival | Dec 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.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
| When | What we observed | Confidence |
|---|---|---|
| Nov 20, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 75 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 19, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 73 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 18, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 75 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 9, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 150 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 18, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 105 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 17, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 109 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 16, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 109 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 15, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 109 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 14, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 158 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 13, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 229 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 12, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 125 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 11, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 122 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 10, 2026, 00:00 UTC | IMO used twice IMO 9548354 was broadcast by two ships (MMSI 219014875 and 219015003) 122 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 9, 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 8, 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 7, 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 6, 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 5, 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 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%) |
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.
Frequently asked questions
- 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.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Sailing vessels
Other sailing vessels with full Voydar profiles. A different set each day. All sailing vessels
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/9548354Cite this page
SKULD VII. Voydar (voydar.com). https://www.voydar.com/vessel/9548354-skuld-vii. Retrieved November 20, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.