Telegram RegisterThe public register of Telegram
Telegram profile photo for Знеструмлення Сумщини

Channel

Знеструмлення Сумщини

@SumyOutage

Not marked by Telegram, checked 15 August 2026

On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

1,785subscribers

-14 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002194979551
TypeChannel
Username@SumyOutage
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/SumyOutage

Growth

1,7851,7991,7927 August 2026 — 1,799 subscribers7 August 2026 — 1,799 subscribers11 August 2026 — 1,798 subscribers17 August 2026 — 1,797 subscribers21 August 2026 — 1,794 subscribers24 August 2026 — 1,792 subscribers27 August 2026 — 1,790 subscribers30 August 2026 — 1,791 subscribers2 September 2026 — 1,787 subscribers6 September 2026 — 1,785 subscribers7 August 20266 September 2026
10 measurements spanning 29 days, net -14. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,783–1,801 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 03:381,785-2
2 Sept 2026, 04:241,787-4
30 Aug 2026, 05:471,791+1
27 Aug 2026, 07:551,790-2
24 Aug 2026, 13:251,792-2
21 Aug 2026, 03:321,794-3
17 Aug 2026, 22:231,797-1
11 Aug 2026, 14:021,798-1
7 Aug 2026, 20:491,799no change
7 Aug 2026, 18:401,799first reading

Engagement

20 posts held, back to 12 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Jul 2026, 05:52 UTC≈1,010 viewsread 7 August 2026

08:43+ 🐶 Декурія. Довідкова інформація: 💡 SumyOutage ГАВ 2025-2026.pdf 💡 SumyOutage СГАВ 2025-2026.pdf

1 Jul 2026, 13:55 UTC≈2,530 viewsread 7 August 2026

16:49+ СГАВ 1 2 3. 🐶 Декурія. ГПВ. Довідкова інформація: 💡 SumyOutage ГАВ 2025-2026.pdf 💡 SumyOutage СГАВ 2025-2026.pdf

1 Jul 2026, 05:36 UTC≈1,950 viewsread 7 August 2026

🔰 Тривають роботи в мережах, про які сповіщали на 29-30 червня. Продовжені через збільшення їх обсягу. 🔰 Продовжують діяти ГАВ (у частині Сумщині) та ГПВ. 🔰 Ситуація ускладнюється постійними атаками ворога. Сьогодні головна причина відключень — не погодні умови, а наслідки російських атак на енергетику. Ворог завдає ударів по всіх ланках енергосистеми. Значна частина енергооб'єктів в області пошкоджена або зруйно

30 Jun 2026, 16:09 UTC≈1,360 viewsread 7 August 2026
Photo

ЗАВТРА ➚ ‒‒:‒‒ offсайт 19:05 offканал

30 Jun 2026, 13:34 UTC≈1,290 viewsread 7 August 2026
Photo

СЬОГОДНІ ➚ ‒‒:‒‒ offсайт 16:27 offканал

30 Jun 2026, 13:25 UTC≈1,550 viewsread 7 August 2026
Photo

ЗАВТРА ➚ ‒‒:‒‒ offсайт 16:12 offканал

30 Jun 2026, 09:34 UTC≈1,520 viewsread 7 August 2026

11:12+ 🐶 Декурія. ГПВ. Довідкова інформація: 💡 SumyOutage ГАВ 2025-2026.pdf 💡 SumyOutage СГАВ 2025-2026.pdf

29 Jun 2026, 16:11 UTC≈1,380 viewsread 7 August 2026
Photo

ЗАВТРА ➚ 😴:😴 offсайт 19:04 offканал

28 Jun 2026, 05:17 UTC≈1,610 viewsread 7 August 2026

🔰 З 05:00 (ПН) до 22:00 (ВТ) На території області можливі тимчасові знеструмлення, пов'язані з роботами в мережах. Також можливі коливання напруги в електромережі.

Showing the 12 most recent of 20 posts we hold for @SumyOutage. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

❗️Тривога. Сумська область
@surenasumy · 87,936
Telegram ranks this channel #40 of 87 here — alongside 86 others — read 17 August 2026
SUMYLIKE TG
@sumyliketop · 155,390
Telegram ranks this channel #55 of 86 here — alongside 85 others — read 14 August 2026
"На межі" - медіа прикордоння
@namezhy · 30,739
Telegram ranks this channel #68 of 82 here — alongside 81 others — read 7 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Знеструмлення Сумщини” (@SumyOutage), 1,785 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/SumyOutage.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.