MISJE LOTUS
General cargo ship · Portugal · built 2024 · AIS Class A
In short
MISJE LOTUS (General cargo ship, Portugal flag) was last seen on AIS on , moored, in the port of Europoort. Its crew-entered AIS destination is NL RTM (Rotterdam); its reported draught is 3.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 12:11 UTC). It arrived there on Nov 18, 2026, 23:50 UTC. ISM manager: Misje EcoBulk AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- General cargo ship
- Flag
- Portugal
- Year built
- 2024
- Gross tonnage
- 3,492
- Size (length × beam)
- 90 m × 15 m
- ISM manager
- Misje EcoBulk AS

Last reported position: 51.9336° N, 4.0522° E · North Sea · See on the map
Watch this ship
Get an email when MISJE LOTUS reaches Rotterdam, and when it 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 20, 2026, 12:37 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for MISJE LOTUS 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: the Voydar app
Last reported position
received- Position
- 51.9336° N, 4.0522° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 346°
- Heading
- 69°
- Compass: course over ground 346°, heading 69°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 10 port calls (Europoort, Tilbury, Amsterdam, IJmuiden/Velsen, Immingham, Hamburg, Bremen, Tyssedal, and Alvik).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data: AISHub contributors · Data delivered by BarentsWatch
Pro shows MISJE LOTUS's track before the last 30 days. Voydar has recorded its port calls since October 11, 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 90 mone tick every 10 m
Beam 15.4 mPlan outline, to scale
- Name
- MISJE LOTUS
- IMO numberWhat is an IMO number?
- 9967550
- MMSIWhat is an MMSI?
- 255916575
- Call signWhat is a call sign?
- CQ2884
- Flag
- Portugal
- Gross tonnageGross tonnage vs deadweight
- 3,492
- Length overall
- 90 m
- Beam
- 15.4 m
- Year built
- 2024
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 · high confidence · retrieved Nov 16, 2026
- 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 |
|---|---|---|
| Arrived at EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TilburyAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TilburyAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdanskAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
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 |
|---|---|---|---|---|
| 2025 | 2,978 t | 929 t | 193 days | 46 kg |
Technical efficiency: EEXI (11.81 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 “General cargo ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed45.9 kg per nautical mile
- Lowest reportedHighest reported
4% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8
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 |
|---|---|---|---|
| Europoort NLEUR | Nov 18, 2026, 23:50 UTC | in port | — |
| Tilbury GBTIL | Nov 14, 2026, 12:08 UTC | Nov 18, 2026, 09:30 UTC | 3 d 21 h |
| Amsterdam NLAMS | Nov 11, 2026, 19:58 UTC | Nov 13, 2026, 09:07 UTC | 37 h 9 min |
| IJmuiden/Velsen NLIJM | Nov 11, 2026, 17:47 UTC | Nov 11, 2026, 19:18 UTC | 1 h 31 min |
| Immingham GBIMM | Nov 8, 2026, 21:02 UTC | Nov 11, 2026, 06:11 UTC | 2 d 9 h |
| Hamburg DEHAM | Nov 5, 2026, 01:15 UTC | Nov 6, 2026, 14:05 UTC | 36 h 50 min |
| Bremen DEBRE | Nov 1, 2026, 21:57 UTC | Nov 4, 2026, 12:05 UTC | 2 d 14 h |
| Tyssedal NOTSX | Oct 27, 2026, 22:05 UTC | Oct 30, 2026, 15:54 UTC | 2 d 17 h |
| Alvik NOAAV | Oct 24, 2026, 22:04 UTC | Oct 27, 2026, 19:35 UTC | 2 d 21 h |
| Europoort NLEUR | Oct 21, 2026, 21:03 UTC | Oct 22, 2026, 14:22 UTC | 17 h 19 min |
| Ipswich GBIPS | Oct 17, 2026, 13:53 UTC | Oct 21, 2026, 09:44 UTC | 3 d 19 h |
| Rosyth GBROY | Oct 11, 2026, 10:30 UTC | Oct 13, 2026, 16:54 UTC | 2 d 6 h |
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 |
|---|---|---|---|---|
| Gdansk PLGDN | Arrival | Oct 4, 2026, 11:30 UTC | Szczeci skie | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
Records published by the authority named on each row. Earliest record for this ship: October 4, 2026.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
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 |
|---|---|---|
| Nov 13, 2026, 07:50 UTC | Draught change Reported draught went from 4.3 m to 6.6 m while in port at Amsterdam. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 10, 2026, 23:08 UTC | Draught change Reported draught went from 6.5 m to 4.3 m while in port at Immingham. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 6, 2026, 12:20 UTC | Draught change Reported draught went from 3.9 m to 6.6 m while in port at Hamburg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 30, 2026, 14:45 UTC | Draught change Reported draught went from 4.1 m to 6.5 m while in port at Tyssedal. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 27, 2026, 18:34 UTC | Draught change Reported draught went from 6.8 m to 4.1 m while in port at Alvik. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 22, 2026, 13:29 UTC | Draught change Reported draught went from 4.6 m to 6.8 m while in port at Europoort. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 21, 2026, 10:06 UTC | Draught change Reported draught went from 6.3 m to 4.6 m after leaving Ipswich. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 13, 2026, 16:59 UTC | Draught change Reported draught went from 6.6 m to 4 m after leaving Rosyth. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 17:20 UTC | Draught change Reported draught went from 5.8 m to 4.6 m after leaving Oxelosund. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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 MISJE LOTUS?
- MISJE LOTUS is a general cargo ship sailing under the flag of Portugal, built in 2024 by Colombo Dockyard. The vessel is 90 m long with a beam of 15.4 m and has a gross tonnage of 3,492.
- Who is recorded as the owner or manager of MISJE LOTUS?
- Misje EcoBulk AS is recorded as ISM manager for MISJE LOTUS (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 MISJE LOTUS?
- Voydar has no matched sanctions record displayed for MISJE LOTUS 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 MISJE LOTUS. 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
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/9967550Cite this page
MISJE LOTUS. Voydar (voydar.com). https://www.voydar.com/vessel/9967550-misje-lotus. Retrieved November 20, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.