Thursday 1 October 2026 Day 216 of the Hormuz crisis AIS feed live
hormuz.now Live status and ship traffic in the Strait of Hormuz
Restricted · 9/24h
How we count

How hormuz.now works

hormuz.now turns public AIS ship positions and IMF PortWatch data into a live count of Strait of Hormuz crossings, an Open, Restricted or Closed status, and a view of where ships wait, where they say they are going and how Gulf ports are faring. This page sets out every rule, threshold and caveat behind those numbers.

Where our Strait of Hormuz AIS data comes from

Live map →

Ships broadcast their position, speed, identity and type by AIS, the Automatic Identification System. A single collector on our server reads the public AIS map tiles covering a box from 24°N to 28.5°N and 54°E to 59°E (six tiles per poll) about every 20 seconds, day and night. It runs on its own schedule whether or not anyone is visiting the site. A normal poll returns well over 1,000 vessels; the latest returned 1,505.

  1. Snapshot. Each poll updates an in-memory snapshot of every vessel in the box. The live map and the ships page read from it.
  2. Crossing detector. Every new position is tested against our counting line. Each crossing is written to a database log with the vessel's name, type, size, flag, declared destination, direction and time.
  3. Fleet tracker. A second tracker times how long each commercial ship has been stationary and keeps a sampled track for ships moving near the strait.
  4. Report. Once a minute we rebuild one report from the snapshot, the crossing log, the fleet tracker and IMF PortWatch data, which we fetch every six hours. Every number on the site comes from that report, including the status.
  5. Serving. Pages and API responses are rendered from the report and cached in memory. Visitors never trigger a request to the AIS source or to PortWatch, so heavy traffic cannot slow the collector.

Satellite positions with no identity (labelled "[SAT-AIS]" on some maps) are ignored, because their IDs change on every poll and a ship cannot be followed from one poll to the next.

How we count Strait of Hormuz transits: the counting line

Transit data →

We count a transit when a ship crosses a line drawn across the eastern mouth of the strait, from the tip of the Musandam Peninsula in Oman (26.37°N 56.38°E) to the Iranian coast near Kuhestak (26.80°N 57.05°E). Every vessel has a remembered side: the Persian Gulf side or the Gulf of Oman side. The Gulf of Oman side is a polygon closed over land, so any movement between the two seas has to cross the line.

The anchorages at Larak, Bandar Abbas and Khasab lie on the Gulf side; Fujairah, Khor Fakkan and Sohar lie on the Gulf of Oman side. None is near the line, so ships waiting at anchor do not create false crossings.

A move onto the Gulf side is Inbound (westbound, into the Gulf); the reverse is Outbound (eastbound, to the Gulf of Oman). We also note which half of the line a ship used: the southern (Omani) half or the northern (Iranian) half. The split is the midpoint of the line, an approximation of the median line. Last 7 days: Northern (Iranian side) 11 · Not determined 11 · Southern (Omani side) 10.

Counting line (Musandam – Kuhestak)IRANOMANUAEPersian GulfGulf of OmanStrait of HormuzFujairahBandar Abbas
TankersCargo shipsCounting line (Musandam to Kuhestak)Faded dots are stationary

Live AIS positions of commercial ships; coastline © Natural Earth.

Rules that turn positions into crossings

RuleSettingWhy
Hysteresis bandPositions within 2 km of the line never change a ship's side.GPS jitter from ships drifting near the line cannot create crossings.
ConfirmationA side change needs 2 observations on the new side, or 1 observation at least 15 km past the line.One stray position cannot count as a transit.
Spoof filterA jump implying more than 40 knots is rejected. Moves under 1 km and gaps longer than 6 hours are exempt, and two consistent jumps re-anchor the track.Spoofed and corrupted positions are dropped, but one bad fix can never freeze a ship.
Land filterPositions on land (Natural Earth coastline) are discarded.Spoofed or corrupted positions can fall on land.
Side memoryEach ship's last confirmed side is saved to disk and kept until the ship has been unseen for 60 days.A ship that switches AIS off on one side and reappears on the other is still counted, and a restart does not double count.
Long gapsA side change first seen after more than 72 hours without AIS is stored in the ship's history but not counted in traffic figures.We cannot tell when the ship actually crossed.
Crossing timeInterpolated where the track meets the line; otherwise the midpoint of the gap.Hourly and daily counts land in the right bucket.
Distinct vesselsEvery window and every UTC day counts distinct vessels per direction.A ship shuttling back and forth counts at most once each way.

