MIRAI
Tanker · Marshall Islands · AIS Class A
In short
MIRAI (Tanker, Marshall Islands flag) was last seen on AIS on , under way at 14.4 kn, in the North Sea. Its crew-entered AIS destination is BEANR (Antwerpen), with an ETA of Oct 4, 2026, 18:00 UTC; its reported draught is 10.2 m (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 09:29 UTC). ISM manager: SYNERGY MARITIME PRIVATE LIMITED (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Zandvliet (departed Sep 30, 2026, 09:06 UTC) to BEANR (Antwerpen)
- Vessel type
- Tanker
- Flag
- Marshall Islands
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- SYNERGY MARITIME PRIVATE LIMITED
Watch this ship
Get an email when MIRAI 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 MIRAI.
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
- 58.6469° N, 4.979° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 14.4 kn
- Course
- 183°
- Heading
- 182°
Last 30 days: 2 port calls (Zandvliet and Karsto).
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
- MIRAI
- IMO numberWhat is an IMO number?
- 9929871
- MMSIWhat is an MMSI?
- 538010289
- Call signWhat is a call sign?
- V7A5850
- Flag
- Marshall Islands
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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 |
|---|---|---|
| Left ZandvlietAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZandvlietAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KarstoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KarstoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EspevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EspevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at Lewes, Delaware | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at TEXAS CITY, Texas | USCG 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
| Date | Type | Port | Findings |
|---|---|---|---|
| Apr 5, 2025 | Vessel InspectionPSC | Lewes, Delaware | clean |
| May 15, 2023 | Vessel InspectionPSC | TEXAS CITY, Texas | clean |
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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2023 | 4,517 t | 1,409 t | 61 days | 251 kg |
| 2024 | 13,045 t | 4,136 t | 228 days | 283 kg |
| 2025 | 14,581 t | 4,686 t | 154 days | 261 kg |
Technical efficiency: EEXI (5.95 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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Zandvliet BEZVT | Sep 28, 2026, 17:46 UTC | Sep 30, 2026, 09:06 UTC | 39 h 20 min |
| Karsto NOKAR | Sep 25, 2026, 23:46 UTC | Sep 26, 2026, 22:52 UTC | 23 h 6 min |
| Espevik NOESP | Aug 30, 2026, 07:11 UTC | Sep 1, 2026, 13:56 UTC | 2 d 6 h |
| Kallo BEKOU | Jul 25, 2026, 16:14 UTC | Jul 25, 2026, 22:16 UTC | 6 h 2 min |
| Zandvliet BEZVT | Jul 12, 2026, 22:36 UTC | Jul 17, 2026, 04:12 UTC | 4 d 5 h |
| Ostermoor DEOSR | Jun 30, 2026, 14:59 UTC | Jul 11, 2026, 05:46 UTC | 10 d 14 h |
| Zandvliet BEZVT | Jun 13, 2026, 10:53 UTC | Jun 14, 2026, 21:21 UTC | 34 h 28 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.
Predicted arrival
Voydar estimates arrival at Antwerpen around Oct 14, 2026, 19:23 UTC, most likely between Oct 7, 2026, 12:02 UTC and Oct 21, 2026, 20:13 UTC. Based on 37 past transits between BEZVT and Antwerpen seen in our port calls. The crew-reported ETA is Oct 4, 2026, 18:00 UTC.
Medium (58%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Sep 26, 2026, 21:28 UTC | Draught change Reported draught went from 7.6 m to 10.1 m while in port at Karsto. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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
- Where is MIRAI now?
- MIRAI (Tanker, Marshall Islands flag) was last seen on AIS on Oct 3, 2026, 10:05 UTC, under way at 14.4 kn, in the North Sea. The crew-entered destination was BEANR (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 09:29 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MIRAI?
- MIRAI is a tanker sailing under the flag of Marshall Islands.
- Who is recorded as the owner or manager of MIRAI?
- SYNERGY MARITIME PRIVATE LIMITED is recorded as ISM manager for MIRAI (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 MIRAI?
- Voydar has no matched sanctions record displayed for MIRAI 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. MIRAI has 2 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/9929871Using 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.