EM NIKITA
Tanker · Singapore · AIS Class A
In short
EM NIKITA (Tanker, Singapore flag) was last seen on AIS on , under way at 8.1 kn, near Pulau Bukom (Strait of Malacca). Its crew-entered AIS destination is KUKUP-MY, with an ETA of Nov 21, 2026, 11:00 UTC; its reported draught is 4.7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 23:23 UTC).
Current voyage: from Singapore (departed Nov 20, 2026, 21:21 UTC) to KUKUP-MY
Last reported position: 1.1666° N, 103.6934° E · Strait of Malacca · See on the map
Watch this ship
Get an email when EM NIKITA 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
Following EM NIKITA over the last 24 hours would have sent 1 message.
- LeftSingapore
Detected from AIS, as of Nov 21, 2026, 00:28 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for EM NIKITA 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
- 1.1666° N, 103.6934° E
- Area
- Strait of Malacca
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 8.1 kn
- Course
- 304°
- Heading
- 303°
- Compass: course over ground 304°, heading 303°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 8 port calls (Singapore, Pengerang, and Keppel).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows EM NIKITA's track before the last 30 days. Voydar has recorded its port calls since October 10, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- EM NIKITA
- IMO numberWhat is an IMO number?
- 1027134
- MMSIWhat is an MMSI?
- 563251100
- Call signWhat is a call sign?
- 9VBA7
- Flag
- Singapore
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.115 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.19 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
No owner, operator or manager is recorded for this vessel yet.
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 SingaporeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SingaporeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PengerangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PengerangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SingaporeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SingaporeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Washington, District of Columbia | 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 |
|---|---|---|---|
| Sep 26, 2005 | Vessel Inspection | Washington, District of Columbia | 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.
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 |
|---|---|---|---|
| Singapore SGSIN | Nov 17, 2026, 15:49 UTC | Nov 20, 2026, 21:21 UTC | 3 d 5 h |
| Pengerang MYPGG | Nov 17, 2026, 03:37 UTC | Nov 17, 2026, 15:30 UTC | 11 h 53 min |
| Singapore SGSIN | Nov 14, 2026, 11:29 UTC | Nov 17, 2026, 03:37 UTC | 2 d 16 h |
| Singapore SGSIN | Nov 12, 2026, 01:06 UTC | Nov 14, 2026, 03:55 UTC | 2 d 2 h |
| Pengerang MYPGG | Nov 10, 2026, 03:13 UTC | Nov 10, 2026, 18:25 UTC | 15 h 13 min |
| Keppel SGKEP | Nov 9, 2026, 09:58 UTC | Nov 10, 2026, 02:04 UTC | 16 h 6 min |
| Singapore SGSIN | Nov 6, 2026, 18:10 UTC | Nov 8, 2026, 21:23 UTC | 2 d 3 h |
| Singapore SGSIN | Nov 6, 2026, 06:51 UTC | Nov 6, 2026, 09:59 UTC | 3 h 7 min |
| Keppel SGKEP | Oct 21, 2026, 23:08 UTC | Oct 23, 2026, 10:51 UTC | 35 h 43 min |
| Jurong SGJUR | Oct 18, 2026, 13:12 UTC | Oct 21, 2026, 02:00 UTC | 2 d 12 h |
| Keppel SGKEP | Oct 16, 2026, 09:28 UTC | Oct 18, 2026, 00:16 UTC | 38 h 48 min |
| Jurong SGJUR | Oct 10, 2026, 07:27 UTC | Oct 11, 2026, 04:36 UTC | 21 h 10 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 |
|---|---|---|
| Nov 17, 2026, 15:23 UTC | Draught change Reported draught went from 7.2 m to 6.3 m while in port at Pengerang. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 17, 2026, 01:47 UTC | Draught change Reported draught went from 4.4 m to 7.2 m while in port at Singapore. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 15, 2026, 03:47 UTC | Draught change Reported draught went from 4.9 m to 4.4 m while in port at Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 14, 2026, 20:11 UTC | Draught change Reported draught went from 4.3 m to 4.9 m while in port at Singapore. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 14, 2026, 10:47 UTC | Draught change Reported draught went from 5.3 m to 4.3 m after leaving Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 13, 2026, 11:53 UTC | Draught change Reported draught went from 6 m to 5.3 m while in port at Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 12, 2026, 18:11 UTC | Draught change Reported draught went from 6.5 m to 6 m while in port at Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 12, 2026, 01:11 UTC | Draught change Reported draught went from 7.2 m to 6.5 m while in port at Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 11, 2026, 17:17 UTC | Draught change Reported draught went from 4.7 m to 7.2 m after leaving Pengerang. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 10, 2026, 18:17 UTC | Draught change Reported draught went from 5.3 m to 4.7 m while in port at Pengerang. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 9, 2026, 18:17 UTC | Draught change Reported draught went from 6.3 m to 5.3 m while in port at Keppel. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 9, 2026, 08:59 UTC | Draught change Reported draught went from 7.2 m to 6.3 m after leaving Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 8, 2026, 19:06 UTC | Draught change Reported draught went from 4.4 m to 7.2 m while in port at Singapore. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 7, 2026, 12:05 UTC | Draught change Reported draught went from 5.4 m to 4.4 m while in port at Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 6, 2026, 17:23 UTC | Draught change Reported draught went from 6.2 m to 5.4 m after leaving Singapore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 23, 2026, 20:17 UTC | Draught change Reported draught went from 5.7 m to 4.5 m after leaving Keppel. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 11, 2026, 04:47 UTC | Draught change Reported draught went from 3.2 m to 7 m after leaving Jurong. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 10, 2026, 06:11 UTC | Draught change Reported draught went from 4.4 m to 3.2 m while in port at Keppel. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 1, 2026, 13:41 UTC | Draught change Reported draught went from 7.2 m to 6.2 m while in port at Keppel. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
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 EM NIKITA?
- EM NIKITA is a tanker sailing under the flag of Singapore.
- What sanctions and inspection records does Voydar hold for EM NIKITA?
- Voydar has no matched sanctions record displayed for EM NIKITA 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. EM NIKITA has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.
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 Tankers
Other tankers with full Voydar profiles, those under the flag of Singapore first. A different set each day. All 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/1027134Cite this page
EM NIKITA. Voydar (voydar.com). https://www.voydar.com/vessel/1027134-em-nikita. Retrieved November 21, 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.