Which ships count: the commercial filter

Ships in the strait →

Headline counts include only commercial ships: vessels whose AIS type is cargo or tanker and that are at least 80 m long, or at least 5,000 deadweight tonnes when no length is reported. This approximates the vessel types in IMF PortWatch's transit count (tankers, container ships, dry bulk, general cargo and ro-ro).

Tugs, dredgers and other special craft, passenger ferries, fishing boats, pleasure craft, high-speed craft, navigation aids, vessels of unknown type, and cargo ships and tankers under 80 m are left out of the headline figures, though they still appear on the live map. In the last 7 days we logged 32 commercial crossings and 84 crossings by all vessels, including small craft (distinct vessels per direction).

Finer classes (crude, product, chemical, LNG and LPG tankers; container, bulk, general cargo and ro-ro ships) come from a second, more detailed type code, which we trust only when it agrees with the main type. Tanker size classes follow deadweight conventions: VLCC from 200,000 t, Suezmax from 120,000 t, Aframax/LR2 from 80,000 t, Panamax/LR1 from 55,000 t and MR from 25,000 t.

Corrected ship types (29 September 2026). Our earlier tracker read two of the AIS feed's ship-type codes the wrong way round: code 7 is cargo and code 8 is tanker, which we have now checked against vessel names in the live data (for example, MAERSK EDMONTON reports 7 and DHT ANTELOPE reports 8). Older "tanker" figures were really cargo ships, and older "cargo" figures were mostly tankers. The reconstructed history has been relabelled with the corrected mapping, using each ship's current AIS data where available, so tanker and cargo counts for earlier dates may differ from figures we published before.

How we decide if the Strait of Hormuz is open: the status rule

Current status →

The headline status is computed automatically every minute from the report. The rules are checked in this order, and the first that matches decides the level. "Normal" is the pre-crisis baseline of 84.8 commercial transits a day (how the baseline is set), and "PortWatch-equivalent" is our 7-day average scaled to PortWatch's count (how we calibrate against PortWatch).

StepConditionResult
1. Health gateFeed older than 30 minutes, or fewer than 300 vessels visible, or feed coverage below 50% of the last 24 hours.Unknown: "Live data delayed" or "Insufficient data". We never infer Closed from missing data.
2. ClosedNo commercial crossing for 48 hours on a healthy feed (up for at least 90% of those 48 hours), or traffic under 10% of normal and a closure declared and no protected corridor operating.Closed: "No commercial traffic" or "Closure declared".
3. OpenPortWatch-equivalent 7-day average of at least 60 a day and JMIC threat level LOW or MODERATE (or not set) and no closure declared.Open
4. OtherwiseSub-label by share of normal: under 10% (under 8.5 a day): Severely restricted; 10–40%: Restricted; 40% up to 60 a day (about 71% of normal): Partially open; 60 a day or more but a SEVERE or CRITICAL threat level or a declared closure: Traffic near normal, high threat.Restricted

The 60-a-day line is the PortWatch 7-day average that Polymarket's "Strait of Hormuz traffic returns to normal" market uses to settle (Polymarket market rules, checked 29 Sep 2026). The threat level, closure and corridor flags come from our editor-maintained context file, each with a date and a source.

Stability. A new level must hold on every rebuild for 60 minutes before the headline changes, and a move from Closed to Open always passes through Restricted first. Unknown is shown immediately but never committed, so the last confirmed level is kept for when data returns. Every committed change is logged in our status history and appears on the news page and in the Atom feed.

Editorial override. An editor can pin the headline, but only for an official declaration or a known data outage. A pinned status carries an "Editor's note" label and a source link, shows our automatic reading beside it, and can be set to expire automatically. No override is active: the current status is fully automatic.

Current inputs and result

