Skip to content

Furness Victoria

Bulk carrier · Panama · built 2012 · AIS Class A

IMO9640621MMSI373191000Call sign3EUY8Last AIS position Oct 1, 2026, 21:36 UTC

In short

Furness Victoria (Bulk carrier, Panama flag) was last seen on AIS on , not moving, in the port of Musel-Arnao. Its crew-entered AIS destination is ES GIJ (Gijon); its reported draught is 12.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:18 UTC). It arrived there on Oct 1, 2026, 19:50 UTC. ISM manager: Viridian Maritime Pte Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Flag
Panama
Year built
2012
Gross tonnage
33,084
Size (length × beam)
197 m × 32 m

Watch this ship

Get an email when Furness Victoria 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 Furness Victoria.

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 Furness Victoria
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
43.579° N, 5.6901° W
Area
Bay of Biscay
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
283°
Heading
250°
43.579° N, 5.6901° W
Open the full live map →

Last 30 days: 2 port calls (Musel-Arnao).

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
Furness Victoria
IMO numberWhat is an IMO number?
9640621
MMSIWhat is an MMSI?
373191000
Call signWhat is a call sign?
3EUY8
Flag
Panama
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
33,084
Length overall
197 m
Beam
32.3 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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
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.

DateEventSource
Arrived at Musel-ArnaoAIS-detectedVoydar port-call detector (AIS geofence)
Left Musel-ArnaoAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Musel-ArnaoAIS-detectedVoydar port-call detector (AIS geofence)
ISM manager: Viridian Maritime Pte Ltd (previously FUKUNAGA KAIUN CO., LTD.)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from MobileAuthority-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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20182,824 t903 t37 days273 kg
20212,827 t897 t29 days326 kg
20226,743 t2,147 t73 days303 kg
20232,924 t932 t38 days280 kg
20246,028 t1,922 t85 days267 kg
20250 t0 t0 days—

Technical efficiency: EEXI (4.09 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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

PortArrivedDepartedTime in port
Musel-Arnao ESMUSOct 1, 2026, 19:50 UTCin port—
Musel-Arnao ESMUSSep 24, 2026, 06:08 UTCOct 1, 2026, 19:50 UTC7 d 13 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
PORT OF SOUTH LOUISIANA (LA)DepartureMay 2, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalApr 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Mobile USMOBDepartureApr 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Mobile USMOBArrivalApr 23, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureApr 20, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalApr 13, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureDec 18, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalDec 12, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PENN MANOR AREA, PADepartureDec 4, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PENN MANOR AREA, PAArrivalNov 30, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureNov 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalNov 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 30, 2012.

Frequently asked questions

Where is Furness Victoria now?
Furness Victoria (Bulk carrier, Panama flag) was last seen on AIS on Oct 1, 2026, 21:36 UTC, not moving, in the port of Musel-Arnao. The crew-entered destination was ES GIJ (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:18 UTC). This report does not confirm the ship’s current route.
What kind of ship is Furness Victoria?
Furness Victoria is a bulk carrier sailing under the flag of Panama, built in 2012 by Kawasaki Heavy Industries. The vessel is 197 m long with a beam of 32.3 m and has a gross tonnage of 33,084.
Who is recorded as the owner or manager of Furness Victoria?
Viridian Maritime Pte Ltd is recorded as ISM manager for Furness Victoria (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Furness Victoria?
Voydar has no matched sanctions record displayed for Furness Victoria from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Furness Victoria. Missing records do not establish whether the ship has been detained.

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