RICHMOND FB VICTORY
United States · AIS Class A
In short
RICHMOND FB VICTORY (Unknown, United States flag) was last seen on AIS on , under way at 2.1 kn, near San Francisco (North Pacific Ocean). Its last detected port call was at Richmond: arrived Nov 16, 2026, left Nov 17, 2026.
- Vessel type
- —
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Last reported position: 37.8504° N, 122.4174° W · North Pacific Ocean · See on the map
Watch this ship
Get an email when RICHMOND FB VICTORY 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
Following RICHMOND FB VICTORY over the last 24 hours would have sent 1 message.
- LeftRichmond
Detected from AIS, as of Nov 17, 2026, 22:30 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for RICHMOND FB VICTORY 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: Voydar for iPhone
Last reported position
received- Position
- 37.8504° N, 122.4174° W
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 2.1 kn
- Course
- 242°
- Heading
- —
- Compass: course over ground 242°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 6 port calls (Richmond, San Francisco, and Alameda).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows RICHMOND FB VICTORY's track before the last 30 days. Voydar has recorded its port calls since September 30, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- RICHMOND FB VICTORY
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 338174415
- Call signWhat is a call sign?
- VICTORY
- Flag
- United States
- Vessel type
- —
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- 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 RichmondAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RichmondAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AlamedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AlamedaAIS-detected | Voydar port-call detector (AIS geofence) |
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 |
|---|---|---|---|
| Richmond USRCH | Nov 16, 2026, 22:21 UTC | Nov 17, 2026, 16:45 UTC | 18 h 24 min |
| San Francisco USSFO | Oct 24, 2026, 19:49 UTC | Oct 28, 2026, 19:40 UTC | 3 d 23 h |
| Alameda USNGZ | Oct 24, 2026, 15:39 UTC | Oct 24, 2026, 19:38 UTC | 3 h 59 min |
| San Francisco USSFO | Oct 23, 2026, 20:37 UTC | Oct 24, 2026, 15:35 UTC | 18 h 57 min |
| Alameda USNGZ | Oct 23, 2026, 19:29 UTC | Oct 23, 2026, 20:23 UTC | 54 min |
| Alameda USNGZ | Oct 22, 2026, 21:06 UTC | Oct 22, 2026, 23:18 UTC | 2 h 12 min |
| San Francisco USSFO | Oct 11, 2026, 16:04 UTC | Oct 13, 2026, 22:46 UTC | 2 d 6 h |
| Alameda USNGZ | Oct 7, 2026, 16:49 UTC | Oct 7, 2026, 18:14 UTC | 1 h 25 min |
| Richmond USRCH | Oct 7, 2026, 15:26 UTC | Oct 7, 2026, 16:20 UTC | 54 min |
| Richmond USRCH | Sep 30, 2026, 20:06 UTC | Oct 5, 2026, 21:07 UTC | 5 d 1 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.
Frequently asked questions
- What kind of ship is RICHMOND FB VICTORY?
- RICHMOND FB VICTORY is a vessel sailing under the flag of United States.
- What sanctions and inspection records does Voydar hold for RICHMOND FB VICTORY?
- Voydar has no matched sanctions record displayed for RICHMOND FB VICTORY 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 RICHMOND FB VICTORY. 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/mmsi-338174415Cite this page
RICHMOND FB VICTORY. Voydar (voydar.com). https://www.voydar.com/vessel/mmsi-338174415-richmond-fb-victory. Retrieved November 17, 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.