InputNowEffect on the rule
Feed healthLiveLast good fetch Passes (stale only after 30 minutes)
Vessels visible1,505Passes (300 or more)
Feed coverage, last 24 h100%Passes (50% or more)
Commercial crossings, last 24 h9Shown with the status; the 48-hour quiet test uses the time since the last crossing ()
AIS-visible 7-day average4.6 a dayRaw count from our line
PortWatch-equivalent 7-day average4.1 a dayRaw average ÷ calibration ratio 1.11; below the 60-a-day Open threshold
Pre-crisis baseline84.8 a dayDenominator for "share of normal"
Share of normal5%Under 10% band
JMIC threat levelSEVEREJMIC Advisory Update 100 (UKMTO), 27 September 2026Blocks Open (only LOW or MODERATE allow it)
Closure declaredYes, since 2 March 2026Wikipedia: Persian Gulf Strait Authority, checked 28 September 2026Blocks Open; allows Closed if traffic is under 10% and no corridor operates
Protected corridor operatingYesFortune (CENTCOM), checked 19 September 2026Rules out "Closure declared"
ResultRestricted (Severely restricted)Level held since Automatic reading: Restricted (Severely restricted)

Why: AIS-visible commercial traffic is about 5% of normal: 4.6 a day over the past week, against 84.8 before the crisis. Ships are crossing under US naval coordination; Iran claims control and requires transit permits; the official threat level is severe.

The pre-crisis baseline: what "normal" means for Hormuz traffic

Traffic history →

We compare traffic with 84.8 commercial transits a day, 47.6 of them tankers: the IMF PortWatch daily average for the 365 days before the crisis (28 Feb 2025 – 27 Feb 2026). We recompute it from our stored copy of the IMF PortWatch series as the average daily transit count over the 365 days before Day 1, so it updates if PortWatch revises its data.

The 365 days before Day 1 include unusually quiet months (67.4 transits a day in November 2025, 55.5 in December and 58.5 in January 2026), so this baseline sits below the 2022–2024 annual averages of 91.1 to 93.5 a day (IMF PortWatch data, queried 29 Sep 2026). Measured against it, current traffic looks slightly higher as a share of normal than it would against a multi-year average.

Day 1 of the crisis is 28 February 2026; today is Day 216. Some trackers count from a later date, such as 2 March, when the IRGC confirmed the closure (Wikipedia, accessed 29 Sep 2026), so their day number is lower.

Calibration against IMF PortWatch

Both series charted →

IMF PortWatch is the reference series for Hormuz transits, but it is published in weekly batches: its latest day is 27 September 2026. Our count is live but uses a different counting line and a different AIS data source, so the two never match exactly. To apply thresholds set in PortWatch terms, such as 60 a day, we scale our count to PortWatch's.

1.11
Ratio, ours ÷ PortWatch
Applied to the status
57
Overlapping days
2 Aug to 27 Sep
267
Our transits in that period
against 241 on PortWatch
4.1
7-day average, scaled
from 4.6 a day on our line

Method: over the last 60 days we add up our daily totals and PortWatch's on every complete UTC day both cover, and divide one sum by the other. The ratio is applied only with at least 14 overlapping days, at least 30 PortWatch transits and a ratio between 0.3 and 3; otherwise the raw count is used. The traffic page charts both series side by side.

Where ships say they are going: decoding AIS destinations

Messages now →

Every AIS signal carries a destination typed in by the crew. It has no fixed format: the same port can appear as AEFJR, AE FJR, FUJAIRAH, FUJ OPL or INSIK>AEFJR, and during this crisis many crews use the field for messages instead. We call it the declared destination everywhere, because it can be wrong, out of date or not a destination at all. We never edit it; we decode it in five steps.

  1. Clean-up. The text is upper-cased and stray punctuation removed. Blank values and fillers such as 0, CLASS B, N/A, NONE, TBA, TBC, PERSIAN GULF or ARABIAN GULF count as not set.
  2. Routes. A route written FROM>TO (or with =>, -> or TO) is read as its last part, and the first part is kept as the origin. If the last part is not a port, as in AE KLF>FOR ORDERS, the whole text is searched instead.
  3. Port. We look first for a UN/LOCODE, the five-letter United Nations code for a port (AEFJR is Fujairah), with or without the space, then for a port name or common abbreviation. Our list has about 70 ports: 32 inside the Gulf, 9 on the Gulf of Oman and Arabian Sea coast just outside the strait, and about 30 common destinations further afield, from Yanbu and Karachi to Singapore and Ningbo.
  4. Country. With no port match, a country name (UAE, SAUDI, INDIA, CHINA and others) or an unlisted UN/LOCODE written with a space (OM XYZ) gives the country only.
  5. Region. Each port is placed inside the Gulf (reached from the open sea only through the strait), on the Gulf of Oman coast outside the strait, or beyond the region. A country on its own counts as beyond the region, except the eight Gulf states (the UAE, Oman, Iran, Iraq, Kuwait, Qatar, Bahrain and Saudi Arabia), which we leave as side unknown.

