RIGNATOR
General cargo ship · Norway · built 2001 · AIS Class A
In short
RIGNATOR (General cargo ship, Norway flag) was last seen on AIS on , under way at 10.3 kn, in the Norwegian Sea. Its crew-entered AIS destination is NO BGN (Bergneset), with an ETA of Nov 17, 2026, 01:00 UTC; its reported draught is 3.9 m (voyage report via BarentsWatch AIS API, received Nov 16, 2026, 15:24 UTC).
Current voyage: from Fjelldal (departed Nov 16, 2026, 12:24 UTC) to NO BGN (Bergneset)
- Vessel type
- General cargo ship
- Flag
- Norway
- Year built
- 2001
- Gross tonnage
- 2,171
- Size (length × beam)
- 79 m × 14 m
- Registered owner
- —

Last reported position: 69.071° N, 17.3669° E · Norwegian Sea · See on the map
Watch this ship
Get an email when RIGNATOR reaches Bergneset, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for RIGNATOR 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
- 69.071° N, 17.3669° E
- Area
- Norwegian Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 10.3 kn
- Course
- 30°
- Heading
- 32°
- Compass: course over ground 30°, heading 32°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Fjelldal, Blokken, Tromso, Stakkvik, Tytebarvika, and Skjervoy).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 78.9 mone tick every 10 m
Beam 13.8 mPlan outline, to scale
- Name
- RIGNATOR
- IMO numberWhat is an IMO number?
- 9224116
- MMSIWhat is an MMSI?
- 257798800
- Call signWhat is a call sign?
- LEHJ
- Flag
- Norway
- Gross tonnageGross tonnage vs deadweight
- 2,171
- Deadweight (DWT)
- Source: Wikidata, record Q61711996. Added to Voydar on October 23, 2026. Licence: CC0 1.0.2,657 t
- Length overall
- 78.9 m
- Beam
- 13.8 m
- Year built
- 2001
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
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.
| Date | Event | Source |
|---|---|---|
| Left FjelldalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FjelldalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BlokkenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BlokkenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TromsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TromsoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Brownsville, Texas | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at PHILADELPHIA, Pennsylvania | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Apr 19, 2008 | Vessel Operational Control | New Orleans, Louisiana | clean |
| Apr 15, 2008 | Vessel InspectionPSC | Brownsville, Texas | clean |
| Jan 15, 2003 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Sep 20, 2002 | Vessel Inspection | New Orleans, Louisiana | clean |
| Sep 19, 2002 | Vessel InspectionPSC | New Orleans, Louisiana | clean |
| Sep 16, 2002 | Vessel Operational Control | New Orleans, Louisiana | clean |
| Sep 16, 2002 | Vessel Operational Control | New Orleans, Louisiana | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 |
|---|---|---|---|
| Fjelldal NOFJL | Nov 15, 2026, 23:50 UTC | Nov 16, 2026, 12:24 UTC | 12 h 35 min |
| Blokken NOBLO | Nov 15, 2026, 11:55 UTC | Nov 15, 2026, 17:12 UTC | 5 h 17 min |
| Tromso NOTOS | Nov 14, 2026, 18:22 UTC | Nov 15, 2026, 00:40 UTC | 6 h 18 min |
| Stakkvik NOSAK | Nov 14, 2026, 06:34 UTC | Nov 14, 2026, 08:53 UTC | 2 h 19 min |
| Tromso NOTOS | Nov 13, 2026, 11:11 UTC | Nov 13, 2026, 17:51 UTC | 6 h 40 min |
| Tromso NOTOS | Nov 12, 2026, 11:50 UTC | Nov 12, 2026, 19:17 UTC | 7 h 27 min |
| Tromso NOTOS | Nov 10, 2026, 12:39 UTC | Nov 10, 2026, 17:04 UTC | 4 h 25 min |
| Tromso NOTOS | Nov 9, 2026, 02:58 UTC | Nov 9, 2026, 12:22 UTC | 9 h 24 min |
| Tytebarvika NOTYT | Nov 8, 2026, 18:00 UTC | Nov 8, 2026, 20:21 UTC | 2 h 22 min |
| Skjervoy NOSKY | Nov 7, 2026, 18:36 UTC | Nov 8, 2026, 13:21 UTC | 18 h 45 min |
| Stakkvik NOSAK | Nov 7, 2026, 09:20 UTC | Nov 7, 2026, 10:37 UTC | 1 h 17 min |
| Tromso NOTOS | Nov 7, 2026, 01:19 UTC | Nov 7, 2026, 07:06 UTC | 5 h 47 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 |
|---|---|---|---|---|
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Aug 11, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Aug 7, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Departure | Aug 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LA | Arrival | Aug 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Apr 19, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Apr 18, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Departure | Apr 16, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Arrival | Apr 14, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Jan 24, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Arrival | Jan 22, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Departure | Jan 15, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Arrival | Jan 14, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 19, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
Predicted arrival
Voydar estimates arrival at Harstad around Nov 16, 2026, 09:07 UTC, most likely between Nov 16, 2026, 00:24 UTC and Nov 16, 2026, 10:23 UTC. Based on 19 past transits between NOBLO and Harstad seen in our port calls. The crew-reported ETA is Nov 16, 2026, 01:00 UTC.
Medium (50%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Nov 15, 2026, 12:51 UTC | Draught change Reported draught went from 3.9 m to 5.3 m while in port at Blokken. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 14, 2026, 18:56 UTC | Draught change Reported draught went from 5 m to 3.9 m while in port at Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 14, 2026, 10:59 UTC | Draught change Reported draught went from 3.9 m to 5 m after leaving Stakkvik. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 12, 2026, 22:16 UTC | Draught change Reported draught went from 3.9 m to 5.4 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 11, 2026, 16:04 UTC | Draught change Reported draught went from 3.9 m to 5.3 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 11, 2026, 06:25 UTC | Draught change Reported draught went from 5.3 m to 3.9 m after leaving Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 10, 2026, 20:20 UTC | Draught change Reported draught went from 3.9 m to 5.3 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 10, 2026, 06:31 UTC | Draught change Reported draught went from 5.3 m to 3.9 m after leaving Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 9, 2026, 17:14 UTC | Draught change Reported draught went from 3.9 m to 5.3 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 8, 2026, 18:43 UTC | Draught change Reported draught went from 4.5 m to 5.3 m while in port at Tytebarvika. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 8, 2026, 12:23 UTC | Draught change Reported draught went from 5.3 m to 4.5 m while in port at Skjervoy. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 7, 2026, 11:11 UTC | Draught change Reported draught went from 4.6 m to 5.3 m after leaving Stakkvik. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 5, 2026, 04:46 UTC | Draught change Reported draught went from 5.3 m to 3.9 m after leaving Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 4, 2026, 20:02 UTC | Draught change Reported draught went from 3.9 m to 5.3 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 4, 2026, 08:06 UTC | Draught change Reported draught went from 5.3 m to 3.9 m while in port at Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 3, 2026, 15:39 UTC | Draught change Reported draught went from 3.9 m to 5.3 m after leaving Tromso. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 3, 2026, 06:20 UTC | Draught change Reported draught went from 5.3 m to 3.9 m after leaving Tromso. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 2, 2026, 04:09 UTC | Draught change Reported draught went from 3.9 m to 5.4 m after leaving Sortland. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 30, 2026, 00:28 UTC | Draught change Reported draught went from 5 m to 3.9 m while in port at Drag. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 29, 2026, 13:47 UTC | Draught change Reported draught went from 3.9 m to 5 m while in port at Blokken. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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).
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
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.
Frequently asked questions
- What kind of ship is RIGNATOR?
- RIGNATOR is a general cargo ship sailing under the flag of Norway, built in 2001 by Tille Scheepsbouw. The vessel is 78.9 m long with a beam of 13.8 m and has a gross tonnage of 2,171.
- What sanctions and inspection records does Voydar hold for RIGNATOR?
- Voydar has no matched sanctions record displayed for RIGNATOR 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. RIGNATOR has 7 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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.
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/9224116Cite this page
RIGNATOR. Voydar (voydar.com). https://www.voydar.com/vessel/9224116-rignator. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.