PACIFIC RELIANCE
Tanker · United States · AIS Class A
In short
PACIFIC RELIANCE (Tanker, United States flag) was last seen on AIS on , under way at 11.8 kn, near Baytown (Gulf of Mexico). Its crew-entered AIS destination is GALVESTON; its reported draught is 8.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 13:55 UTC).
Current voyage: from Baytown (departed Sep 27, 2026, 02:49 UTC) to GALVESTON
- Vessel type
- Tanker
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 205 m × 23 m
- Registered owner
- —
Watch this ship
Get an email when PACIFIC 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- Position
- 29.6498° N, 94.9692° W
- Area
- Gulf of Mexico
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.8 kn
- Course
- 161°
- Heading
- 160°
Last 30 days: 1 port call (Baytown).
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-upIdentity & particulars
- Name
- PACIFIC RELIANCE
- IMO numberWhat is an IMO number?
- 9386548
- MMSIWhat is an MMSI?
- 367036000
- Call signWhat is a call sign?
- WDI7757
- Flag
- United States
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 205 m
- Beam
- 23 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.
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 BaytownAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BaytownAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PAULSBORO, NJAuthority-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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Baytown USHPY | Sep 25, 2026, 14:20 UTC | Sep 27, 2026, 02:49 UTC | 36 h 29 min |
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 |
|---|---|---|---|---|
| Galveston USGLS | Arrival | May 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Mar 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 26, 2016.
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 |
|---|---|---|
| Sep 27, 2026, 01:49 UTC | Draught change Reported draught went from 9.1 m to 6.5 m while in port at Baytown. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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
- Where is PACIFIC RELIANCE now?
- PACIFIC RELIANCE (Tanker, United States flag) was last seen on AIS on Oct 5, 2026, 17:50 UTC, under way at 11.8 kn, near Baytown (Gulf of Mexico). The crew-entered destination was GALVESTON (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 13:55 UTC). This report does not confirm the ship’s current route.
- What kind of ship is PACIFIC RELIANCE?
- PACIFIC RELIANCE is a tanker sailing under the flag of United States. The vessel is 205 m long with a beam of 23 m.
- What sanctions and inspection records does Voydar hold for PACIFIC RELIANCE?
- Voydar has no matched sanctions record displayed for PACIFIC 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 PACIFIC 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/9386548Using 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.