Methodology

How this is built, what it counts, and what it does not claim.

246 incidents130 installations 11 countries100 satellite-confirmed 2026-02-28 → 2026-08-01

What this is

An open-source record of damage to United States, Israeli and Gulf state military and economic infrastructure during the ongoing conflict. Every incident names the asset struck, carries a verification tier proportionate to its evidence, and links to the material it rests on.

Maintained independently and published pseudonymously. Not affiliated with any government, military or media organisation. All source material is public.

How an incident is built

Public reporting is indexed in full, then filtered — so a change in what counts can be re-applied rather than losing what was already collected. Multi-image posts are expanded, because before-and-after pairs are often published as groups whose later frames carry no caption.
Reposts are collapsed by text and perceptual image hashing, so one photograph circulated by eight accounts counts once. Amplification is the most common thing mistaken for confirmation.
Every image is opened and examined, not judged from its caption. Text burned into the image — including Arabic and Farsi — is transcribed, because it often names the correct facility while the surrounding post does not. Dates burned into imagery outrank the date posted. Most reviewed imagery is rejected.
Where redistributed imagery is unusable, before-and-after comparisons are built from Copernicus Sentinel-2 — composited from the raw 10 m red, green and blue bands rather than the pre-rendered true-colour product, which saturates over bright desert, with one contrast stretch across both dates so rendering differences cannot pass as damage.
Coordinates are checked against the named installation rather than trusted from the report; those derived from a place name are marked approximate.

Verification tiers

SatelliteOverhead imagery shows the damage described.

OfficialConfirmed by a government, military or operator statement.

Multiple sourcesIndependently reported more than once, without overhead imagery.

ReportedReported but not independently corroborated.

UnverifiedRecorded for completeness; treat with caution.

Cost figures

The damage figure measures physical repair and replacement cost only — not lost revenue, production outage or wider economic disruption. Damage is priced against the asset struck, not the facility containing it, and never against an attacker's own valuation.

The figure is a range, because the alternative is a false precision. 179 of the 246 records carry a defensible figure. Summing the remaining 67 as exactly zero would assert that 67 confirmed strikes did no damage, which is plainly untrue — so the tracker shows both bounds:

LowOnly what is priced. The 67 records without a figure count as zero. This is a floor.

HighAdds 28 of those records, each valued at the median of comparable strikes of the same target type and severity.

Records marked Unconfirmed or Evacuated stay at zero in both bounds. An unconfirmed strike has not been shown to have happened, and an evacuation leaves a site intact. The rule is applied mechanically rather than record by record, so it can be checked and cannot be tuned to taste.

Aircraft lost in the air

48 US aircraft — 40 destroyed, 8 damaged — are counted alongside the assets struck on the ground. The accounting rests on a Congressional Research Service report, a US government source and a higher evidence tier than most records here. As published it itemises 42; a later upward revision of MQ‑9 Reaper losses carries the total to 48. Two of the 48 were destroyed on the ground and are marked as such.

They are included by default, and you can take them back out. The Assets struck panel carries a band labelled aircraft. Switch it off and both the asset count and the damage figure drop to fixed assets only, so what the headline is made of is always checkable rather than asserted. The airframe value added is $1.90B — replacement cost of the destroyed aircraft. Damaged aircraft are not costed: repair cost is not published and any figure would be a guess.

They are never placed on the map. An aircraft lost in the air has no coordinate and nothing to photograph, so it cannot carry the overhead evidence the map exists to show. Each one is a full record in Records, with its quantity, the cause as stated, and its citations.

Where a cause is given it is quoted as stated and no intent is inferred from it. Claims of further aircraft downed that carry no official acknowledgement are not counted.

Limits worth knowing

Imagery access is constrained. Commercial high-resolution coverage of the region is restricted, so overhead evidence leans on free Sentinel-2 at 10 m per pixel. Small or transient damage is not always resolvable.
Reporting is thin in some theatres. Several countries have criminalised posting about strikes on their territory — often exactly where the most significant damage occurred.
Absence is not evidence. A facility with no incidents may simply be one nobody photographed.

Credits and corrections

Imagery from Conflict Mapping / Soar Atlas is used under CC BY 4.0. Comparisons built here use modified Copernicus Sentinel-2 data (2026). Base map tiles by CARTO and Esri; map data © OpenStreetMap contributors.

Corrections are welcome and acted on — a misidentified facility, a bad coordinate, a duplicated strike, an image that does not show what it is captioned as. Write to damagetracker@proton.me.