Tryvohystatistics

Updated

Укр

Tomakivska 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 7571 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?

2759 h 15 min

the alert sounded somewhere within this territory over the last 365 days — 31.5% 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 3 Feb, 21.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 1894
  • Median 50 min
  • Average 1 h 27 min
  • Shortest less than a minute
  • Longest 16 h 8 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.

Barkovevillage
2759 h 15 min
Veselyi Yarvillage
2759 h 15 min
Vysokevillage
2759 h 15 min
Hannivkavillage
2759 h 15 min
Harbuzivkavillage
2759 h 15 min
Hrushevevillage
2759 h 15 min
Zaporizkevillage
2759 h 15 min
Zelenyi Haivillage
2759 h 15 min
Zelenyi Klynvillage
2759 h 15 min
Katoshchynevillage
2759 h 15 min
Kyslychuvatavillage
2759 h 15 min
Kytaihorodkavillage
2759 h 15 min
Krasnopilvillage
2759 h 15 min
Krutenkevillage
2759 h 15 min
Myroliubivkavillage
2759 h 15 min
Mykhailivkavillage
2759 h 15 min
Novoukrainkavillage
2759 h 15 min
Petrivkavillage
2759 h 15 min
Sadovevillage
2759 h 15 min
Semenivkavillage
2759 h 15 min
Serhiivkavillage
2759 h 15 min
Stepanivkavillage
2759 h 15 min
Tarasivkavillage
2759 h 15 min
Tomakivkavillage
2759 h 15 min
Urozhainevillage
2759 h 15 min
Chaikyvillage
2759 h 15 min
Chumakyvillage
2759 h 15 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 10: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 22:00 — the alert touched this hour on 64.3% of days.