RS ALEGRANZA
Cable and pipe layer · Portugal · built 2006 · AIS Class A
In short
RS ALEGRANZA (Cable and pipe layer, Portugal flag) was last seen on AIS on , moored, near Moldtustranda (Norwegian Sea). Its crew-entered AIS destination is FOSNAVAG; its reported draught is 5.1 m (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 13:31 UTC).
Current voyage: from Mjolstadneset (departed Sep 22, 2026, 16:44 UTC) to FOSNAVAG
- Vessel type
- Cable and pipe layer
- Flag
- Portugal
- Year built
- 2006
- Gross tonnage
- 3,404
- Size (length × beam)
- 80 m
- Registered owner
- —
Watch this ship
Get an email when RS ALEGRANZA 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.

Last reported position
received- Position
- 62.3214° N, 5.6707° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 276°
- Heading
- 274°
Last 30 days: at least 12 port calls (Mjolstadneset and Eggesbones).
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- RS ALEGRANZA
- IMO numberWhat is an IMO number?
- 9282144
- MMSIWhat is an MMSI?
- 255915965
- Call signWhat is a call sign?
- CQ2423
- Flag
- Portugal
- Vessel type
- Cable and pipe layer
- AIS ship type
- Other
- Gross tonnageGross tonnage vs deadweight
- 3,404
- Length overall
- 80 m
- Beam
- —
- Year built
- 2006
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 · 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.
| Date | Event | Source |
|---|---|---|
| Left MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MjolstadnesetAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LAAuthority-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.
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 |
|---|---|---|---|
| Mjolstadneset NOMSD | Sep 22, 2026, 04:22 UTC | Sep 22, 2026, 16:44 UTC | 12 h 22 min |
| Mjolstadneset NOMSD | Sep 22, 2026, 00:46 UTC | Sep 22, 2026, 04:19 UTC | 3 h 33 min |
| Mjolstadneset NOMSD | Sep 21, 2026, 16:52 UTC | Sep 22, 2026, 00:37 UTC | 7 h 45 min |
| Mjolstadneset NOMSD | Sep 21, 2026, 04:26 UTC | Sep 21, 2026, 16:46 UTC | 12 h 20 min |
| Mjolstadneset NOMSD | Sep 21, 2026, 00:53 UTC | Sep 21, 2026, 04:23 UTC | 3 h 30 min |
| Eggesbones NOEGG | Sep 20, 2026, 16:51 UTC | Sep 21, 2026, 00:41 UTC | 7 h 50 min |
| Mjolstadneset NOMSD | Sep 20, 2026, 04:30 UTC | Sep 20, 2026, 16:51 UTC | 12 h 20 min |
| Mjolstadneset NOMSD | Sep 20, 2026, 00:56 UTC | Sep 20, 2026, 04:28 UTC | 3 h 32 min |
| Mjolstadneset NOMSD | Sep 19, 2026, 17:00 UTC | Sep 20, 2026, 00:45 UTC | 7 h 45 min |
| Mjolstadneset NOMSD | Sep 19, 2026, 04:34 UTC | Sep 19, 2026, 16:54 UTC | 12 h 21 min |
| Mjolstadneset NOMSD | Sep 19, 2026, 01:00 UTC | Sep 19, 2026, 04:30 UTC | 3 h 30 min |
| Mjolstadneset NOMSD | Sep 18, 2026, 17:03 UTC | Sep 19, 2026, 00:48 UTC | 7 h 45 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Departure | Sep 12, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Arrival | Aug 31, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Departure | Aug 22, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Arrival | Aug 22, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Departure | Aug 3, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Arrival | Jul 27, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Jul 20, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Arrival | Jun 28, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Jun 9, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Jun 8, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | May 30, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | May 1, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 4, 2006.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is RS ALEGRANZA now?
- RS ALEGRANZA (Cable and pipe layer, Portugal flag) was last seen on AIS on Oct 5, 2026, 13:34 UTC, moored, near Moldtustranda (Norwegian Sea). The crew-entered destination was FOSNAVAG (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 13:31 UTC). This report does not confirm the ship’s current route.
- What kind of ship is RS ALEGRANZA?
- RS ALEGRANZA is a cable and pipe layer sailing under the flag of Portugal, built in 2006 by Wuhu Shipyard. The vessel is 80 m long and has a gross tonnage of 3,404.
- What sanctions and inspection records does Voydar hold for RS ALEGRANZA?
- Voydar has no matched sanctions record displayed for RS ALEGRANZA 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 RS ALEGRANZA. 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/9282144Using 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.