Tryvohystatistics

Updated

Укр

Kalynivska 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 7526 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?

347 h 36 min

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

No alerts since 00:00 today.

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 24 Sep, 11.9 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 348
  • Median 32 min
  • Average 59 min
  • Shortest 1 min
  • Longest 8 h 44 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.

Adamivkavillage
347 h 36 min
Antonopilvillage
347 h 36 min
Berezhanyvillage
347 h 36 min
Veselavillage
347 h 36 min
Vyshnevevillage
347 h 36 min
Hlynskvillage
347 h 36 min
Holendryvillage
347 h 36 min
Holubivkavillage
347 h 36 min
Hulivtsivillage
347 h 36 min
Druzhnevillage
347 h 36 min
Zabaravillage
347 h 36 min
Kalynivkacity
347 h 36 min
Kordelivkavillage
347 h 36 min
Lemeshivkavillage
347 h 36 min
Liulyntsivillage
347 h 36 min
Myrnevillage
347 h 36 min
Miziakivvillage
347 h 36 min
Monchyntsivillage
347 h 36 min
Napadivkavillage
347 h 36 min
Pavlenkyvillage
347 h 36 min
Pavlivkavillage
347 h 36 min
Panasivkavillage
347 h 36 min
Pysarivkavillage
347 h 36 min
Postolovevillage
347 h 36 min
Prylutskevillage
347 h 36 min
Radivkavillage
347 h 36 min
Raikyvillage
347 h 36 min
Rivnynnevillage
347 h 36 min
Salnykvillage
347 h 36 min
Sofiivkavillage
347 h 36 min
Tarasivkavillage
347 h 36 min
Uladivskevillage
347 h 36 min
Cherniatynvillage
347 h 36 min
Yablunevevillage
347 h 36 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

Most often at 01: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 03:00 — the alert touched this hour on 23.2% of days.