Tryvohystatistics

Updated

Укр

Opishnianska Hromada — air raid alerts

An alert is counted if it was anywhere within this territory. Simultaneous alerts across several of its parts are one episode.

Incomplete data: 1 gap, total 883 h. This does not mean there were no alerts. Alerts that ran through these periods are not counted in the durations, and shares of time are calculated against the time the source was actually watching.
Period
Other dates

How much time?

837 h 15 min

the alert sounded somewhere within this territory over the last 90 days — 38.8% of the time that the source was actually watching

Since 00:00 today — 10 h 8 min

Each bar is one day. Its height shows how many of the 24 hours had an alert running. Hatched bars are days the source did not report.

The chart needs JavaScript. The period totals are in the numbers above and to the right.

The loudest day was 30 Sep, 20.9 h. Hatched bars are days without observations.

Episodes over the last 90 days An episode is one unbroken stretch during which an alert was running somewhere within this territory. Alerts in different rayons merge into a single episode when they overlap in time; most episodes are made up of several announcements. How many times — how many such stretches the period contained. Median — the midpoint of the duration series: half the episodes are shorter than it, half are longer. Average — the sum of the durations divided by their count. A few long episodes pull it above the median. Shortest and longest — the ends of the same series. The longest one is an unbroken chain of alerts, not a single siren. Days observed — on how many days of the period the source reported anything at all. Time the source was silent does not count toward the duration: an episode breaks off at the start of the silence and starts over after it.

  • How many times 637
  • Median 54 min
  • Average 1 h 18 min
  • Shortest less than a minute
  • Longest 9 h 44 min
  • Days observed 91

Locations

The parts of this territory, from the loudest. Time is counted the same way — an alert anywhere within each of them.

Babanskevillage
837 h 15 min
Batkyvillage
837 h 15 min
Bezrukyvillage
837 h 15 min
Bukhalivkavillage
837 h 15 min
Vaskyvillage
837 h 15 min
Vilkhovevillage
837 h 15 min
Vintentsivillage
837 h 15 min
Voloshkovevillage
837 h 15 min
Hlynskevillage
837 h 15 min
Deriahyvillage
837 h 15 min
Dibrovavillage
837 h 15 min
Dranyvillage
837 h 15 min
Zaikyvillage
837 h 15 min
Zaichentsivillage
837 h 15 min
Kyriakovevillage
837 h 15 min
Klymenkyvillage
837 h 15 min
Kolchenkyvillage
837 h 15 min
Korliukovevillage
837 h 15 min
Lavryntsivillage
837 h 15 min
Lazkyvillage
837 h 15 min
Mysykyvillage
837 h 15 min
Opishniavillage
837 h 15 min
Popivkavillage
837 h 15 min
Pruhlyvillage
837 h 15 min
Ustymenkyvillage
837 h 15 min
Yabluchnevillage
837 h 15 min

When exactly?

A row is one day, a cell is one hour. The darker the cell, the larger the share of the hour the alert ran. That is how you can see that alerts cluster at night — no total reveals that.

The chart needs JavaScript.

quiet up to 9 min 9–27 min 27–45 min 45–60 min no data

Hover a cell to see the exact figures for that hour.

At what hour most often?

When alerts begin — for the chosen period. An alert that started in the evening and ran until morning is counted once, at the hour it began.

By hour of day

Most often at 17:00.

By day of week

Most often — Tue.

Does an alert usually happen at this hour?

A different question from the chart above: not when alerts began, but what share of days an alert ran during this hour at all — regardless of when it started.

Calculated over a fixed 56 days, not the period chosen above: over a shorter stretch, a single day would swing the share. It describes the past and is not a forecast — do not use it as grounds to ignore a signal.

Peak at 10:00 — the alert touched this hour on 85.7% of days.