For every crossing we keep the destination the ship declared at that moment, so the traffic page can show where ships that crossed in the last 7 days said they were going (each ship counted once per direction). The ships page decodes the destinations of every commercial ship in the region now.

Commercial ships in the region now, by declared destination

Inside the Gulf
148
Gulf of Oman, outside the strait
469
Beyond the region
38
Awaiting orders
41
Side unknown or unrecognised
90
Not set
13

Messages we look for

Whatever else the text says, we also check it for these messages. One destination can carry several. Counts are commercial ships in the region broadcasting each message now.

MessageMatched text (examples)What it saysShips now
Crew or owner nationality broadcastCHINESE CREW ONBOARD, ALL CREW …, a nationality followed by CREW, OWNER or FLAGWho is on board or who owns the ship, not where it is going.15
Armed guards declaredARMED GUARD, SECURITY TEAM ON BOARD, PCASPThe ship says armed security is on board.1
Neutrality messageNO CONTACT WITH ISRAEL, NOT AFFILIATED, NEUTRALThe ship says it has no link to a party in the conflict.0
Humanitarian cargo declaredFOOD FOR IRAN, HUMANITARIAN, AID, WFPThe ship says it carries food or aid.1
Heading for scrappingFOR BEACHING, SCRAP, DEMOLITION, ALANG, GADANIThe ship is bound for a ship-breaking yard.1
Awaiting ordersFOR ORDERS, TO ORDERNo destination fixed yet; the ship waits for instructions.47
Waiting outside port limitsOPL, ANCHORAGE, WAITING, DRIFTINGThe ship is at anchor or drifting outside a port.53

Messages are self-declared, and we cannot verify them. Pattern matching is imperfect: unusual spellings go unrecognised, and a text that mentions a nationality for another reason can be misread. Ships with anonymous satellite positions are excluded.

How long ships have been waiting near the strait

Waiting times now →

We time how long each large cargo ship or tanker in our area has been stationary. Tracking began on , so no wait can be measured from before then: a ship already at anchor that day has its clock start then, and its wait is shown as "at least".

RuleSetting
StationaryA commercial ship (cargo or tanker, 80 m or more) reporting a speed under 1 knot.
Fresh positions onlyPosition reports more than 6 hours old are ignored.
Start of the waitThe time of the first position report under 1 knot.
DriftMoving more than 3 km from where it stopped restarts the clock; any report at 1 knot or more ends the wait.
Waiting nowShips seen in the last hour. Ships unseen for 24 hours are forgotten.
RestartsWaiting clocks are saved to our database every 5 minutes, so a server restart does not reset them.
"At least"Any wait that began within an hour of tracking starting is flagged, because the real wait is longer.
By anchorageFor each port or anchorage area: ships waiting, their deadweight, the median wait, and how many have waited more than 24 hours and more than 7 days.
644
commercial ships stationary now
38.4m t deadweight
Waiting forShips
Under 1 day630
1–3 days14
3–7 days0
1–2 weeks0
2 weeks or more0

Stationary does not always mean queuing for the strait: a ship may be alongside a berth, refuelling at Fujairah or waiting for orders. The "ships waiting" counts on each side of the strait use the live snapshot (commercial ships under 1 knot with a position less than 6 hours old), so they can differ slightly from the waiting-time total. Both cover only our AIS area.

AIS-silent ships near the Strait of Hormuz

Silent ships now →

Our AIS source keeps listing a ship for a while after its last position report. We flag a commercial ship as AIS-silent when its most recent position is more than 6 hours old and lies within 150 km of the counting line. We show its last known position, the time of that fix, its side of the strait and its distance from the line.

Silence has several causes: a transponder switched off (a "dark" ship), a ship out of range of the receivers our source relies on, or jamming and interference. It is not evidence of wrongdoing. Ships that drop out of the feed altogether are not listed, so this is a floor, not a count of every dark ship.

