St. Jude
Fishing vessel · built 1987
In short
St. Jude (Fishing vessel) has no AIS position on record with Voydar.
- Vessel type
- Fishing vessel
- Flag
- —
- Year built
- 1987
- Gross tonnage
- 167
- Size (length × beam)
- 26 m × 8 m
- Registered owner
- —
Watch this ship
Get an email when St. Jude 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 St. Jude.
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
- St. Jude
- IMO numberWhat is an IMO number?
- 8855877
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Fishing vessel
- Gross tonnageGross tonnage vs deadweight
- 167
- Length overall
- 26 m
- Beam
- 8 m
- Year built
- 1987
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 |
|---|---|---|
| Reported departure from Coos BayAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SeattleAuthority-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 |
|---|---|---|---|---|
| Coos Bay USCOB | Departure | Oct 24, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 20, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 20, 2008.
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 St. Jude now?
- Voydar has no displayable AIS position for St. Jude in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is St. Jude?
- St. Jude is a fishing vessel, built in 1987. The vessel is 26 m long with a beam of 8 m and has a gross tonnage of 167.
- What sanctions and inspection records does Voydar hold for St. Jude?
- Voydar has no matched sanctions record displayed for St. Jude 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 St. Jude. 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/8855877Using 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.