SM Qingdao
Cargo ship · South Korea · built 2010 · AIS Class A
In short
SM Qingdao (Cargo ship, South Korea flag) was last seen on AIS on , under way at 21.4 kn, in the Sea of Japan. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Seattle: arrived Oct 20, 2026, left Oct 21, 2026.
- Vessel type
- Cargo ship
- Flag
- South Korea
- Year built
- 2010
- Gross tonnage
- 40,741
- Size (length × beam)
- 259 m × 32 m
- Registered owner
- —
Last reported position: 34.8667° N, 129.3201° E · Sea of Japan · See on the map
Watch this ship
SM Qingdao has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
Voydar last heard SM Qingdao on November 12, 2026. Our receivers cover coasts and busy waters, so alerts resume when it is next in range.
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 20, 2026, 22:10 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for SM Qingdao 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.8667° N, 129.3201° E
- Area
- Sea of Japan
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 21.4 kn
- Course
- 73°
- Heading
- 74°
- Compass: course over ground 73°, heading 74°
- 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 SM Qingdao's track before the last 30 days. Voydar has recorded its port calls since June 10, 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 259 mone tick every 50 m
Beam 32 mPlan outline, to scale
- Name
- SM Qingdao
- IMO numberWhat is an IMO number?
- 9395939
- MMSIWhat is an MMSI?
- 440022000
- Call signWhat is a call sign?
- D7CL
- Flag
- South Korea
- Vessel type
- Cargo ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 40,741
- Length overall
- 259 m
- Beam
- 32 m
- Year built
- 2010
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.
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
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 SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left New WestminsterAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at New WestminsterAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SeattleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Reported arrival at SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at ELIZABETH RIVER, VAAuthority-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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Apr 25, 2026 | Vessel Inspection | Seattle, Washington | clean |
| Mar 22, 2026 | Boarding | Seattle, Washington | clean |
| Mar 21, 2026 | Vessel InspectionPSC | Seattle, Washington | clean |
| Feb 3, 2026 | Vessel Inspection | Seattle, Washington | clean |
| Dec 23, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Sep 26, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Jul 2, 2025 | Vessel Inspection | Seattle, Washington | clean |
| May 22, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Apr 19, 2025 | Vessel InspectionPSC | Seattle, Washington | clean |
| Feb 4, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Dec 23, 2024 | Vessel Inspection | Seattle, Washington | clean |
| Aug 5, 2024 | Vessel Inspection | Seattle, Washington | clean |
| Jul 2, 2024 | Vessel InspectionPSC | Seattle, Washington | clean |
| Oct 27, 2022 | Vessel InspectionPSC | San Pedro, California | clean |
| Nov 22, 2021 | Vessel Inspection | PORTLAND, Oregon | clean |
| Apr 10, 2021 | Vessel InspectionPSC | Seattle, Washington | clean |
| Sep 14, 2020 | Vessel InspectionPSC | Seattle, Washington | clean |
| Aug 26, 2020 | Vessel InspectionPSC | PORTLAND, Oregon | clean |
| Aug 3, 2020 | Vessel InspectionPSC | PORTLAND, Oregon | clean |
| Sep 6, 2019 | Boarding | Seattle, Washington | 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 |
|---|---|---|---|
| Seattle USSEA | Oct 20, 2026, 20:22 UTC | Oct 21, 2026, 11:47 UTC | 15 h 26 min |
| New Westminster CANWE | Oct 16, 2026, 22:29 UTC | Oct 20, 2026, 09:58 UTC | 3 d 11 h |
| Seattle USSEA | Sep 11, 2026, 21:08 UTC | Sep 12, 2026, 14:22 UTC | 17 h 14 min |
| New Westminster CANWE | Sep 8, 2026, 02:30 UTC | Sep 11, 2026, 10:04 UTC | 3 d 7 h |
| Seattle USSEA | Jul 26, 2026, 04:05 UTC | Jul 26, 2026, 14:31 UTC | 10 h 26 min |
| New Westminster CANWE | Jul 24, 2026, 02:52 UTC | Jul 24, 2026, 09:45 UTC | 6 h 53 min |
| Seattle USSEA | Jun 13, 2026, 17:16 UTC | Jun 14, 2026, 05:15 UTC | 11 h 59 min |
| New Westminster CANWE | Jun 10, 2026, 09:32 UTC | Jun 13, 2026, 02:21 UTC | 2 d 16 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Savannah USSAV | Arrival | May 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | May 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | May 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | May 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Mar 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Mar 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | Mar 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | Mar 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Mar 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Mar 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 30, 2014.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Oct 20, 2026, 12:22 UTC | Draught change Reported draught went from 8.6 m to 11.1 m after leaving New Westminster. Voydar infers the ship probably loaded 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 SM Qingdao?
- SM Qingdao is a cargo ship sailing under the flag of South Korea, built in 2010 by HHIC Phil. The vessel is 259 m long with a beam of 32 m and has a gross tonnage of 40,741.
- What sanctions and inspection records does Voydar hold for SM Qingdao?
- Voydar has no matched sanctions record displayed for SM Qingdao 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. SM Qingdao has 29 recorded Port State Control inspections. 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 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/9395939Cite this page
SM Qingdao. Voydar (voydar.com). https://www.voydar.com/vessel/9395939-sm-qingdao. Retrieved November 20, 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.