Skip to content

Suar Vigo

Ro-ro ship · Spain · built 2003 · AIS Class A

IMO9250000MMSI224499000Call signECDYLast AIS position Oct 3, 2026, 14:22 UTC

In short

Suar Vigo (Ro-ro ship, Spain flag) was last seen on AIS on , under way at 18.4 kn, near Malaga (Mediterranean Sea). Its crew-entered AIS destination is ES BCN (Barcelona); its reported draught is 5.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 04:49 UTC). ISM manager: FLOTA SUARDIAZ, S.L. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Santa Cruz de Tenerife (departed Sep 29, 2026, 00:42 UTC) to ES BCN (Barcelona)

Vessel type
Ro-ro ship
Flag
Spain
Year built
2003
Gross tonnage
16,361
Size (length × beam)
149 m

Watch this ship

Get an email when Suar Vigo 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 Suar Vigo.

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 SUAR VIGO
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
36.5957° N, 4.2381° W
Area
Mediterranean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
18.4 kn
Course
255°
Heading
252°
36.5957° N, 4.2381° W
Open the full live map →

Last 30 days: 2 port calls (Santa Cruz de Tenerife and Barcelona).

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
Suar Vigo
IMO numberWhat is an IMO number?
9250000
MMSIWhat is an MMSI?
224499000
Flag
Spain
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
16,361
Length overall
149 m
Beam
—
Year built
2003

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
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
Left Santa Cruz de TenerifeAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Santa Cruz de TenerifeAIS-detectedVoydar port-call detector (AIS geofence)
Left BarcelonaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BarcelonaAIS-detectedVoydar port-call detector (AIS geofence)

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
201827,753 t8,901 t216 days365 kg
201925,382 t8,139 t193 days345 kg
202018,550 t5,942 t130 days392 kg
202123,492 t7,529 t171 days363 kg
202226,123 t8,371 t188 days380 kg
202327,794 t8,914 t219 days345 kg
202418,847 t6,023 t269 days317 kg
202540,747 t13,060 t293 days343 kg

Technical efficiency: EEXI (23.7 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
Santa Cruz de Tenerife ESSCTSep 28, 2026, 19:47 UTCSep 29, 2026, 00:42 UTC4 h 54 min
Barcelona ESBCNSep 25, 2026, 03:06 UTCSep 26, 2026, 00:10 UTC21 h 4 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.

Frequently asked questions

Where is Suar Vigo now?
Suar Vigo (Ro-ro ship, Spain flag) was last seen on AIS on Oct 3, 2026, 14:22 UTC, under way at 18.4 kn, near Malaga (Mediterranean Sea). The crew-entered destination was ES BCN (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 04:49 UTC). This report does not confirm the ship’s current route.
What kind of ship is Suar Vigo?
Suar Vigo is a ro-ro ship sailing under the flag of Spain, built in 2003 by Hijos de J. Barreras. The vessel is 149 m long and has a gross tonnage of 16,361.
Who is recorded as the owner or manager of Suar Vigo?
FLOTA SUARDIAZ, S.L. is recorded as ISM manager for Suar Vigo (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 Suar Vigo?
Voydar has no matched sanctions record displayed for Suar Vigo 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 Suar Vigo. 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/9250000
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