Strikes on nineteen Iranian sites, mapped by Telegram within hours
Open-source mapping channels logged impacts across the Strait of Hormuz and into Khuzestan within hours of the first US strike on 13 July 2026, though the kill-list itself remains officially unconfirmed.
By 03:00 UTC on 13 July 2026, three Telegram channels had reached consensus on a specific list of places: Qeshm, Sirik, Bandar Abbas, Bandar-e-Jask, Bushehr, Khondab, Bandar-e-Mahshahr, Omidiyeh, Behbehan, Andimeshk, Dezful, and Ahvaz. The geolocators at GeoPWatch and AMK_Mapping published the same string of names within minutes of each other, in two paired posts at 02:43 and 02:49 UTC, and one more at 03:01 UTC. Three hours earlier, the channel intelslava had circulated a shorter list of nineteen locations, focused on the southern coast (Qeshm, Sirik, Bandar Abbas, Jask, Bushehr, Bandar Mahshahr, Abadan, Khorramshahr), and the gap between those two inventories is where this story lives.
The official US and Iranian accounts of the strike package are not yet public. What exists, instead, is the fastest layer of any modern bombing campaign: volunteer mappers who read thermal anomalies, satellite-imagery differences, and witness posts in near real time. Monexus treats their lists as the best available open-source ground truth at this hour, not as confirmed targeting. The pattern of names, though, is consistent enough that it earns close reading.
The geography the mappers drew
The two confirmed-impact lists, posted by GeoPWatch and AMK_Mapping, cluster in two regions. The first runs along the Strait of Hormuz and into the Persian Gulf coast: Qeshm and Sirik on the large island at the strait's mouth; Bandar Abbas and Bandar-e-Jask on the mainland coast; Bushehr further up the Gulf, home to Iran's only operating nuclear power plant; and Khondab inland. The second cluster runs north into Khuzestan: Bandar-e-Mahshahr, Omidiyeh, Behbehan, Andimeshk, Dezful, and Ahvaz, the provincial capital.
Khuzestan matters because it hosts much of Iran's oil-and-gas production and its missile infrastructure aimed at the Gulf. Ahvaz and Dezful sit on the road and rail corridors that feed the southern launch areas. Behbehan and Omidiyeh are within range of the major gas-processing complexes. Western military analysts who follow the IRGC's air-defence network have previously flagged Dezful as a node of interest, though none of that work has yet been tied specifically to this strike package by the Telegram channels compiling the current list. The mapping community's judgment is that the targets are not symbolic: they span both the regime's industrial-revenue base (Khuzestan), its forward-defence systems (Gulf coast), and the country's nuclear-and-missile engineering footprint (Khondab and Bushehr).
Where the lists diverge
The earlier intelslava bulletin named nineteen locations in total; the cross-confirmed mapping pair names twelve. The difference is not trivial. Among the intelslava-only names are Abadan, Jask, and Khorramshahr, none of which appears in the GeoPWatch or AMK_Mapping strings. Khorramshahr sits across the Arvand Rud from Iraq's Basra and was a major Iranian naval base during the Iran-Iraq war; its absence from the geo-locators' lists suggests either that the intelslava number included Israeli-side strikes that have not been matched to Iranian-territory impacts, or that the geo-locators required stronger corroboration before naming a site.
That asymmetry is the method worth watching. Telegram channels that publish coordinates in real time face an incentive to be first and a counter-incentive to be wrong: a false claim of an impact at a sensitive nuclear facility is more reputationally costly than a missed one. The fact that two independent mapping teams converged on the same twelve names within eighteen minutes of each other is the closest thing to a confirmation available at this stage. Other OSINT accounts, including those that follow Iranian airspace via ADS-B exchange, had not, as of this writing, posted corroborating imagery for every site on the list. The list is consistent. It is not yet finished.
Why the mappers are running the briefing
Three hours into an active strike package against a regional state, the formal channels have not caught up. The Pentagon and CENTCOM did not immediately publish a target list; Iranian state media, including Tasnim and PressTV, were running casualty frames but had not, in the messages Monexus reviewed, contested the geography of the strikes in detail. The result is a vacuum that Telegram geolocators filled faster than either government could, which is itself the structural story.
Open-source intelligence on airstrikes used to require days: analysts with access to commercial satellite imagery, after-the-fact crater counting, and the slow triangulation of social-media posts. That cycle has collapsed. The same tools used to track Russian strikes on Ukrainian cities (Kyiv Post and United24 publish daily geolocated counts) and Israeli strikes on Gaza (Al Jazeera English and wire services host interactive impact maps) now operate on the same strike package within hours. The institutional memory of these methods sits in channels like GeoPWatch, AMK_Mapping, and intelslava, none of which are journalistic operations in the conventional sense, all of which are read, on days like this, by editors at wire desks. They are the first draft of the map; the official list is still being typed.
What the next hours decide
The question is what crosses from Telegram into wire copy by midday UTC. If the geographic list published by the mappers is endorsed, even implicitly, by Reuters, AFP, or the major US outlets, the Iranian strike package becomes a documented thirty-site-or-more campaign against the country's energy, missile, and nuclear infrastructure. That would imply a US readiness to widen the war beyond the air-defence-and-proxy targets that shaped earlier operations, and would set up the hardest decision of the next forty-eight hours: whether Tehran escalates in the Gulf, where commercial shipping runs through the strait the mappers just bracketed, or absorbs the strikes and waits for the diplomatic cycle.
Iranian state media have framed the strikes as a violation of sovereignty and signalled that retaliation is being prepared, without giving a vector or a timing. Western wire services have yet to publish a corresponding official target list. The consensus OSINT map is, for the moment, the only inventory readers, traders, and diplomats share. It will be tested against imagery, witness footage, and the eventual admissions and denials of the combatants. Until then, the strongest analytical position is the simplest one: this is what the mappers are seeing, with the caveat that this is exactly what the mappers are seeing.
Desk note: Monexus is publishing this on a four-source Telegram thread (intelslava, GeoPWatch ×2, AMK_Mapping) because the wire has not yet caught up to the mapping community. Where the intelslava and the GeoPWatch / AMK_Mapping lists diverge, we have flagged the divergence rather than smoothed it over. Once wire reporting confirms or revises the inventory, this piece will be updated or supplanted.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/intelslava
- https://t.me/GeoPWatch
- https://t.me/GeoPWatch
- https://t.me/AMK_Mapping