RAM VI
Other (hazardous cat. A) · United States · AIS Class A
In short
RAM VI (Other, United States flag) was last seen on AIS on , at anchor, in the Gulf of Mexico. Its crew-entered AIS destination is NUNA BIS (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 06:50 UTC).
- Vessel type
- Other (hazardous cat. A)
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 30 m × 12 m
- Registered owner
- —
Watch this ship
Get an email when RAM VI 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.56° N, 93.4248° W
- Area
- Gulf of Mexico
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0.1 kn
- Course
- —
- Heading
- —
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-upIdentity & particulars
- Name
- RAM VI
- IMO numberWhat is an IMO number?
- 8765838
- MMSIWhat is an MMSI?
- 367035040
- Call signWhat is a call sign?
- WRA8604
- Flag
- United States
- Vessel type
- Other (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 30 m
- Beam
- 12 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.
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 26, 2026, 00:00 UTC | IMO used twice IMO 8765838 was broadcast by two ships (MMSI 367034170 and 367035040) 159 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
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 RAM VI now?
- RAM VI (Other, United States flag) was last seen on AIS on Oct 5, 2026, 06:19 UTC, at anchor, in the Gulf of Mexico. The crew-entered destination was NUNA BIS (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 06:50 UTC). This report does not confirm the ship’s current route.
- What kind of ship is RAM VI?
- RAM VI is a other (hazardous cat. a) sailing under the flag of United States. The vessel is 30 m long with a beam of 12 m.
- What sanctions and inspection records does Voydar hold for RAM VI?
- Voydar has no matched sanctions record displayed for RAM VI 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 RAM VI. 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/8765838Using 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.