A silent ship cannot be seen crossing. If it reappears on the other side of the line, our side memory still records the crossing, unless the gap is longer than 72 hours.

48
commercial ships near the strait with AIS silent for 6+ hours
switched off, out of range or jammed

Ship tracks: how we sample positions

For commercial ships moving at 1 knot or more within 150 km of the counting line, we store at most one position every 5 minutes per ship: time, position, speed and course. Samples are written to our database in batches and deleted after 7 days. Stationary ships are not sampled (their waiting time is recorded instead), and position reports more than 6 hours old are skipped.

Each vessel page draws the ship's track for the last 7 days; the vessel API returns the last 48 hours. A gap in a track means we had no fresh position: the ship was stationary, outside the 150 km radius, or silent.

Gulf ports: how we compare activity with IMF PortWatch

All 25 ports →

The ports pages use IMF PortWatch's daily port data (its Daily_Ports_Data service) for 25 ports whose activity tells the Hormuz story: export terminals inside the Gulf that depend on the strait, and the outlets that bypass it.

Oil and gas terminals inside the Gulf (12)

Ras Tanura, Juaymah, Jubail, Ras Laffan, Mesaieed (Umm Said), Mina al Ahmadi, Umm Qasr, Kharg Island, Bandar-e Pars (Assaluyeh), Ruwais, Das Island, Sitrah

Container and general ports inside the Gulf (7)

Jebel Ali, Khalifa Port, Hamad Port, Dammam, Shahid Rajaee (Bandar Abbas), Sharjah, Mina Saqr

Ports outside the strait (bypass routes) (6)

Fujairah, Khor Fakkan, Sohar, Duqm, Yanbu (King Fahd Port), Chabahar

StepMethod
SourceDaily port calls (all ships, and tankers, container ships and dry bulk carriers separately) and estimated import and export volumes in metric tonnes, which PortWatch derives from satellite AIS.
FetchingEvery six hours, with the last 7 days fetched again each time because PortWatch revises recent data. We store daily rows from 1 January 2024.
NormalThe daily average over the 365 days before Day 1 (28 February 2025 to 27 February 2026).
NowThe daily average over each port's latest 30 days of data, ending on its latest date.
Share of normalNow ÷ normal, for port calls and for exports. We show no port-call percentage for a port that averaged under 1 call a day before the crisis, where a percentage would mislead.
Weekly chartPort calls per week for the 30 weeks to the latest date; the dashed line is the pre-crisis weekly average.
Live shipsFor the ports inside our AIS area (Jebel Ali, Khalifa Port, Shahid Rajaee (Bandar Abbas), Sharjah, Mina Saqr, Fujairah, Khor Fakkan, Sohar), the number of commercial ships stationary in the matching area now, updated every minute.
Port factsShare of the country's maritime exports and main industry, from PortWatch's ports database, refreshed weekly.
RefreshPort figures are recomputed every 30 minutes.

PortWatch port figures are estimates from satellite AIS, published several days behind (the newest port data we hold is for 25 September 2026), so every port shows the date of its latest data. Ships with AIS switched off are missed, export tonnage is an estimate rather than customs data, and port calls count visits, not cargo. Port data © IMF PortWatch; the comparisons are ours.

Tanker tonnage through the strait: deadweight, not cargo

Oil and LNG →

IMF PortWatch's daily data for the strait include the combined deadweight tonnage of the ships crossing it, by vessel type, and we use the tanker figure. Deadweight is the most a ship can carry, including fuel and stores, so this measures the carrying capacity of the tankers passing through, not the oil on board: an empty tanker counts the same as a full one, and both directions are included.

Normal is the average tanker deadweight a day over the 365 days before Day 1, computed only when at least 300 of those days are stored. Now is the average over PortWatch's latest 7 days (and 30 days), and the percentage compares the 7-day average with normal. The chart covers the last 120 days.

Like every PortWatch figure it counts only tankers visible on AIS and arrives several days late. Sources that also track dark tankers report far higher oil volumes; the oil page sets them side by side.

1%
of normal tanker deadweight, 7-day average
18k t a day to 27 Sep, against 2.2m t before the crisis
15k t
a day over PortWatch's latest 30 days
latest day 27 September 2026

Why do Strait of Hormuz ship counts differ?

FAQ →

