PRIVATEER Maritime Analytics Internal working artifact · not for external release

Newest position— Board built— Next refresh—

Beta Gulf of Oman · demarcation line watch

Ras al Hadd Line Watch

Beta. Not for operational decisions on its own. Everything here is derived from vessel self-reported AIS, assembled as accurately as the available data allows, and shown with its own limits attached. Positions are up to 30 minutes old, nothing is corroborated by a second source, and no detector here has passed an acceptance test. Figures may be incomplete or wrong where the feed was incomplete, and absence of a vessel is not evidence it was not there. Verify anything that would drive an action.

Vessels on course to cross the Ras al Hadd – Jiwani line, grouped by how long until they cross. Times already account for how old each position is. Select any contact to pin its 0-day track to the chart; select several to compare. Built from Lloyd’s AIS only.

Inside 4 hours15 Crossing before the warning window closes

4 to 8 hours12 The window the tasking asks for

Feed latency 30min Median age of each last fix. The binding constraint, not the geometry.

Worst position error ±32nm How far a contact could have moved since its last fix

AIS off events 0 Across 0 of the closing contacts over 0 days

Identity flags0 Position discontinuities or duplicate-MMSI signatures

Sanctioned calls0 Port calls in an OFAC-program jurisdiction

Approach chart

MIL-STD-2525D frames · drag to pan, scroll to zoom · click a contact to pin its track

Unknown 36 Friend 0 Neutral 0 Hostile 0 Other vessel, not closing on the line 486 Every contact is an unknown. Affiliation needs a determination AIS cannot make.

Closing on the line

Type

Size

Speed under 5 kn 5–10 kn over 10 kn

Flags

Longest AIS gap under 4 h 4–12 h over 12 h

Marked

Cleared, not a target

Marked by hand on this board. The system clears nothing on its own.

Marked as target

An analyst's judgement recorded here. Not a confirmation: that needs a second source this board does not have.

Unknown, needs investigation

Everything not yet marked. A prioritized tasking queue for imagery, not an identification.

Marks are stored in this browser only. They are not shared with other viewers, do not reach the record, and are lost if site data is cleared. Treat them as a working scratchpad, which is the analyst workspace-state gap (GAP-046) still open in the requirement stack.

What this board does not tell you

AIS only. Every figure here is the vessel's own broadcast. A vessel manipulating AIS appears here exactly as it intends to.
No confidence score is attached. The detector families that would support one have no acceptance criteria yet (GAP-032).
eta_from_now_h already subtracts feed latency. dr_uncertainty_nm is how far the vessel could have moved since its last fix.
Vessel length and beam come from the AIS message-5 dimension fields: the vessel's own declaration, not an independent measurement.
Coverage is not stated. No gap-detection contract exists (GAP-044), so an absence here is not evidence of absence.
Sanctioned calls are a jurisdiction screen, not an OFAC designation. There is no published list of OFAC-sanctioned ports. This flags port calls whose country carries an OFAC country program, derived from the AOI layer's own country field. It is not a named-entity screen against the SDN list, and it is not legal advice.
Vessel length and beam are self-declared, taken from the AIS message-5 dimension fields. They are what the vessel says about itself, not an independent measurement, and implausible values are discarded rather than corrected.
Identity flags are facts about the data, not diagnoses. A position reported in two places at once is most likely a duplicate or cloned MMSI; a bad fix and a deliberate spoof look the same from AIS alone.
History findings are geometric facts about a track scored against R&D-bench AOI layers. A zone visit means a reported position fell inside a polygon, nothing more.