Skip to content
voydar.com

Vikingbank

General cargo ship · Netherlands · built 2012 · AIS Class A

IMO9604184MMSI244855000Call signPCORLast AIS position Nov 17, 2026, 15:36 UTC

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

Data: AISHub contributors

Year built
2012
Gross tonnage
7,367
Size (length × beam)
143 m × 16 m
Registered owner
—
Photo of VIKINGBANK
Photo: Leo Johannes · Licence: CC BY-SA 4.0 · via Wikimedia Commons

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°
NArrow: course. Hull: heading. As broadcast on AIS.
38.9939° N, 0.1498° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
38.9939° N, 0.1498° W
See it live in 3D →

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.

Data: AISHub contributors

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-up

Identity & particulars

Length overall 142.7 mone tick every 25 m

Beam 15.9 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
Vikingbank
IMO numberWhat is an IMO number?
9604184
MMSIWhat is an MMSI?
244855000
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, 2026
FERUS 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.

DateEventSource
Left Sandvik, StyrsoAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Sandvik, StyrsoAIS-detectedVoydar port-call detector (AIS geofence)
Left SunilaAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from KotkaAuthority-reportedDigitraffic Port Call API
Reported arrival at KotkaAuthority-reportedDigitraffic Port Call API
Arrived at SunilaAIS-detectedVoydar port-call detector (AIS geofence)
Left Oulu (Uleaborg)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Oulu (Uleaborg)Authority-reportedDigitraffic Port Call API
Reported arrival at Oulu (Uleaborg)Authority-reportedDigitraffic Port Call API
Arrived at Oulu (Uleaborg)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from ECORSE, MI (INCLUDED IN PORT OF DETROIT)Authority-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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20186,659 t2,108 t191 days155 kg
20197,164 t2,260 t244 days152 kg
20206,932 t2,185 t175 days157 kg
20218,376 t2,631 t190 days156 kg
20226,575 t2,062 t168 days133 kg
20236,632 t2,083 t175 days148 kg
20246,215 t1,944 t169 days149 kg
20256,579 t2,147 t193 days132 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

Time in port over the last 76 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Sandvik, Styrso SESTRNov 7, 2026, 07:01 UTCNov 7, 2026, 12:23 UTC5 h 22 min
Sunila FISULOct 30, 2026, 16:45 UTCNov 4, 2026, 13:23 UTC4 d 20 h
Oulu (Uleaborg) FIOULOct 23, 2026, 16:18 UTCOct 28, 2026, 12:58 UTC4 d 20 h
Sandvik, Styrso SESTROct 19, 2026, 19:37 UTCOct 19, 2026, 22:05 UTC2 h 27 min
Heroya NOHRYOct 16, 2026, 16:55 UTCOct 19, 2026, 10:22 UTC2 d 17 h
Europoort NLEUROct 12, 2026, 17:07 UTCOct 14, 2026, 15:20 UTC46 h 13 min
Rotterdam NLRTMOct 7, 2026, 20:30 UTCOct 12, 2026, 15:28 UTC4 d 18 h
Blyth GBBLYOct 4, 2026, 09:08 UTCOct 6, 2026, 07:44 UTC46 h 36 min
Ceuta ESCEUSep 22, 2026, 05:26 UTCSep 22, 2026, 18:46 UTC13 h 19 min
Gandia ESGANSep 15, 2026, 16:30 UTCSep 15, 2026, 17:20 UTC50 min
Kiel DEKELSep 3, 2026, 22:16 UTCSep 15, 2026, 16:30 UTC11 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

PortRecordDate (UTC)BerthSource
Kotka FIKTKArrivalOct 30, 2026, 17:15 UTCHIEH6Digitraffic Port Call API
Oulu (Uleaborg) FIOULArrivalOct 23, 2026, 16:35 UTC302Digitraffic Port Call API
ECORSE, MI (INCLUDED IN PORT OF DETROIT)DepartureDec 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ECORSE, MI (INCLUDED IN PORT OF DETROIT)ArrivalDec 6, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalOct 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureOct 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Chicago USCHIDepartureOct 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Chicago USCHIArrivalOct 5, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalMay 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureMay 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
BURNS WATERWAY HARBOR, INDepartureMay 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
BURNS WATERWAY HARBOR, INArrivalMay 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.

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 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.

How these are computed →

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.

See a sample report (PDF)

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/9604184
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite 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.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Bron: Inspectie Leefomgeving en Transport (ILT), Vlagregister data (CC0 1.0). (CC0 1.0 (ilent.nl site-wide))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9604184-vikingbank

Generated from voydar.com on Nov 17, 2026, 19:06 UTC