A live drone and missile strike map is a map of reports, not of confirmed hits. Every pin means that an air-defence command, a local outlet or a witness with a phone reported a strike, an explosion or an interception at a specific place and time. It is not a complete picture of a raid and it is not a casualty list. On battleMap these events arrive roughly every five minutes with a timestamp, coordinates, a category and a link to the source, and the most recent drone-related reports from all ten regions are collected on the live drone attack map page. This guide explains how to read such a map without mistaking a pin for a fact.
What does a live attack map actually show?
People searching for a "Ukraine attack map live" or a "missile attack map" usually expect one of two things: a map of air-raid alerts, which shows the regions under warning, or a map of events, which shows where something was reported to have happened. battleMap is the second kind. On the Russia–Ukraine war map, pins mark reported explosions, missile impacts, drone crashes, fires after a strike and interceptions announced by air defence.
Each event carries a timestamp, coordinates, a category and a link to the outlet or statement it came from. Territorial control is a separate layer — polygons showing who holds an area — and we explain it in how to read a frontline map. In practice, "live" means a stream of reports that are confirmed one after another, not a radar feed.
Where does the data about drone and missile strikes come from?
The sources are public and varied. For Ukraine, the backbone is the Ukrainian Air Force: warnings during a raid and a morning summary listing how many drones and missiles were launched and how many were shot down, complemented by regional administrations reporting damage on the ground. For Russia, the main sources are Ministry of Defence statements about drones "intercepted" over particular oblasts, posts by regional governors and local media covering fires at refineries or fuel depots. In the Middle East, the Israel Defense Forces, Iranian state media, the Houthi movement and the UK Maritime Trade Operations centre, which receives reports from ships, add their own streams.
On top of that come videos from social networks, geolocated by the OSINT community, and the reporting of local newsrooms. battleMap aggregates these public reports, geolocates them and shows each one with its origin, so every event can be traced back to a source. The pipeline, the classification rules and the known limits are documented on the data sources and methodology page.
What kinds of attacks appear on the map?
- Night-time drone waves — Russian Shahed/Geran drones launched in the evening fly for hours along different routes; the largest waves have run into the hundreds in a single night. The airframe itself is covered in what is a Shahed drone.
- Ballistic and cruise missiles — Iskander, Kinzhal, Kalibr and Kh-101 strikes usually arrive late in a wave, once air defence is busy with drones.
- Glide bombs — FAB bombs with glide kits dropped on front-line cities such as Kharkiv and Zaporizhzhia.
- FPV drones and loitering munitions — FPV drones and Lancets work along the line of contact and in the near rear; they show up as single reports of hits on vehicles or positions, not as a "raid".
- Ukrainian long-range strikes inside Russia — drones targeting refineries, fuel depots, airfields and defence plants; these reports are gathered on the Russia strikes map.
- The Middle East — direct Iran–Israel exchanges, Houthi attacks on shipping in the Red Sea and fire across the Israel–Lebanon border, starting from the Iran–Israel war map.
Why do "shot down" and "hit" mean different things?
Each side reports what serves it. The Russian Ministry of Defence announces the number of drones "intercepted" over an oblast and rarely admits a hit; Ukrainian sources describe a "refinery struck" and rarely mention the drones that did not arrive. Both statements can describe the same attack, and both reach the map as separate reports, each with its own attribution. The map does not decide who is right. It shows what was reported and by whom.
Finding out what actually happened takes independent evidence: geolocated footage, satellite imagery or fire detections from satellites. The step-by-step method is in how to verify video footage from conflict zones.
Why is there a delay between a strike and a pin?
Between an explosion and a pin lies a whole chain: the alert, a witness recording, a post on social media, geolocation, a local news item or an official statement, and finally aggregation. In practice that means minutes to a few hours, and the full shape of a night-time wave only becomes visible in the morning, when the Air Force publishes its summary. A "live" attack map should therefore be read as a stream of successively confirmed reports, not a real-time picture.
For the same reason, no pins does not mean no attacks. In occupied areas, in places without connectivity and where local media do not operate, there are fewer reports — not necessarily fewer strikes. The map mirrors the flow of information, and that flow is uneven.
How do you read a night-time wave?
- Look at the time, not the number of pins. A wave lasts for hours; pins appear where something fell or was intercepted, not along the whole flight path.
- Do not count pins as drones. One report may cover several aircraft, and one drone may generate several reports from different sources.
- Compare the map with the morning summary. The official count of launches and interceptions gives the scale; the map gives the geography.
- Watch for the "missile" category late in the wave. Ballistic and cruise strikes tend to come once the defences are saturated.
- Open the source. A report from an air-defence command and a report from an anonymous channel carry different weight, even though they look identical on the map.
What does an attack map not show?
Above all, it does not show drones in flight. Combat drones carry no transponders, so they never appear on flight-tracking maps, and military aircraft on combat missions usually do not broadcast their position either. The live aircraft and ship tracker will, however, show the indirect effects of a raid: civilian traffic routing around closed airspace or an airport suspending operations. How that layer works is explained under ADS-B in the glossary and in why planes disappear from radar.
The map also does not show missile trajectories, complete damage assessments or attacks nobody reported. The number of pins is not a measure of intensity; it is a measure of the number of public reports. That distinction matters whenever you compare two regions or two nights.
How do you use the attack map in practice?
Start with the live drone attack map, which lists the latest drone-related reports from all ten regions; clicking an event opens it on the map in the right region. On the main live war map, pick a region, open the event list and read from the newest down; every event has a share link, so a specific pin can be passed on. The free dashboard keeps 30 days of history, and the same events are available in structured form through the REST API with a key. And always open the source: the pin says "someone reported this"; the source says who, and on what basis.
Key takeaways
- A pin on an attack map is an attributed report, not a confirmed hit.
- Data comes from air-defence statements, local media, geolocated footage and the parties' own announcements.
- The two sides report different things by design: "intercepted" and "struck" can describe the same attack.
- A delay of minutes to hours is normal; a night-time wave is only fully visible in the morning.
- No public map shows drones in flight — you see effects and reactions, not the aircraft.