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.1 kn, in the port of Blokken. Its crew-entered AIS destination is NO DRG (Drag), with an ETA of Oct 2, 2026, 06:00 UTC; its reported draught is 4.6 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:01 UTC). It arrived there on Oct 1, 2026, 15:21 UTC.
- Vessel type
- General cargo ship
- Flag
- Norway
- Year built
- 2001
- Gross tonnage
- 2,171
- Size (length × beam)
- 79 m × 14 m
- Registered owner
- —
Watch this ship
Get an email when RIGNATOR 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 RIGNATOR.
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.
Last reported position
received- Position
- 68.5809° N, 15.2089° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.1 kn
- Course
- 234°
- Heading
- 234°
Last 30 days: 8 port calls (Blokken, Sortland, Tromso, and Kaldfjord).
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-upIdentity & particulars
- Name
- RIGNATOR
- IMO numberWhat is an IMO number?
- 9224116
- MMSIWhat is an MMSI?
- 257798800
- Call signWhat is a call sign?
- LEHJ
- Flag
- Norway
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 2,171
- Deadweight (DWT)
- Source: Wikidata, record Q61711996. Added to Voydar on September 23, 2026. Licence: CC0 1.0.2,657 t
- Length overall
- 78.9 m
- Beam
- 13.8 m
- Year built
- 2001
NorwayA 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 |
|---|---|---|
| Arrived at BlokkenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SortlandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SortlandAIS-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 |
|---|---|---|---|
| Blokken NOBLO | Oct 1, 2026, 15:21 UTC | in port | — |
| Sortland NOSLX | Oct 1, 2026, 11:11 UTC | Oct 1, 2026, 15:03 UTC | 3 h 51 min |
| Tromso NOTOS | Sep 30, 2026, 18:06 UTC | Oct 1, 2026, 00:11 UTC | 6 h 5 min |
| Tromso NOTOS | Sep 30, 2026, 03:49 UTC | Sep 30, 2026, 10:17 UTC | 6 h 28 min |
| Tromso NOTOS | Sep 28, 2026, 20:59 UTC | Sep 29, 2026, 03:55 UTC | 6 h 56 min |
| Kaldfjord NOKDF | Sep 28, 2026, 04:44 UTC | Sep 28, 2026, 10:06 UTC | 5 h 21 min |
| Tromso NOTOS | Sep 25, 2026, 20:13 UTC | Sep 26, 2026, 02:17 UTC | 6 h 3 min |
| Blokken NOBLO | Sep 22, 2026, 16:59 UTC | Sep 22, 2026, 20:12 UTC | 3 h 13 min |
| Tromso NOTOS | Aug 22, 2026, 18:15 UTC | Aug 24, 2026, 01:29 UTC | 31 h 14 min |
| Nordkjosbotn NONKB | Jun 27, 2026, 00:27 UTC | Jun 28, 2026, 14:03 UTC | 37 h 36 min |
| Nordkjosbotn NONKB | Jun 13, 2026, 15:06 UTC | Jun 14, 2026, 00:32 UTC | 9 h 26 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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 30, 2026, 05:46 UTC | Draught change Reported draught went from 5.4 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%) |
| Sep 29, 2026, 21:43 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%) |
| Sep 29, 2026, 06:27 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%) |
| Sep 28, 2026, 21:22 UTC | Draught change Reported draught went from 5.4 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%) |
| Sep 28, 2026, 13:07 UTC | Draught change Reported draught went from 3.9 m to 5.4 m after leaving Kaldfjord. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 28, 2026, 05:35 UTC | Draught change Reported draught went from 5 m to 3.9 m while in port at Kaldfjord. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 20:47 UTC | Draught change Reported draught went from 5.4 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%) |
| Sep 23, 2026, 18:24 UTC | Draught change Reported draught went from 3.9 m to 5.4 m after leaving Blokken. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 23, 2026, 10:53 UTC | Draught change Reported draught went from 5.4 m to 3.9 m after leaving Blokken. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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.
Frequently asked questions
- Where is RIGNATOR now?
- RIGNATOR (General cargo ship, Norway flag) was last seen on AIS on Oct 1, 2026, 21:23 UTC, under way at 10.1 kn, in the port of Blokken. The crew-entered destination was NO DRG (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:01 UTC). This report does not confirm the ship’s current route.
- 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 and the New Zealand Russia Sanctions 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.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9224116Using 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.