Trackers count different things. AIS-only sources, including IMF PortWatch and hormuz.now, miss ships that switch their transponders off, and many do during this crisis. Others add satellite imagery and radio signals, count only some fleets, or report the ships they escort. AIS-visible counts can undercount real traffic by an order of magnitude.

Who counts what

SourceWhat it countsHow
IMF PortWatchDaily transits of tankers, container ships, dry bulk, general cargo and ro-ro vessels through the Strait of HormuzAIS only; published weekly, several days behind
WindwardAll transits it can detect, including ships running darkAIS plus satellite imagery and radio-frequency detection
KplerCommercial vessel movements and oil and product volumesAIS combined with satellite and other signals
Lloyd's List IntelligenceTransits by non-Iranian-linked cargo vessels over 10,000 dwtIts own vessel tracking; Iranian-linked and smaller ships excluded
US NCAGS (Naval Cooperation and Guidance for Shipping)Merchant transits the US Navy coordinates through the southern corridor in Omani watersUS Navy reporting of the ships it coordinates (source for the corridor: Fortune (CENTCOM), 19 Sep)
hormuz.nowDistinct commercial ships (cargo and tankers of 80 m or more) with AIS on, crossing the Musandam to Kuhestak linePublic AIS, polled about every 20 seconds; no satellite imagery

Latest figures from each source

SourceLatest figureWhat it countsDate
hormuz.now9 crossings in the last 24 h · 4.6 a day over 7 daysCommercial ships (cargo and tankers ≥80 m) with AIS on, crossing our counting lineLive
IMF PortWatch1 transit on 27 Sep · 3.1 a day over 7 daysSatellite AIS; tankers, container, dry bulk, general cargo and ro-ro ships27 Sep
Windward17 transits on 28 Sep (6 with AIS off)AIS plus satellite imagery and radio-frequency detection; includes ships running dark.28 Sep
Windward24 transits on 27 Sep (14 with AIS off, 11 via the southern corridor)AIS plus satellite imagery and radio-frequency detection; includes ships running dark.27 Sep
Lloyd's List Intelligence346 transits in August 2026 (191 westbound, 155 eastbound)Non-Iranian-linked vessels over 10,000 dwt.9 Sep

Examples of the gap

PeriodPortWatchOther count
August 2026146346, 2.4 times PortWatchLloyd's List Intelligence: non-Iranian-linked vessels over 10,000 dwt
27 September 2026124, 24 times PortWatchWindward, including 14 with AIS off

Sources: IMF PortWatch data, queried 29 Sep 2026; Lloyd's List Intelligence, 9 Sep 2026; Windward, data as of 28 Sep 2026.

Limitations: dark ships, GPS jamming and what AIS misses

Dark ships

Ships of 300 gross tonnes and above on international voyages must carry AIS, but a master may switch it off when broadcasting would compromise safety or security (IMO, accessed 29 Sep 2026; IMO Resolution A.1106(29)). Many ships cross Hormuz dark during this crisis: on 27 September 2026 Windward counted 14 of 24 transits with AIS off (Windward, data as of 28 Sep 2026). A ship that goes dark and reappears on the other side is still counted by our side memory, unless the gap exceeds 72 hours; a ship that stays dark is not counted at all. We list ships near the strait that have gone quiet as AIS-silent.

GNSS jamming and spoofing

Jamming and spoofing of satellite navigation can place ships in the wrong position, on land or jumping across the water. Windward reported 110 vessels affected by GPS jamming on 28 September 2026 (Windward, data as of 28 Sep 2026). We discard positions on land and jumps faster than 40 knots, and the 2 km band absorbs jitter near the line, but a consistently spoofed track can still be wrong.

Warships and escorts

Most warships do not broadcast AIS, and those that do are normally left out by our commercial filter, which keeps only cargo ships and tankers. Merchant ships crossing under naval coordination are counted only if their AIS is on.

Coverage limited to our box

We see only 24–28.5°N and 54–59°E. That covers the strait, Dubai and Jebel Ali, Fujairah, Khor Fakkan, Bandar Abbas and Sohar, but not upper-Gulf ports such as Ras Tanura, Kuwait or Ras Laffan, so fleet and waiting counts describe our area, not the whole Gulf. Crossing counts are unaffected, because the line sits well inside the box. Ship type, size and declared destination are self-reported in AIS and can be wrong or missing.

