Skip to content

BOKALIFT 2

Offshore unit · Cyprus · built 2000 · AIS Class A

IMO9190705MMSI209951000Call sign5BMC5Last AIS position Oct 3, 2026, 21:45 UTC

In short

BOKALIFT 2 (Offshore unit, Cyprus flag) was last seen on AIS on , moored, in the port of Teesport. Its crew-entered AIS destination is HORNSEA 3 OWF, with an ETA of Oct 3, 2026, 17:00 UTC; its reported draught is 9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 21:20 UTC). It arrived there on Oct 3, 2026, 16:16 UTC. ISM manager: BOSKALIS OFFSHORE FLEET MGMT (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Offshore unit
Flag
Cyprus
Year built
2000
Gross tonnage
47,079
Size (length × beam)
231 m × 36 m

Watch this ship

Get an email when BOKALIFT 2 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 BOKALIFT 2.

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
54.5984° N, 1.1699° W
Area
North Sea
Speed
0 kn
Course
132°
Heading
42°
54.5984° N, 1.1699° W
Open the full live map →

Last 30 days: 3 port calls (Teesport).

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-up

Identity & particulars

Name
BOKALIFT 2
IMO numberWhat is an IMO number?
9190705
MMSIWhat is an MMSI?
209951000
Call signWhat is a call sign?
5BMC5
Flag
Cyprus
AIS ship type
Other
Gross tonnageGross tonnage vs deadweight
47,079
Length overall
231 m
Beam
36 m
Year built
2000

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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 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 TeesportAIS-detectedVoydar port-call detector (AIS geofence)
Left TeesportAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TeesportAIS-detectedVoydar port-call detector (AIS geofence)
Left TeesportAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TeesportAIS-detectedVoydar port-call detector (AIS geofence)
Port State Control inspection at Woods Hole, MassachusettsUSCG PSIX / CGMIX inspections
Port State Control inspection at Woods Hole, MassachusettsUSCG PSIX / CGMIX inspections
Inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Port State Control inspection at Lewes, DelawareUSCG PSIX / CGMIX inspections
Port State Control inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Inspection at Woods Hole, MassachusettsUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Port State Control inspection at Woods Hole, MassachusettsUSCG PSIX / CGMIX inspections
Reported departure from BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Port State Control inspection at CORPUS CHRISTI, TexasUSCG 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

14
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Apr 28, 2026Vessel InspectionPSCWoods Hole, Massachusettsclean
Oct 28, 2025Vessel InspectionPSCWoods Hole, Massachusettsclean
Oct 11, 2025Vessel Operational ControlSTATEN ISLAND, New Yorkclean
Apr 22, 2025Vessel InspectionPSCLewes, Delawareclean
Jul 12, 2024Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Jul 18, 2023Vessel InspectionWoods Hole, Massachusettsclean
Jul 1, 2023Incident InvestigationWASHINGTON, District of Columbiaclean
Jun 7, 2023Vessel InspectionPSCWoods Hole, Massachusettsclean
Jun 26, 2004Incident InvestigationWASHINGTON, District of Columbiaclean
Jan 22, 2004Vessel InspectionPSCCORPUS CHRISTI, Texasclean
Jun 5, 2002Vessel InspectionPort Arthur, Texasclean
Dec 2, 2001Vessel InspectionMorgan City, Louisianaclean
May 31, 2001Vessel InspectionMorgan City, Louisianaclean
May 23, 2001Vessel InspectionMorgan City, Louisianaclean

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.

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
202514,475 t4,515 t98 days1,660 kg

Technical efficiency: Not Applicable. 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
Teesport GBTEEOct 3, 2026, 16:16 UTCin port—
Teesport GBTEEOct 1, 2026, 02:23 UTCOct 1, 2026, 12:49 UTC10 h 27 min
Teesport GBTEESep 28, 2026, 07:57 UTCSep 28, 2026, 17:37 UTC9 h 40 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

PortRecordDate (UTC)BerthSource
BAYOU LAFOURCHE AND LAFOURCHE-JUMP WATERWAY, LADepartureJul 13, 2004(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: July 13, 2004.

Frequently asked questions

Where is BOKALIFT 2 now?
BOKALIFT 2 (Offshore unit, Cyprus flag) was last seen on AIS on Oct 3, 2026, 21:45 UTC, moored, in the port of Teesport. The crew-entered destination was HORNSEA 3 OWF (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 21:20 UTC). This report does not confirm the ship’s current route.
What kind of ship is BOKALIFT 2?
BOKALIFT 2 is an offshore unit sailing under the flag of Cyprus, built in 2000 by Harland and Wolff. The vessel is 231 m long with a beam of 36 m and has a gross tonnage of 47,079.
Who is recorded as the owner or manager of BOKALIFT 2?
BOSKALIS OFFSHORE FLEET MGMT is recorded as ISM manager for BOKALIFT 2 (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for BOKALIFT 2?
Voydar has no matched sanctions record displayed for BOKALIFT 2 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. BOKALIFT 2 has 14 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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/9190705
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