S Mermaid
Cargo ship · South Korea · built 2005 · AIS Class A
In short
S Mermaid (Cargo ship, South Korea flag) was last seen on AIS on , under way at 9.9 kn, near Hibi (North Pacific Ocean). Its crew-entered AIS destination is KR_KAN (Gwangyang), with an ETA of Nov 21, 2026, 21:00 UTC; its reported draught is 3.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 16:38 UTC). Its last detected port call was at Chiba: arrived Sep 16, 2026, left Sep 17, 2026.
- Vessel type
- Cargo ship
- Flag
- South Korea
- Year built
- 2005
- Gross tonnage
- 1,999
- Size (length × beam)
- 81 m × 14 m
- Registered owner
- —
Last reported position: 34.4161° N, 133.951° E · North Pacific Ocean · See on the map
Watch this ship
Get an email when S Mermaid reaches Gwangyang, 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 19, 2026, 20:52 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for S Mermaid 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
- 34.4161° N, 133.951° E
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 9.9 kn
- Course
- 254°
- Heading
- 255°
- Compass: course over ground 254°, heading 255°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
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.
Pro shows S Mermaid's track before the last 30 days. Voydar has recorded its port calls since September 3, 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 81 mone tick every 10 m
Beam 13.6 mPlan outline, to scale
- Name
- S Mermaid
- IMO numberWhat is an IMO number?
- 9344887
- MMSIWhat is an MMSI?
- 441366000
- Call signWhat is a call sign?
- DSPP5
- Flag
- South Korea
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- 1,999
- Deadweight (DWT)
- Source: Wikidata, record Q105765286. Added to Voydar on October 23, 2026. Licence: CC0 1.0.3,337 t
- Length overall
- 81 m
- Beam
- 13.6 m
- Year built
- 2005
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.
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 ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PyeongtaekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PyeongtaekAIS-detected | Voydar port-call detector (AIS geofence) |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred May 11, 2024衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)関門港若松区安瀬公共岸壁 若松洞海湾口防波堤灯台から真方位278°1.9海里付近
貨物船S MERMAID貨物船第八阿州山丸衝突Report published Dec 19, 2024
貨物船S MERMAIDは、着岸操船中、係留して荷役作業中の貨物船第八阿州山丸に衝突した。
- Occurred Dec 1, 2020衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)明石海峡航路 江埼灯台から真方位047°1.1海里付近
貨物船S MERMAID漁船明石丸衝突Report published Sep 30, 2021
貨物船S MERMAIDは、東南東進中、また、漁船明石丸は、北西進中、両船が衝突した。
- Occurred Feb 1, 2016衝突(単) · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)千葉港葛南区 千葉港葛南市川灯台から真方位039°690m付近
貨物船S MERMAID衝突(岸壁施設)Report published Jun 30, 2016
貨物船S MERMAIDは、出港作業中、岸壁のクレーンと衝突した。 S MERMAIDは、右舷ウイングに圧壊等を生じ、クレーンは、曲損等を生じた。
- Occurred Mar 6, 2014衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)明石海峡東方沖 兵庫県神戸市所在の平磯灯標から真方位133°3.8海里付近
貨物船ST MERMAID漁船住吉丸衝突Report published Dec 18, 2014
A船は、船長Aほか12人が乗り組み、明石海峡を通過し、船長Aが操船指揮に当たり、三等航海士及び操舵員を船橋配置に就け、約9ノット(kn)の速力(対地速力、以下同じ。)で東進していた。 船長Aは、B船を認めたものの、針路及び速力を保持して航行を続けた。 A船は、東進中、平成26年3月6日07時41分ごろ、明石海峡東方沖において、左舷船尾部とB船の左舷船尾部とが衝突した。 B船は、船長Bが1人で乗り組み、約3knの速力により、長さ約380mのワイヤに接続した漁網をえい網しながら北西進し、船長Bが、船尾甲板で船首方を向き、中腰の体勢で漁獲物の選別作業を始めた。 船長Bは、周囲を見回し、航行に支障となる船はいないものと思い、選別作業に専念していたところ、航走波による動揺で左舷方を振り向いた時、A船が目前に迫っていることが分かったが、どうすることもできず、B船の左舷船尾部とA船の左舷船尾部とが衝突し
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 |
|---|---|---|---|
| Chiba JPCHB | Sep 16, 2026, 06:27 UTC | Sep 17, 2026, 08:49 UTC | 26 h 22 min |
| Pyeongtaek KRPTK | Sep 3, 2026, 07:42 UTC | Sep 8, 2026, 21:25 UTC | 5 d 13 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.
Frequently asked questions
- What kind of ship is S Mermaid?
- S Mermaid is a cargo ship sailing under the flag of South Korea, built in 2005. The vessel is 81 m long with a beam of 13.6 m and has a gross tonnage of 1,999.
- What sanctions and inspection records does Voydar hold for S Mermaid?
- Voydar has no matched sanctions record displayed for S Mermaid 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 S Mermaid. 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
More Cargo ships
Other cargo ships with full Voydar profiles. A different set each day. All cargo ships
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/9344887Cite this page
S Mermaid. Voydar (voydar.com). https://www.voydar.com/vessel/9344887-s-mermaid. Retrieved November 19, 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.