Reconstructed history

Our crossing log starts on 20 April 2026. The live tracker described on this page recorded its first counted crossing on 28 September 2026; crossings before that are reconstructed from an earlier tracker that stored only a few positions per ship inside a smaller box (26.10–26.95°N, 55.95–56.95°E). They are estimates and can miss crossings north-east of that box. Reconstructed crossings are marked "est." in tables; days counted entirely by the earlier tracker are drawn hatched in charts and labelled legacy in the daily dataset (mixed when both trackers contributed).

Live countReconstructed (earlier method)

Fujairah bunkering and "waiting" ships

Fujairah, on the UAE's east coast just outside the strait, is a major bunkering hub where tankers refuel (Baird Maritime, 22 Jul 2025). Ships stationary there may be refuelling, loading or waiting for orders rather than queuing for the strait, so our count of commercial ships waiting on the Gulf of Oman side (479 now) can overstate the queue for the strait. Ships that approach and turn back without crossing the line are not counted as transits.

Data health

● Live
Live
Feed
live up to 5 min old, delayed up to 30, then stale
1,505
Vessels visible
normally well over 1,000; under 300 means Unknown
100%
Coverage, last 24 h
5-minute intervals with a good poll
6/6
Tiles, last poll
no failed polls in a row
Last good fetch
IMF PortWatch, latest day
27 September 2026
PortWatch last checked
Waiting times tracked since
30 September 2026

If the feed is stale, fewer than 300 vessels are visible or coverage drops below 50%, the status switches to Unknown rather than guessing. Machine-readable health: /api/health.

Open Strait of Hormuz data and API

Open data →

Everything described on this page is published as free open data under CC BY 4.0: the live status, daily crossings (CSV and JSON), individual crossings, ships waiting, AIS-silent ships and declared destinations, Gulf port activity derived from IMF PortWatch, GeoJSON of the counting line and an Atom feed. Endpoints, formats, caching and how to credit us are on the open data page.

To show the live status on your own site or README, use our embeddable status badge.

Data sources and credits

  • Live vessel positions: public AIS, the positions broadcast by the ships themselves, read from public AIS map tiles about every 20 seconds.
  • Daily transits, tanker tonnage and the pre-crisis baseline: IMF PortWatch Strait of Hormuz chokepoint data, read from its public ArcGIS service every six hours. © IMF PortWatch.
  • Gulf ports: IMF PortWatch daily port data and ports database, read at the same time. © IMF PortWatch.
  • Coastlines and land filter: Natural Earth 1:10m land (public domain).
  • Live map tiles: OpenFreeMap, with map data © OpenStreetMap contributors.
  • Context: the JMIC threat level, closure and corridor flags, headlines and other trackers' counts are kept in an editor-maintained file; every item carries a date and a source link. Last reviewed 29 September 2026.

Changelog

  • New data: declared destinations and broadcast messages, waiting times, AIS-silent ships, sampled tracks, 25 Gulf ports and tanker tonnage from IMF PortWatch. API documentation moved to the open data page.
  • Redesign: new pages for traffic, ships, oil, the map, the timeline and news; the status rule, this methodology, the open API and the embeddable badge documented.
  • Gate-crossing method: transits are now counted when a ship crosses the Musandam to Kuhestak line, with hysteresis, confirmation, spoof and land filters and side memory, replacing entry and exit through a small box. Earlier days were rebuilt with the new method and marked as reconstructed.
  • Corrected ship types: codes 7 (cargo) and 8 (tanker) had been swapped in the earlier tracker; the reconstructed history was relabelled.
  • First data: earliest crossing in our log.

Disclaimer

hormuz.now is an independent information service and not an official source. AIS data can be delayed, incomplete, spoofed or switched off, and our counts cover only AIS-visible ships. Nothing here is navigational, security, legal or investment advice: mariners should follow official advisories such as JMIC and UKMTO and their flag state, company and naval guidance.

Related: Is the Strait of Hormuz open? · Live ship map · Daily transit data · Ships in the strait · Gulf ports · Oil and LNG flows · Map and geography · Crisis timeline · News · FAQ · Open data

Live AIS data as of · 1,505 vessels visible in the region. Counts are AIS-visible only and miss ships running dark. How we count.