Skip to content

COLLETTE C

Tug · United States · built 1978 · AIS Class A

IMO7819498MMSI303200000Call signWDP2208Last AIS position Oct 4, 2026, 00:19 UTC

In short

COLLETTE C (Tug, United States flag) was last seen on AIS on , not moving, near Los Angeles (North Pacific Ocean). Its crew-entered AIS destination is US VA3; its reported draught is 3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 23:50 UTC).

Current voyage: from Thenard (departed Sep 18, 2026, 19:36 UTC) to US VA3

Vessel type
Tug
Year built
1978
Gross tonnage
—
Size (length × beam)
21 m × 7 m
Registered owner
—

Watch this ship

Get an email when COLLETTE C 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 COLLETTE C.

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

received
Position
33.7533° N, 118.2238° W
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
326°
Heading
249°
33.7533° N, 118.2238° W
Open the full live map →

Last 30 days: 7 port calls (Thenard).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)

Try the live demo, no sign-up

Identity & particulars

Name
COLLETTE C
IMO numberWhat is an IMO number?
7819498
MMSIWhat is an MMSI?
303200000
Call signWhat is a call sign?
WDP2208
Vessel type
Tug
AIS ship type
Towing (long/wide)
Length overall
21 m
Beam
7 m
Year built
1978

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.

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.

DateEventSource
Left ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Left ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Left ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ThenardAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from San FranciscoAuthority-reportedUSACE 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.

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

PortArrivedDepartedTime in port
Thenard USOJLSep 18, 2026, 14:26 UTCSep 18, 2026, 19:36 UTC5 h 10 min
Thenard USOJLSep 15, 2026, 15:15 UTCSep 18, 2026, 13:56 UTC2 d 22 h
Thenard USOJLSep 14, 2026, 12:48 UTCSep 14, 2026, 14:00 UTC1 h 12 min
Thenard USOJLSep 14, 2026, 03:36 UTCSep 14, 2026, 12:40 UTC9 h 4 min
Thenard USOJLSep 12, 2026, 00:15 UTCSep 13, 2026, 23:21 UTC47 h 6 min
Thenard USOJLSep 8, 2026, 03:23 UTCSep 9, 2026, 02:23 UTC23 h 0 min
Thenard USOJLSep 5, 2026, 00:30 UTCSep 8, 2026, 01:09 UTC3 d 0 h
Thenard USOJLJun 19, 2026, 20:18 UTCJun 19, 2026, 22:27 UTC2 h 9 min
Thenard USOJLJun 9, 2026, 23:04 UTCJun 13, 2026, 23:16 UTC4 d 0 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

PortRecordDate (UTC)BerthSource
Oakland USOAKArrivalJun 20, 2011(date only)—USACE foreign traffic vessel entrances & clearances
San Francisco USSFODepartureJun 6, 2011(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: June 6, 2011.

Frequently asked questions

Where is COLLETTE C now?
COLLETTE C (Tug, United States flag) was last seen on AIS on Oct 4, 2026, 00:19 UTC, not moving, near Los Angeles (North Pacific Ocean). The crew-entered destination was US VA3 (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 23:50 UTC). This report does not confirm the ship’s current route.
What kind of ship is COLLETTE C?
COLLETTE C is a tug sailing under the flag of United States, built in 1978. The vessel is 21 m long with a beam of 7 m.
What sanctions and inspection records does Voydar hold for COLLETTE C?
Voydar has no matched sanctions record displayed for COLLETTE C 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 COLLETTE C. 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/7819498
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans