Where is Ocean Reliance now?

Ocean Reliance (Tug, United States flag) was last seen on AIS on Oct 6, 2026, 16:07 UTC, under way at 10.9 kn, near Los Angeles (North Pacific Ocean). The crew-entered destination was SFSB (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:30 UTC). This report does not confirm the ship’s current route.

What kind of ship is Ocean Reliance?

Ocean Reliance is a tug sailing under the flag of United States, built in 2002. The vessel is 179 m long with a beam of 23 m and has a gross tonnage of 963.

What sanctions and inspection records does Voydar hold for Ocean Reliance?

Voydar has no matched sanctions record displayed for Ocean Reliance 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 Ocean Reliance. Missing records do not establish whether the ship has been detained.

Ocean Reliance

Tug · United States · built 2002 · AIS Class A

IMO9275438MMSI369703000Call signWADYLast AIS position Oct 6, 2026, 16:07 UTC

Open in Terminal

In short

Ocean Reliance (Tug, United States flag) was last seen on AIS on Oct 6, 2026, 16:07 UTC, under way at 10.9 kn, near Los Angeles (North Pacific Ocean). Its crew-entered AIS destination is SFSB, with an ETA of Oct 8, 2026, 10:00 UTC; its reported draught is 7.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:30 UTC). Managing owner (USCG): OCEAN RELIANCE 550-3 LLC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).

Vessel type: Tug
Flag: United States
Year built: 2002
Gross tonnage: 963
Size (length × beam): 179 m × 23 m
Managing owner (USCG): OCEAN RELIANCE 550-3 LLC

Watch this ship

Get an email when Ocean Reliance arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received Oct 6, 2026, 16:07 UTC

Position: 33.6356° N, 118.3446° W
Area: North Pacific Ocean
StatusWhat do AIS statuses mean?: Under way using engine
Speed: 10.9 kn
Course: 262°
Heading: 260°

33.6356° N, 118.3446° W

Open the full live map →

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.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name: Ocean Reliance
IMO numberWhat is an IMO number?: 9275438
MMSIWhat is an MMSI?: 369703000
Call signWhat is a call sign?: WADY
Flag: United States
Vessel type: Detailed type from WikidataTug
AIS ship type: Tanker
Gross tonnageGross tonnage vs deadweight: 963
Deadweight (DWT): Source: Wikidata, record Q117102108. Added to Voydar on September 23, 2026. Licence: CC0 1.0.455 t
Length overall: 179 m
Beam: 23 m
Year built: 2002

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.

Managing owner (USCG): OCEAN RELIANCE 550-3 LLC(not linked to a company record)
Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · confidence 0.9 · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by IMO number and call sign. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
Ship radio licensee (FCC): FAIRWATER TANKER MANAGEMENT LLC(not linked to a company record)
Source: FCC Universal Licensing System — ship station licences · since 2022 · reported · confidence 0.9 · retrieved Oct 6, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.

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
Dec 2, 2016	Reported arrival at OTHER PUGET SOUND AREA PORTS, WA (NET)Authority-reported	USACE foreign traffic vessel entrances & clearances
Nov 27, 2016	Reported departure from OTHER PUGET SOUND AREA PORTS, WA (NET)Authority-reported	USACE foreign traffic vessel entrances & clearances
Nov 22, 2016	Reported arrival at PortlandAuthority-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.

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
OTHER PUGET SOUND AREA PORTS, WA (NET)	Arrival	Dec 2, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Nov 27, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Portland USPDX	Arrival	Nov 22, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Nov 15, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Arrival	Nov 2, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Oct 31, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Arrival	Oct 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Oct 21, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Arrival	Jun 25, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Jun 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Arrival	Jun 17, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
OTHER PUGET SOUND AREA PORTS, WA (NET)	Departure	Jun 14, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: August 19, 2003.

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 6, 2026, 06:25 UTC	Draught change Reported draught went from 6.4 m to 7.3 m while in port at Los Angeles. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1	Medium (65%)
Sep 28, 2026, 14:06 UTC	Draught change Reported draught went from 7 m to 6.4 m while in port at Los Angeles. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1	Medium (65%)

When

What we observed

Confidence

Oct 6, 2026, 06:25 UTC

Draught change

Reported draught went from 6.4 m to 7.3 m while in port at Los Angeles. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

Sep 28, 2026, 14:06 UTC

Draught change

Reported draught went from 7 m to 6.4 m while in port at Los Angeles. Voydar infers the ship probably discharged 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.

How these are computed →

Frequently asked questions

Where is Ocean Reliance now?: Ocean Reliance (Tug, United States flag) was last seen on AIS on Oct 6, 2026, 16:07 UTC, under way at 10.9 kn, near Los Angeles (North Pacific Ocean). The crew-entered destination was SFSB (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:30 UTC). This report does not confirm the ship’s current route.
What kind of ship is Ocean Reliance?: Ocean Reliance is a tug sailing under the flag of United States, built in 2002. The vessel is 179 m long with a beam of 23 m and has a gross tonnage of 963.
Who is recorded as the owner or manager of Ocean Reliance?: OCEAN RELIANCE 550-3 LLC is recorded as Managing owner (USCG) for Ocean Reliance (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Ocean Reliance?: Voydar has no matched sanctions record displayed for Ocean Reliance 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 Ocean Reliance. 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/9275438

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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