Frakt Vik
Cargo ship · Cyprus · built 2010 · AIS Class A
In short
Frakt Vik (Cargo ship, Cyprus flag) was last seen on AIS on , under way at 11.2 kn, in the Baltic Sea. Its crew-entered AIS destination is VIEROW, with an ETA of Oct 7, 2026, 06:00 UTC; its reported draught is 4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 21:13 UTC).
Current voyage: from Herre (departed Oct 5, 2026, 16:38 UTC) to VIEROW
- Vessel type
- Cargo ship
- Flag
- Cyprus
- Year built
- 2010
- Gross tonnage
- 2,999
- Size (length × beam)
- 90 m × 14 m
- Registered owner
- —
Watch this ship
Get an email when Frakt Vik arrives or 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.

Last reported position
received- Position
- 58.2478° N, 10.6298° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.2 kn
- Course
- 156°
- Heading
- 153°
Last 30 days: 2 port calls (Herre and Orkanger).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Frakt Vik's track before the last 30 days. Voydar has recorded its port calls since August 5, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Frakt Vik
- IMO numberWhat is an IMO number?
- 9356579
- MMSIWhat is an MMSI?
- 212979000
- Call signWhat is a call sign?
- 5BKU4
- Flag
- Cyprus
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 2,999
- Length overall
- 90 m
- Beam
- 14.4 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.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- 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.
| Date | Event | Source |
|---|---|---|
| Left HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HerreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left OrkangerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at OrkangerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TromsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TromsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at North Charleston, South Carolina | USCG PSIX / CGMIX inspections | |
| Reported departure from CharlestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at CharlestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from WilmingtonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at Houston, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at TEXAS CITY, Texas | USCG PSIX / CGMIX inspections |
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 |
|---|---|---|---|
| Mar 12, 2014 | Vessel InspectionPSC | North Charleston, South Carolina | clean |
| Apr 29, 2011 | Vessel InspectionPSC | Houston, Texas | clean |
| Apr 28, 2011 | Boarding | TEXAS CITY, Texas | 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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Herre NOHRR | Oct 2, 2026, 21:29 UTC | Oct 5, 2026, 16:38 UTC | 2 d 19 h |
| Orkanger NOORK | Sep 29, 2026, 15:08 UTC | Sep 30, 2026, 13:33 UTC | 22 h 25 min |
| Tromso NOTOS | Aug 5, 2026, 20:00 UTC | Aug 6, 2026, 04:28 UTC | 8 h 28 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Charleston USCHS | Departure | Mar 12, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Mar 11, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILM | Departure | May 8, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILM | Arrival | May 7, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | May 1, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Apr 28, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 28, 2011.
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 |
|---|---|---|
| Oct 5, 2026, 14:18 UTC | Draught change Reported draught went from 5.2 m to 4 m while in port at Herre. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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
- Where is Frakt Vik now?
- Frakt Vik (Cargo ship, Cyprus flag) was last seen on AIS on Oct 5, 2026, 22:21 UTC, under way at 11.2 kn, in the Baltic Sea. The crew-entered destination was VIEROW (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 21:13 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Frakt Vik?
- Frakt Vik is a cargo ship sailing under the flag of Cyprus, built in 2010 by Veka Shipyard Lemmer. The vessel is 90 m long with a beam of 14.4 m and has a gross tonnage of 2,999.
- What sanctions and inspection records does Voydar hold for Frakt Vik?
- Voydar has no matched sanctions record displayed for Frakt Vik 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. Frakt Vik has 3 recorded Port State Control inspections. 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/9356579Using 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.