CSL FRONTIER
Cargo ship · Bahamas · AIS Class A
In short
CSL FRONTIER (Cargo ship, Bahamas flag) was last seen on AIS on , moored, near Victoria (North Pacific Ocean). Its crew-entered AIS destination is CA VAN > CA VIC; its reported draught is 5.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 22:12 UTC). Its last detected port call was at Vancouver: arrived Sep 1, 2026, left Sep 22, 2026.
- Vessel type
- Cargo ship
- Flag
- Bahamas
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 197 m × 32 m
- Registered owner
- —
Last reported position: 48.4145° N, 123.3906° W · North Pacific Ocean · See on the map
Watch this ship
Get an email when CSL FRONTIER 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
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, 23:22 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for CSL FRONTIER 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
- 48.4145° N, 123.3906° W
- Area
- North Pacific Ocean
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 340°
- Heading
- 85°
- Compass: course over ground 340°, heading 85°
- 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 CSL FRONTIER's track before the last 30 days. Voydar has recorded its port calls since June 15, 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 197 mone tick every 25 m
Beam 32 mPlan outline, to scale
- Name
- CSL FRONTIER
- IMO numberWhat is an IMO number?
- 9228734
- MMSIWhat is an MMSI?
- 311000421
- Call signWhat is a call sign?
- C6CA8
- Flag
- Bahamas
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 197 m
- Beam
- 32 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.
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 VancouverAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VancouverAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Port McNeillAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port McNeillAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Redwood CityAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Redwood CityAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Francisco, California | 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 departure from SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET)Authority-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 |
|---|---|---|---|
| Mar 2, 2026 | Vessel InspectionPSC | San Francisco, California | clean |
| Nov 18, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Aug 15, 2025 | Vessel InspectionPSC | San Francisco, California | clean |
| Jun 9, 2025 | Vessel Inspection | Seattle, Washington | clean |
| Feb 20, 2025 | Vessel InspectionPSC | Portland, Oregon | clean |
| Aug 7, 2024 | Vessel InspectionPSC | San Francisco, California | clean |
| Jul 21, 2024 | Vessel Operational Control | San Francisco, California | clean |
| Apr 26, 2024 | Boarding | Seattle, Washington | clean |
| Jan 31, 2023 | Vessel InspectionPSC | Seattle, Washington | clean |
| Jan 31, 2023 | Boarding | Seattle, Washington | clean |
| May 27, 2022 | Vessel Operational Control | San Francisco, California | clean |
| Mar 12, 2022 | Vessel Inspection | San Francisco, California | clean |
| Mar 12, 2022 | Vessel Operational Control | San Francisco, California | clean |
| Mar 12, 2022 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jan 15, 2021 | Vessel InspectionPSC | San Francisco, California | clean |
| Nov 13, 2020 | Vessel InspectionPSC | San Francisco, California | clean |
| Nov 12, 2020 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Dec 20, 2019 | Vessel InspectionPSC | Honolulu, Hawaii | clean |
| Jul 1, 2019 | Vessel InspectionPSC | San Pedro, California | clean |
| Dec 20, 2018 | Vessel InspectionPSC | San Francisco, California | 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 |
|---|---|---|---|
| Vancouver CAVAN | Sep 1, 2026, 16:17 UTC | Sep 22, 2026, 01:03 UTC | 20 d 8 h |
| Port McNeill CAPMA | Aug 29, 2026, 05:26 UTC | Aug 30, 2026, 15:38 UTC | 34 h 12 min |
| Redwood City USRWC | Aug 18, 2026, 10:31 UTC | Aug 19, 2026, 02:11 UTC | 15 h 40 min |
| Los Angeles USLAX | Aug 1, 2026, 17:38 UTC | Aug 2, 2026, 03:32 UTC | 9 h 54 min |
| Redwood City USRWC | Jul 2, 2026, 18:16 UTC | Jul 2, 2026, 23:04 UTC | 4 h 48 min |
| Oakland USOAK | Jul 1, 2026, 06:25 UTC | Jul 1, 2026, 20:58 UTC | 14 h 32 min |
| Redwood City USRWC | Jun 21, 2026, 11:55 UTC | Jun 30, 2026, 12:48 UTC | 9 d 0 h |
| Oakland USOAK | Jun 19, 2026, 14:44 UTC | Jun 21, 2026, 00:51 UTC | 34 h 7 min |
| Port McNeill CAPMA | Jun 15, 2026, 06:27 UTC | Jun 18, 2026, 23:30 UTC | 3 d 17 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 |
|---|---|---|---|---|
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Oct 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Sep 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET) | Departure | Sep 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Sep 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Sep 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORTS OTHER THAN PORTLAND, ASTORIA, ST. HELENS, LONGVIEW, VANCOUVER AND KALAMA | Departure | Aug 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORTS OTHER THAN PORTLAND, ASTORIA, ST. HELENS, LONGVIEW, VANCOUVER AND KALAMA | Arrival | Aug 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Jul 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Jul 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORTS OTHER THAN PORTLAND, ASTORIA, ST. HELENS, LONGVIEW, VANCOUVER AND KALAMA | Departure | Jun 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORTS OTHER THAN PORTLAND, ASTORIA, ST. HELENS, LONGVIEW, VANCOUVER AND KALAMA | Arrival | Jun 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Apr 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 3, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- What kind of ship is CSL FRONTIER?
- CSL FRONTIER is a cargo ship sailing under the flag of Bahamas. The vessel is 197 m long with a beam of 32 m.
- What sanctions and inspection records does Voydar hold for CSL FRONTIER?
- Voydar has no matched sanctions record displayed for CSL FRONTIER 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. CSL FRONTIER has 50 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, those under the flag of Bahamas first. 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/9228734Cite this page
CSL FRONTIER. Voydar (voydar.com). https://www.voydar.com/vessel/9228734-csl-frontier. 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.