LOTUS RISING
Bulk carrier · Marshall Islands · built 2001 · AIS Class A
In short
LOTUS RISING (Bulk carrier, Marshall Islands flag) was last seen on AIS on , under way at 11.9 kn, near Shekou Pt (South China Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is HONG KONG; its reported draught is 13.8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 02:24 UTC). ISM manager: Minoa Marine Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- Marshall Islands
- Year built
- 2001
- Gross tonnage
- 39,783
- Size (length × beam)
- 225 m × 32 m
- ISM manager
- Minoa Marine Ltd
Watch this ship
LOTUS RISING has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
We email you a link and a code. That creates a free account, no password or card, and follows LOTUS RISING.
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
- 22.5155° N, 113.7399° E
- Area
- South China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.9 kn
- Course
- 343°
- Heading
- 344°
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
- LOTUS RISING
- IMO numberWhat is an IMO number?
- 9217656
- MMSIWhat is an MMSI?
- 538006247
- Call signWhat is a call sign?
- V7LA7
- Flag
- Marshall Islands
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 39,783
- Deadweight (DWT)
- Source: Wikidata, record Q117022894. Added to Voydar on September 23, 2026. Licence: CC0 1.0.75,120 t
- Length overall
- 225 m
- Beam
- 32 m
- Year built
- 2001
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 years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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 |
|---|---|---|
| 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 Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Long BeachAuthority-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.
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 | 2,087 t | 669 t | 29 days | 320 kg |
| 2019 | 1,522 t | 484 t | 20 days | 324 kg |
| 2020 | 3,140 t | 1,007 t | 32 days | 359 kg |
| 2022 | 2,565 t | 812 t | 37 days | 338 kg |
| 2023 | 1,644 t | 522 t | 12 days | 512 kg |
| 2024 | 0 t | 0 t | 0 days | — |
| 2025 | 3,446 t | 1,104 t | 53 days | 263 kg |
Technical efficiency: EEXI (3.63 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 | Sep 29, 2026, 02:09 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Long Beach USLGB | Departure | Apr 15, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Apr 10, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Feb 19, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Feb 4, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Nov 26, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Nov 23, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Arrival | Oct 25, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Oct 25, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | Mar 29, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Mar 10, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Jan 2, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 19, 2002.
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.
Frequently asked questions
- Where is LOTUS RISING now?
- LOTUS RISING (Bulk carrier, Marshall Islands flag) was last seen on AIS on Sep 30, 2026, 03:12 UTC, under way at 11.9 kn, near Shekou Pt (South China Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was HONG KONG (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 02:24 UTC). This report does not confirm the ship’s current route.
- What kind of ship is LOTUS RISING?
- LOTUS RISING is a bulk carrier sailing under the flag of Marshall Islands, built in 2001. The vessel is 225 m long with a beam of 32 m and has a gross tonnage of 39,783.
- Who is recorded as the owner or manager of LOTUS RISING?
- Minoa Marine Ltd is recorded as ISM manager for LOTUS RISING (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for LOTUS RISING?
- Voydar has no matched sanctions record displayed for LOTUS RISING 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 LOTUS RISING. Missing records do not establish whether the ship has been detained.
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/9217656Using 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.