Valovine
Bulk carrier · built 2016
In short
Valovine (Bulk carrier) has no AIS position on record with Voydar. ISM manager: ALPHA ADRIATIC SHIPMANAGEMENT PTE LTD (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 2016
- Gross tonnage
- 30,092
- Size (length × beam)
- 189 m × 32 m
- ISM manager
- ALPHA ADRIATIC SHIPMANAGEMENT PTE LTD
Watch this ship
Get an email when Valovine 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 Valovine.
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
No AIS position on record for this vessel. Identity and particulars are 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
- Valovine
- IMO numberWhat is an IMO number?
- 9606120
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 30,092
- Deadweight (DWT)
- Source: Wikidata, record Q117027486. Added to Voydar on September 23, 2026. Licence: CC0 1.0.52,000 t
- Length overall
- 189 m
- Beam
- 32 m
- Year built
- 2016
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.
| Date | Event | Source |
|---|---|---|
| Reported arrival at PORT OF PLAQUEMINES, LAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PORT OF PLAQUEMINES, LAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at MobileAuthority-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 |
|---|---|---|---|---|
| 2019 | 3,735 t | 1,192 t | 59 days | 395 kg |
| 2020 | 2,217 t | 710 t | 30 days | 306 kg |
| 2021 | 4,214 t | 1,342 t | 50 days | 305 kg |
| 2023 | 2,127 t | 673 t | 27 days | 271 kg |
| 2025 | 5,141 t | 1,628 t | 57 days | 348 kg |
Technical efficiency: EEXI (4.33 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 |
|---|---|---|---|---|
| PORT OF PLAQUEMINES, LA | Arrival | Nov 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Departure | Nov 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Nov 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Nov 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Departure | Oct 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Arrival | Oct 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 26, 2016.
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 Valovine now?
- Voydar has no displayable AIS position for Valovine in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Valovine?
- Valovine is a bulk carrier, built in 2016 by Uljanik. The vessel is 189 m long with a beam of 32 m and has a gross tonnage of 30,092.
- Who is recorded as the owner or manager of Valovine?
- ALPHA ADRIATIC SHIPMANAGEMENT PTE LTD is recorded as ISM manager for Valovine (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 Valovine?
- Voydar has no matched sanctions record displayed for Valovine from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Valovine. 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/9606120Using 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.