BIT FORCE
Oil tanker · Netherlands · built 2003 · AIS Class A
In short
BIT FORCE (Oil tanker, Netherlands flag) was last seen on AIS on , at anchor, in the North Sea. Its crew-entered AIS destination is MAMOH > NLRTM, with an ETA of Nov 15, 2026, 20:00 UTC; its reported draught is 6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 07:10 UTC). Registered owner: Ciconia B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Vlaardingen (departed Oct 31, 2026, 08:32 UTC) to MAMOH > NLRTM
- Vessel type
- Oil tanker
- Flag
- Netherlands
- Year built
- 2003
- Gross tonnage
- 6,280
- Size (length × beam)
- 117 m × 18 m
- Registered owner
- Ciconia B.V.

Last reported position: 51.9436° N, 3.7175° E · North Sea · See on the map
Watch this ship
Get an email when BIT FORCE arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 16, 2026, 14:49 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for BIT FORCE 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
- 51.9436° N, 3.7175° E
- Area
- North Sea
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0.4 kn
- Course
- 161°
- Heading
- 296°
- Compass: course over ground 161°, heading 296°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 5 port calls (Vlaardingen, Europoort, and Gravesend).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows BIT FORCE's track before the last 30 days. Voydar has recorded its port calls since September 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 116.9 mone tick every 25 m
Beam 18 mPlan outline, to scale
- Name
- BIT FORCE
- IMO numberWhat is an IMO number?
- 9256420
- MMSIWhat is an MMSI?
- 244813000
- Call signWhat is a call sign?
- PCXW
- Flag
- Netherlands
- Gross tonnageGross tonnage vs deadweight
- 6,280
- Length overall
- 116.9 m
- Beam
- 18 m
- Year built
- 2003
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.
- Registered owner
- Ciconia B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- SHANGHAI EDWARD SHIPBUILDING LTD.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 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 VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left GravesendAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GravesendAIS-detected | Voydar port-call detector (AIS geofence) |
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.
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 | 7,752 t | 2,418 t | 215 days | 147 kg |
| 2019 | 8,970 t | 2,798 t | 235 days | 162 kg |
| 2020 | 9,233 t | 2,880 t | 196 days | 173 kg |
| 2021 | 7,851 t | 2,449 t | 185 days | 159 kg |
| 2022 | 7,677 t | 2,395 t | 194 days | 153 kg |
| 2023 | 6,381 t | 1,990 t | 173 days | 155 kg |
| 2024 | 7,348 t | 2,292 t | 174 days | 162 kg |
| 2025 | 6,849 t | 2,136 t | 148 days | 183 kg |
Technical efficiency: EEXI (11.09 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Oil tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile68.77 g per tonne-nautical mile
- Lowest reportedHighest reported
98% of the 1,692 ships in this group reported a lower figure.
Group: lower quartile 5.83 · median 7.97 · upper quartile 13.91
- CO₂ per nautical mile sailed183 kg per nautical mile
- Lowest reportedHighest reported
5% of the 1,763 ships in this group reported a lower figure.
Group: lower quartile 316.7 · median 404.7 · upper quartile 492.7
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Vlaardingen NLVLA | Oct 29, 2026, 23:05 UTC | Oct 31, 2026, 08:32 UTC | 33 h 27 min |
| Europoort NLEUR | Oct 26, 2026, 17:40 UTC | Oct 29, 2026, 22:25 UTC | 3 d 4 h |
| Gravesend GBGVS | Oct 25, 2026, 05:28 UTC | Oct 26, 2026, 00:38 UTC | 19 h 10 min |
| Vlaardingen NLVLA | Oct 22, 2026, 12:27 UTC | Oct 23, 2026, 18:08 UTC | 29 h 42 min |
| Vlaardingen NLVLA | Oct 17, 2026, 16:44 UTC | Oct 18, 2026, 17:03 UTC | 24 h 19 min |
| Alvika NOALV | Oct 13, 2026, 08:12 UTC | Oct 13, 2026, 22:03 UTC | 13 h 51 min |
| Thoroya NOTOY | Oct 11, 2026, 06:11 UTC | Oct 11, 2026, 17:29 UTC | 11 h 17 min |
| Botlek NLBOT | Oct 8, 2026, 15:13 UTC | Oct 9, 2026, 09:58 UTC | 18 h 45 min |
| Delfzijl NLDZL | Oct 3, 2026, 02:40 UTC | Oct 4, 2026, 00:22 UTC | 21 h 43 min |
| Schiermonnikoog NLSMO | Sep 30, 2026, 14:05 UTC | Oct 3, 2026, 00:00 UTC | 2 d 9 h |
| Thoroya NOTOY | Sep 27, 2026, 17:51 UTC | Sep 28, 2026, 07:05 UTC | 13 h 14 min |
| Vlaardingen NLVLA | Sep 24, 2026, 05:19 UTC | Sep 26, 2026, 04:08 UTC | 46 h 49 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.
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 30, 2026, 21:57 UTC | Draught change Reported draught went from 6 m to 7.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 25, 2026, 11:32 UTC | Draught change Reported draught went from 7.1 m to 6.1 m while in port at Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 22, 2026, 15:14 UTC | Draught change Reported draught went from 6 m to 6.9 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 18, 2026, 15:49 UTC | Draught change Reported draught went from 6 m to 6.7 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 8, 2026, 20:07 UTC | Draught change Reported draught went from 6.2 m to 6.7 m while in port at Botlek. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 02:40 UTC | Draught change Reported draught went from 7.4 m to 6.2 m while in port at Thoroya. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 08:34 UTC | Draught change Reported draught went from 6 m to 7.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
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).
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 BIT FORCE?
- BIT FORCE is an oil tanker sailing under the flag of Netherlands, built in 2003. The vessel is 116.9 m long with a beam of 18 m and has a gross tonnage of 6,280.
- Who is recorded as the owner or manager of BIT FORCE?
- Ciconia B.V. is recorded as Registered owner for BIT FORCE (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for BIT FORCE?
- Voydar has no matched sanctions record displayed for BIT FORCE 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 BIT FORCE. Missing records do not establish whether the ship has been detained.
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
More Oil tankers
Other oil tankers with full Voydar profiles. A different set each day. All oil tankers
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/9256420Cite this page
BIT FORCE. Voydar (voydar.com). https://www.voydar.com/vessel/9256420-bit-force. 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.