GENESIS
Pleasure craft · United States · AIS Class A
In short
GENESIS (Pleasure craft, United States flag) was last seen on AIS on , not moving, near Baltimore (North Atlantic Ocean). Its crew-entered AIS destination is USBWI; its reported draught is 2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 09:09 UTC).
Current voyage: from Pasajes (departed Oct 1, 2026, 17:53 UTC) to USBWI
- Vessel type
- Pleasure craft
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 18 m × 5 m
- Registered owner
- —
Watch this ship
Get an email when GENESIS 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 GENESIS.
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
received- Position
- 39.2807° N, 76.6011° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 258°
- Heading
- 353°
Last 30 days: 1 port call (Pasajes).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- GENESIS
- IMO numberWhat is an IMO number?
- 9060156
- MMSIWhat is an MMSI?
- 368219430
- Call signWhat is a call sign?
- WDM5806
- Flag
- United States
- Vessel type
- Pleasure craft
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 18 m
- Beam
- 5 m
- Year built
- —
United StatesA 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 PasajesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PasajesAIS-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 |
|---|---|---|---|
| Pasajes ESPAS | Sep 30, 2026, 17:12 UTC | Oct 1, 2026, 17:53 UTC | 24 h 41 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.
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 3, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,027 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 2, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,025 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 1, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,026 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 30, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,056 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 29, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,027 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 28, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,028 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 27, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,029 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 26, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,027 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 25, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,028 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 24, 2026, 00:00 UTC | IMO used twice IMO 9060156 was broadcast by two ships (MMSI 235000097 and 368219430) 6,029 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
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 GENESIS now?
- GENESIS (Pleasure craft, United States flag) was last seen on AIS on Oct 3, 2026, 09:57 UTC, not moving, near Baltimore (North Atlantic Ocean). The crew-entered destination was USBWI (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 09:09 UTC). This report does not confirm the ship’s current route.
- What kind of ship is GENESIS?
- GENESIS is a pleasure craft sailing under the flag of United States. The vessel is 18 m long with a beam of 5 m.
- What sanctions and inspection records does Voydar hold for GENESIS?
- Voydar has no matched sanctions record displayed for GENESIS 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 GENESIS. 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/9060156Using 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.