Tryvohystatistics

Updated

Укр

Luhanska 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 7730 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?

1029 h 31 min

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

Since 00:00 today — 14 h 4 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 16 Aug, 24.0 h. Hatched bars are days without observations.

Episodes over the last 365 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 4
  • Median 146 h 23 min
  • Average 257 h 22 min
  • Shortest 2 h 43 min
  • Longest 734 h 1 min
  • Days observed 366

Locations

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

Vesela Horavillage
1029 h 31 min
Haiovevillage
1029 h 31 min
Zhovtevillage
1029 h 31 min
Zemlianevillage
1029 h 31 min
Zrazkovevillage
1029 h 31 min
Katerynivkavillage
1029 h 31 min
Kruta Horavillage
1029 h 31 min
Lymanvillage
1029 h 31 min
Lobachevevillage
1029 h 31 min
Luhanskcity
1029 h 31 min
Metalistvillage
1029 h 31 min
Mykolaivkavillage
1029 h 31 min
Novoselivkavillage
1029 h 31 min
Oboznevillage
1029 h 31 min
Oleksandrivskcity
1029 h 31 min
Pankivkavillage
1029 h 31 min
Pryvitnevillage
1029 h 31 min
Raivkavillage
1029 h 31 min
Rozkishnevillage
1029 h 31 min
Sabivkavillage
1029 h 31 min
Svitlevillage
1029 h 31 min
Sukhodilvillage
1029 h 31 min
Teplychnevillage
1029 h 31 min
Fabrychnevillage
1029 h 31 min
Khrystovevillage
1029 h 31 min
Shyshkovevillage
1029 h 31 min

When exactly?

The hourly grid is shown for periods up to 92 days — beyond that it becomes hundreds of rows with nothing visible in them. What time of day the alerts happen over this stretch is shown in the two charts below.

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

Alert starts, by hour of day.

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 16:00 — the alert touched this hour on 76.8% of days.