Vikingbank
General cargo ship · Netherlands · built 2012 · AIS Class A
In short
Vikingbank (General cargo ship, Netherlands flag) was last seen on AIS on , not moving, near Gandia (Mediterranean Sea). Its crew-entered AIS destination is GANDIA, with an ETA of Nov 17, 2026, 15:00 UTC; its reported draught is 5.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 04:45 UTC).
Current voyage: from Sandvik, Styrso (departed Nov 7, 2026, 12:23 UTC) to GANDIA
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2012
- Gross tonnage
- 7,367
- Size (length × beam)
- 143 m × 16 m
- Registered owner
- —

Last reported position: 38.9939° N, 0.1498° W · Mediterranean Sea · See on the map
Watch this ship
Get an email when Vikingbank 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 17, 2026, 19:06 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Vikingbank 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: Voydar for iPhone
Last reported position
received- Position
- 38.9939° N, 0.1498° W
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0.4 kn
- Course
- 151°
- Heading
- 331°
- Compass: course over ground 151°, heading 331°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 4 port calls (Sandvik, Styrso, Sunila, and Oulu (Uleaborg)).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Vikingbank's track before the last 30 days. Voydar has recorded its port calls since September 3, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 142.7 mone tick every 25 m
Beam 15.9 mPlan outline, to scale
- Name
- Vikingbank
- IMO numberWhat is an IMO number?
- 9604184
- MMSIWhat is an MMSI?
- 244855000
- Call signWhat is a call sign?
- PCOR
- Flag
- Netherlands
- Vessel type
- General cargo ship
- Gross tonnageGross tonnage vs deadweight
- 7,367
- Length overall
- 142.7 m
- Beam
- 15.9 m
- Year built
- 2012
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 · high confidence · retrieved Nov 15, 2026FERUS SMIT B.V(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 2026
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.
| Date | Event | Source |
|---|---|---|
| Left Sandvik, StyrsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Sandvik, StyrsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SunilaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from KotkaAuthority-reported | Digitraffic Port Call API | |
| Reported arrival at KotkaAuthority-reported | Digitraffic Port Call API | |
| Arrived at SunilaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Oulu (Uleaborg)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Oulu (Uleaborg)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Oulu (Uleaborg)Authority-reported | Digitraffic Port Call API | |
| Arrived at Oulu (Uleaborg)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from ECORSE, MI (INCLUDED IN PORT OF DETROIT)Authority-reported | USACE 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 6,659 t | 2,108 t | 191 days | 155 kg |
| 2019 | 7,164 t | 2,260 t | 244 days | 152 kg |
| 2020 | 6,932 t | 2,185 t | 175 days | 157 kg |
| 2021 | 8,376 t | 2,631 t | 190 days | 156 kg |
| 2022 | 6,575 t | 2,062 t | 168 days | 133 kg |
| 2023 | 6,632 t | 2,083 t | 175 days | 148 kg |
| 2024 | 6,215 t | 1,944 t | 169 days | 149 kg |
| 2025 | 6,579 t | 2,147 t | 193 days | 132 kg |
Technical efficiency: EEXI (10.3 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed132.5 kg per nautical mile
- Lowest reportedHighest reported
61% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Sandvik, Styrso SESTR | Nov 7, 2026, 07:01 UTC | Nov 7, 2026, 12:23 UTC | 5 h 22 min |
| Sunila FISUL | Oct 30, 2026, 16:45 UTC | Nov 4, 2026, 13:23 UTC | 4 d 20 h |
| Oulu (Uleaborg) FIOUL | Oct 23, 2026, 16:18 UTC | Oct 28, 2026, 12:58 UTC | 4 d 20 h |
| Sandvik, Styrso SESTR | Oct 19, 2026, 19:37 UTC | Oct 19, 2026, 22:05 UTC | 2 h 27 min |
| Heroya NOHRY | Oct 16, 2026, 16:55 UTC | Oct 19, 2026, 10:22 UTC | 2 d 17 h |
| Europoort NLEUR | Oct 12, 2026, 17:07 UTC | Oct 14, 2026, 15:20 UTC | 46 h 13 min |
| Rotterdam NLRTM | Oct 7, 2026, 20:30 UTC | Oct 12, 2026, 15:28 UTC | 4 d 18 h |
| Blyth GBBLY | Oct 4, 2026, 09:08 UTC | Oct 6, 2026, 07:44 UTC | 46 h 36 min |
| Ceuta ESCEU | Sep 22, 2026, 05:26 UTC | Sep 22, 2026, 18:46 UTC | 13 h 19 min |
| Gandia ESGAN | Sep 15, 2026, 16:30 UTC | Sep 15, 2026, 17:20 UTC | 50 min |
| Kiel DEKEL | Sep 3, 2026, 22:16 UTC | Sep 15, 2026, 16:30 UTC | 11 d 18 h |
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 |
|---|---|---|---|---|
| Kotka FIKTK | Arrival | Oct 30, 2026, 17:15 UTC | HIEH6 | Digitraffic Port Call API |
| Oulu (Uleaborg) FIOUL | Arrival | Oct 23, 2026, 16:35 UTC | 302 | Digitraffic Port Call API |
| ECORSE, MI (INCLUDED IN PORT OF DETROIT) | Departure | Dec 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ECORSE, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Dec 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Departure | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Departure | Oct 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Arrival | Oct 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Arrival | May 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Departure | May 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BURNS WATERWAY HARBOR, IN | Departure | May 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BURNS WATERWAY HARBOR, IN | Arrival | May 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: June 27, 2012.
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 28, 2026, 04:02 UTC | Draught change Reported draught went from 8.2 m to 4.8 m while in port at Oulu (Uleaborg). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 19, 2026, 09:19 UTC | Draught change Reported draught went from 8.2 m to 4.8 m while in port at Heroya. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 17, 2026, 17:21 UTC | Draught change Reported draught went from 4.8 m to 8.2 m while in port at Heroya. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 14, 2026, 14:48 UTC | Draught change Reported draught went from 4.8 m to 8.2 m while in port at Europoort. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 9, 2026, 15:23 UTC | Draught change Reported draught went from 6.6 m to 4.8 m while in port at Rotterdam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 6, 2026, 07:13 UTC | Draught change Reported draught went from 6.6 m to 4.8 m while in port at Blyth. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Source: BarentsWatch AIS API. Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket). Licence: NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD).
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 Vikingbank?
- Vikingbank is a general cargo ship sailing under the flag of Netherlands, built in 2012 by Ferus Smit. The vessel is 142.7 m long with a beam of 15.9 m and has a gross tonnage of 7,367.
- What sanctions and inspection records does Voydar hold for Vikingbank?
- Voydar has no matched sanctions record displayed for Vikingbank 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 Vikingbank. Missing records do not establish whether the ship has been detained.
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
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/9604184Cite this page
Vikingbank. Voydar (voydar.com). https://www.voydar.com/vessel/9604184-vikingbank. Retrieved November 17, 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.