Bonifacy appears on the UK Sanctions List, the EU list of designated vessels and the Canadian autonomous sanctions list under Russia, Russia (Reg. 833/2014 Annex XLII). Verify at GOV.UK.
Every vessel on:UK Sanctions ListEU list of designated vesselsCanadian autonomous sanctions list
Bonifacy
Oil tanker · Cameroon · built 2004 · AIS Class A
In short
Bonifacy (Oil tanker, Cameroon flag) was last seen on AIS on , at anchor, at 57.6724° N, 32.5227° E. Its crew-entered AIS destination is RULED (Saint Petersburg (ex Leningrad)); its reported draught is 7 m (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 22:10 UTC). It appears on 3 sanctions lists (details below).
- Vessel type
- Oil tanker
- Flag
- Cameroon
- Year built
- 2004
- Gross tonnage
- 28,059
- Size (length × beam)
- 180 m × 28 m
- Registered owner
- —
Watch this ship
Get an email when Bonifacy 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 Bonifacy.
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
- 57.6724° N, 32.5227° E
- Area
- —
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 81 kn
- Course
- 312°
- Heading
- 217°
Voydar detected no port call in the last 30 days.
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
- Bonifacy
- IMO numberWhat is an IMO number?
- 9284726
- MMSIWhat is an MMSI?
- 613003743
- Call signWhat is a call sign?
- TJMC147
- Flag
- Cameroon
- Vessel type
- Oil tanker
- AIS ship type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- 28,059
- Length overall
- 179.9 m
- Beam
- 28 m
- Year built
- 2004
CameroonA 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.
- Owner or operator (sanctions listing)
- Blossom Bridge Corp / Seafaring Savants LLC(not linked to a company record)Source: UK Sanctions List (FCDO) · reported · confidence 0.7 · retrieved Oct 3, 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.
| Date | Event | Source |
|---|---|---|
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from New YorkAuthority-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.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| Canadian autonomous sanctions list | Russia | Bonifacy | Jun 13, 2025 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Bonifacy | May 21, 2025 | In force |
| UK Sanctions List | Russia | Bonifacy | May 9, 2025 | In force |
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 0 t | 0 t | 0 days | — |
| 2021 | 619 t | 193 t | 9 days | 313 kg |
Technical efficiency: EIV (5.93 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Oct 28, 2020, 20:27 UTC | SINO | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 17, 2019, 21:04 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| New York USNYC | Departure | Feb 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Feb 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Nov 19, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Nov 19, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Departure | Nov 9, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Arrival | Nov 9, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PROVIDENCE RIVER AND HARBOR, RI | Departure | Nov 3, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PROVIDENCE RIVER AND HARBOR, RI | Arrival | Nov 3, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Sep 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Sep 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 10, 2004.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 |
|---|---|---|
| Oct 3, 2026, 21:31 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 21:16 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 21:06 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 20:46 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 20:31 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 20:04 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 19:32 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 19:04 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 18:48 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 00:16 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 3, 2026, 00:04 UTC | Two positions This MMSI was reported in two places 353 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 23:16 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 23:05 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 22:49 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 22:36 UTC | Two positions This MMSI was reported in two places 353 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 04:31 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 03:31 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 03:01 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 02:16 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 2, 2026, 00:31 UTC | Two positions This MMSI was reported in two places 352 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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
- Where is Bonifacy now?
- Bonifacy (Oil tanker, Cameroon flag) was last seen on AIS on Oct 3, 2026, 22:13 UTC, at anchor, at 57.6724° N, 32.5227° E. The crew-entered destination was RULED (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 22:10 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Bonifacy?
- Bonifacy is an oil tanker sailing under the flag of Cameroon, built in 2004 by Shin Kurushima Dockyard. The vessel is 179.9 m long with a beam of 28 m and has a gross tonnage of 28,059.
- What sanctions and inspection records does Voydar hold for Bonifacy?
- Bonifacy appears on the UK Sanctions List, the EU list of designated vessels and the Canadian autonomous sanctions list under Russia, Russia (Reg. 833/2014 Annex XLII). No matched inspection records are displayed for Bonifacy. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Shin Kurushima Dockyard, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- PatrickIMO 9182045Tanker · built 1998 · 28,077 GT
- WisdomIMO 9182069Oil tanker · built 1999 · 28,077 GT
- Bonanza 10IMO 9222699Oil tanker · built 2000 · 28,133 GT
- Katerina IIIMO 9222704Oil tanker · built 2000 · 28,077 GT
- Sanmar SopranoIMO 9247895Oil tanker · built 2002 · 28,048 GT
- Bitu ExpressIMO 9265689Oil tanker · built 2003 · 28,323 GT
- E PioneerIMO 9278686Oil tanker · built 2003 · 28,059 GT
- FathIMO 9272395Oil tanker · built 2003 · 28,059 GT
- IMO 9254927IMO 9254927Tanker · built 2003 · 28,059 GT
- Pro EmeraldIMO 9267948Oil tanker · built 2003 · 28,144 GT
- Pro SapphireIMO 9274484Oil tanker · built 2003 · 28,098 GT
- Biendong MelodyIMO 9279721Oil tanker · built 2004 · 28,150 GT
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/9284726Using 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.