Skip to content

SC CONNECTOR

Ro-ro ship · Malta · built 1997 · AIS Class A

IMO9131993MMSI256149000Call sign9HA3834Last AIS position Oct 5, 2026, 07:35 UTC

In short

SC CONNECTOR (Ro-ro ship, Malta flag) was last seen on AIS on , under way at 1.3 kn, in the port of Immingham. Its crew-entered AIS destination is IMMINGHAM, with an ETA of Oct 5, 2026, 07:00 UTC; its reported draught is 6.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 06:50 UTC). It arrived there on Oct 5, 2026, 06:55 UTC. Registered owner: Sea-Cargo (source: Wikidata).

Vessel type
Ro-ro ship
Flag
Malta
Year built
1997
Gross tonnage
12,251
Size (length × beam)
155 m × 23 m
Registered owner
Sea-Cargo

Watch this ship

Get an email when SC CONNECTOR 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.

Photo of SC CONNECTOR
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
53.6262° N, 0.1912° W
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
1.3 kn
Course
330°
Heading
115°
53.6262° N, 0.1912° W
Open the full live map →

Last 30 days: 10 port calls (Immingham, Tananger, Husoy - Karmoy, Rotterdam, Husnes, and Pernis).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows SC CONNECTOR's track before the last 30 days. Voydar has recorded its port calls since August 14, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
SC CONNECTOR
IMO numberWhat is an IMO number?
9131993
MMSIWhat is an MMSI?
256149000
Call signWhat is a call sign?
9HA3834
Flag
Malta
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
12,251
Length overall
154.5 m
Beam
22.7 m
Year built
1997

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.

Registered owner
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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 ImminghamAIS-detectedVoydar port-call detector (AIS geofence)
Left TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Left Husoy - KarmoyAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Husoy - KarmoyAIS-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
201814,310 t4,463 t255 days206 kg
201914,304 t4,462 t256 days201 kg
202014,151 t4,414 t287 days219 kg
202112,628 t3,939 t213 days203 kg
202212,520 t3,905 t228 days196 kg
202311,775 t3,673 t225 days190 kg
202412,720 t3,968 t261 days185 kg
202512,716 t3,966 t257 days185 kg

Technical efficiency: EEXI (12.69 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
Immingham GBIMMOct 5, 2026, 06:55 UTCin port—
Tananger NOTAEOct 2, 2026, 20:43 UTCOct 3, 2026, 02:12 UTC5 h 29 min
Husoy - Karmoy NOHSOOct 2, 2026, 12:08 UTCOct 2, 2026, 18:32 UTC6 h 24 min
Tananger NOTAEOct 1, 2026, 19:56 UTCOct 1, 2026, 21:34 UTC1 h 38 min
Rotterdam NLRTMSep 29, 2026, 16:05 UTCSep 29, 2026, 22:21 UTC6 h 17 min
Immingham GBIMMSep 28, 2026, 17:01 UTCSep 29, 2026, 05:06 UTC12 h 4 min
Husnes NOHUSSep 26, 2026, 09:02 UTCSep 26, 2026, 12:25 UTC3 h 23 min
Pernis NLPERSep 15, 2026, 13:45 UTCSep 17, 2026, 09:48 UTC44 h 3 min
Pernis NLPERSep 8, 2026, 14:24 UTCSep 10, 2026, 12:26 UTC46 h 2 min
Pernis NLPERSep 8, 2026, 07:43 UTCSep 8, 2026, 14:23 UTC6 h 40 min
Tananger NOTAEAug 27, 2026, 19:46 UTCAug 27, 2026, 21:19 UTC1 h 33 min
Havik NOHVIAug 14, 2026, 13:38 UTCAug 15, 2026, 13:00 UTC23 h 22 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.

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
Sep 29, 2026, 17:26 UTC
Draught change

Reported draught went from 6.2 m to 5.6 m while in port at Rotterdam. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 27, 2026, 00:13 UTC
Draught change

Reported draught went from 5.6 m to 6.1 m after leaving Husnes. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

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.

How these are computed →

Frequently asked questions

Where is SC CONNECTOR now?
SC CONNECTOR (Ro-ro ship, Malta flag) was last seen on AIS on Oct 5, 2026, 07:35 UTC, under way at 1.3 kn, in the port of Immingham. The crew-entered destination was IMMINGHAM (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 06:50 UTC). This report does not confirm the ship’s current route.
What kind of ship is SC CONNECTOR?
SC CONNECTOR is a ro-ro ship sailing under the flag of Malta, built in 1997 by Fosen Yard. The vessel is 154.5 m long with a beam of 22.7 m and has a gross tonnage of 12,251.
Who is recorded as the owner or manager of SC CONNECTOR?
Sea-Cargo is recorded as Registered owner for SC CONNECTOR (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for SC CONNECTOR?
Voydar has no matched sanctions record displayed for SC CONNECTOR 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 SC CONNECTOR. 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/9131993
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