Laodicea appears on the Canadian autonomous sanctions list and the EU list of designated vessels under Russia, Russia (Reg. 833/2014 Annex XLII). Verify at Global Affairs Canada.
Every vessel on:Canadian autonomous sanctions listEU list of designated vessels
Laodicea
Cargo ship · built 2005
In short
Laodicea (Cargo ship) has no AIS position on record with Voydar. It appears on 2 sanctions lists (details below).
- Vessel type
- Cargo ship
- Flag
- —
- Year built
- 2005
- Gross tonnage
- 9,611
- Size (length × beam)
- 138 m × 21 m
- Registered owner
- —
Watch this ship
Get an email when Laodicea 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 Laodicea.
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
- Laodicea
- IMO numberWhat is an IMO number?
- 9274343
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- 9,611
- Deadweight (DWT)
- Source: Wikidata, record Q117102095. Added to Voydar on September 23, 2026. Licence: CC0 1.0.12,744 t
- Length overall
- 138 m
- Beam
- 21 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.
- 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 |
|---|---|---|
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Reported departure from MobileAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at MobileAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from MENOMINEE HARBOR AND RIVER, MI AND WIAuthority-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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Monte Rosa | Name on a sanctions list | — | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) |
| San Cosmas | Name on a sanctions list | — | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| Canadian autonomous sanctions list | Russia | Monte Rosa | Mar 25, 2026 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | San Cosmas | Dec 17, 2024 | In force |
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
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 |
|---|---|---|---|---|
| Mobile USMOB | Departure | Nov 4, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Oct 31, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| MENOMINEE HARBOR AND RIVER, MI AND WI | Departure | Jun 17, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| MENOMINEE HARBOR AND RIVER, MI AND WI | Arrival | Jun 15, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Departure | Jun 13, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Arrival | Jun 13, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Departure | May 30, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Arrival | May 30, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ketchikan USKTN | Departure | Mar 8, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| KAKE HARBOR, AK | Arrival | Mar 8, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Skagway USSGY | Departure | Mar 6, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Skagway USSGY | Arrival | Mar 5, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 1, 2005.
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 Laodicea now?
- Voydar has no displayable AIS position for Laodicea in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Laodicea?
- Laodicea is a cargo ship, built in 2005 by Qingshan Shipyard. The vessel is 138 m long with a beam of 21 m and has a gross tonnage of 9,611.
- What sanctions and inspection records does Voydar hold for Laodicea?
- Laodicea appears on the Canadian autonomous sanctions list and the EU list of designated vessels under Russia, Russia (Reg. 833/2014 Annex XLII). No matched inspection records are displayed for Laodicea. 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/9274343Using 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.