Telegram RegisterThe public register of Telegram
Telegram profile photo for Дніпро Аварійна служба (Світло | Графіки)

Channel

Дніпро Аварійна служба (Світло | Графіки)

@avariykaaa

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

77,737subscribers

-1,187 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001950163436
TypeChannel
Username@avariykaaa
DescriptionАварійна служба м.Дніпро та область. Світло,Вода Посилання для друзів https://t.me/avariykaaa На біржі: adsell.me/r/CkAoy6 Адміністратор: @generalzvit Менеджер: @vector_roman
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/avariykaaa

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 72% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Dnipro_Svitloo/59966 Aug 2026, 15:45 UTC@avariykaaa/25378 · this entry6 Aug 2026, 15:45 UTC0.98under a minute
@avariykaaa/25380 · this entry6 Aug 2026, 18:47 UTC@Dnipro_Svitloo/59986 Aug 2026, 18:47 UTC0.98under a minute
@avariykaaa/25393 · this entry7 Aug 2026, 18:25 UTC@Dnipro_Svitloo/60117 Aug 2026, 18:25 UTC0.97under a minute
@avariykaaa/25392 · this entry7 Aug 2026, 15:38 UTC@Dnipro_Svitloo/60107 Aug 2026, 15:38 UTC0.97under a minute
@avariykaaa/25373 · this entry6 Aug 2026, 10:28 UTC@Dnipro_Svitloo/59916 Aug 2026, 10:28 UTC0.94under a minute
@avariykaaa/25375 · this entry6 Aug 2026, 11:47 UTC@Dnipro_Svitloo/59936 Aug 2026, 11:47 UTC0.92under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Dnipro_Svitloo9 (8/8 hand-verifiable sample passed)0.94under a minutethis entry (90)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 23 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @avariykaaa — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

77,73778,92478,330.57 August 2026 — 78,924 subscribers7 August 2026 — 78,922 subscribers8 August 2026 — 78,883 subscribers9 August 2026 — 78,853 subscribers10 August 2026 — 78,837 subscribers11 August 2026 — 78,817 subscribers12 August 2026 — 78,814 subscribers13 August 2026 — 78,787 subscribers14 August 2026 — 78,738 subscribers16 August 2026 — 78,692 subscribers17 August 2026 — 78,628 subscribers18 August 2026 — 78,594 subscribers19 August 2026 — 78,550 subscribers20 August 2026 — 78,508 subscribers21 August 2026 — 78,474 subscribers23 August 2026 — 78,414 subscribers24 August 2026 — 78,366 subscribers25 August 2026 — 78,307 subscribers26 August 2026 — 78,267 subscribers27 August 2026 — 78,263 subscribers28 August 2026 — 78,254 subscribers29 August 2026 — 78,213 subscribers31 August 2026 — 78,176 subscribers31 August 2026 — 78,155 subscribers2 September 2026 — 78,126 subscribers3 September 2026 — 78,099 subscribers4 September 2026 — 78,070 subscribers7 September 2026 — 78,045 subscribers10 September 2026 — 77,951 subscribers12 September 2026 — 77,873 subscribers14 September 2026 — 77,839 subscribers15 September 2026 — 77,790 subscribers17 September 2026 — 77,737 subscribers7 August 202617 September 2026
33 measurements spanning 41 days, net -1,187. 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 77,559–79,102 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 22:2177,737-53
15 Sept 2026, 18:5877,790-49
14 Sept 2026, 01:1977,839-34
12 Sept 2026, 11:3877,873-78
10 Sept 2026, 07:3577,951-94
7 Sept 2026, 02:3778,045-25
4 Sept 2026, 09:1778,070-29
3 Sept 2026, 00:1478,099-27
2 Sept 2026, 00:5478,126-29
31 Aug 2026, 23:2678,155-21
31 Aug 2026, 00:1278,176-37
29 Aug 2026, 22:2278,213-41
28 Aug 2026, 19:1778,254-9
27 Aug 2026, 19:1478,263-4
26 Aug 2026, 20:3778,267-40
25 Aug 2026, 20:4378,307-59
24 Aug 2026, 18:4778,366-48
23 Aug 2026, 00:3678,414-60
21 Aug 2026, 15:0978,474-34
20 Aug 2026, 15:3578,508first reading

Engagement

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

ERR · 30 days
21.5%
avg views ÷ 77,737 subscribers
Avg views / post
16,700
449 posts measured
Reaction rate
0.656%
reactions ÷ views · ER floor
Posts in window
449
of 679 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 21 September 2026
Posts held679 (6 August 202621 September 2026)
Views total7,514,030
Reactions total49,294
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 00:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
4,440
Videos
654
Links
22,400

Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
5m 40s
Average length
20s

Measured directly from 17 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

74,446 reactions across 679 posts, in 30 distinct kinds. The most used accounts for 35.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬26,40035.5%
😢20,18327.1%
9,00012.1%
🙏8,53011.5%
👍2,2763.06%
😱2,0602.77%
🤯1,5282.05%
👎1,1831.59%
😁7150.96%
🔥6330.85%
😡5980.803%
🤔2380.32%
💔1990.267%
👀1850.249%
👌1520.204%
🥰1180.159%
🎉1150.154%
🥱1000.134%
👏560.075%
🤨460.062%
10 further kinds1310.176%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 679 of the 679 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 74,446 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 679 most recent posts we hold, published 6 August 2026 to 21 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

21 Sept 2026, 23:48 UTC≈11,500 views291 reactionsread 22 September 2026

‼️Дніпропетровщина під ворожою атакою. Росіяни одночасно завдали ударів по промислових підприємствах у трьох містах області – Дніпрі, Кривому Розі та Павлограді. Зайнялися пожежі. Інформацію про постраждалих уточнюємо. https://t.me/avariykaaa

🤬140🙏118😢24😱8😁1

21 Sept 2026, 23:06 UTC≈15,100 views267 reactionsread 22 September 2026

Також вибухи пролунали і в Кривому Розі https://t.me/avariykaaa

🙏135🤬84😢3410😡4

21 Sept 2026, 23:02 UTC≈16,100 views317 reactionsread 22 September 2026

Вибухи пролунали у Дніпрі https://t.me/avariykaaa

🙏154🤬122😢29😱9🤯3

21 Sept 2026, 22:43 UTC≈16,600 views418 reactionsread 22 September 2026
Photo

🙏🏻Сподіваємося, що під час ворожої атаки не було поруч людей. Палає дуже сильно. https://t.me/avariykaaa

🙏212🤬115😢6319💔9

21 Sept 2026, 22:34 UTC≈16,300 views336 reactionsread 22 September 2026
Photo

😡Масштабна пожежа у Дніпрі після атаки русні https://t.me/avariykaaa

🤬196😢66🙏43😱19😡12

21 Sept 2026, 17:20 UTC≈20,300 views60 reactionsread 22 September 2026

⚡️Дніпро – на лінії усунення несправностей обладнання електромереж: вул. Мальовнича Балка пров. Пестушка Костя вул. Пестушка Костя пров. Семенка Юрія вул. Гімалайська вул. Загорянська вул. Новосічнева пров. Заповідний та прилеглі вул. Степової Дивізії (32, 34, 35, 36, 37...) вул. Високогірна (100, 101, 102, 103...) вул. Новошкільна (62, 64, 70, 74, 76...) Орієнтовний час відновлення електроенергії до 22:00. https:

😢2214🤬12😱6🙏6

21 Sept 2026, 17:10 UTC≈18,600 views121 reactionsread 22 September 2026

🏥Лікарні працюватимуть за новими правилами під час повітряних тривог: за жовтого рівня медзаклади продовжують роботу, а за червоного пацієнти й медики мають спускатися в укриття Водночас операції, реанімацію та іншу допомогу, яку небезпечно переривати, не зупинятимуть. Пацієнтів, яких неможливо перемістити, лікуватимуть у найбезпечніших доступних приміщеннях. https://t.me/avariykaaa

🙏75🤬31😱105

21 Sept 2026, 16:05 UTC≈18,700 views171 reactionsread 22 September 2026

❗️Одна людина загинула. Майже 50 разів ворог атакував чотири райони Дніпропетровщини ▪️У Дніпрі понівечена інфраструктура, магазин та дитячий садок. ▪️На Нікопольщині пошкоджена інфраструктура, магазин, приватний будинок, автівки. Загинула одна людина. ▪️На Криворіжжі росіяни цілили по Зеленодольській громаді. Понівечені підприємство і автівка. ▪️У Синельниківському районі противник завдав удару по Миколаївській

🤬87😢52🙏1913

21 Sept 2026, 15:18 UTC≈19,500 views387 reactionsread 22 September 2026

❗️Удари рф будуть не тільки по ТЕЦ, а й по котельням, щоб українці лишились без опалення. Це каже розвідка, — повідомляє Харченко. Найнебезпечніше, що котельні знаходяться безпосередньо в дворах житлових будинків, або по сусідству з ними. https://t.me/avariykaaa

🤬291😱42😢3014😁10

21 Sept 2026, 13:09 UTC≈20,600 views185 reactionsread 22 September 2026
Photo

⛈️У найближчу годину та до кінця дня у Дніпрі та по області очікується гроза. https://t.me/avariykaaa

😢93😱6513👍12🤩2

21 Sept 2026, 11:10 UTC≈21,100 views396 reactionsread 22 September 2026

😭У лікарні помер 20-річний юнак, якого важко поранили під час ворожої атаки на Дніпро 3 вересня Увесь цей час медики боролися за його життя. На жаль, травми виявилися надто тяжкими. Того дня росіяни вдарили по складах логістичної компанії. Внаслідок атаки постраждали семеро людей. https://t.me/avariykaaa

😢313💔46😡2111😱5

21 Sept 2026, 10:34 UTC≈20,100 views55 reactionsread 22 September 2026

💧Соборний район — тимчасово припинено подачу води на станції Лоцманська. 🚰Після завершення робіт водопостачання відновимо протягом дня. https://t.me/avariykaaa

🤬27😢165🤯5🙏2

Showing the 12 most recent of 679 posts we hold for @avariykaaa. 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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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.

Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 178,513
Telegram ranks this channel #8 of 69 here — alongside 68 others — read 12 August 2026
ProDnipro
@prodnipro1 · 26,232
Telegram ranks this channel #10 of 67 here — alongside 66 others — read 12 September 2026
Хуевый Днепр | Дніпро
@huevyi_dnepr · 168,126
Telegram ranks this channel #14 of 82 here — alongside 81 others — read 12 August 2026
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 275,953
Telegram ranks this channel #14 of 72 here — alongside 71 others — read 10 August 2026
ДС: новини Дніпро
@dnipro_now · 118,952
Telegram ranks this channel #16 of 86 here — alongside 85 others — read 14 August 2026
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 188,235
Telegram ranks this channel #16 of 82 here — alongside 81 others — read 11 August 2026
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 314,423
Telegram ranks this channel #17 of 81 here — alongside 80 others — read 10 August 2026
Повестки Днепр
@povestki_dnepr_TSK · 38,427
Telegram ranks this channel #18 of 71 here — alongside 70 others — read 31 August 2026
Труха⚡️Дніпро | Новини
@truexadnepr · 365,109
Telegram ranks this channel #19 of 79 here — alongside 78 others — read 10 August 2026
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,501
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 8 August 2026
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 86,159
Telegram ranks this channel #21 of 85 here — alongside 84 others — read 18 August 2026
Дніпро ⚡️Новини
@dnipro_insider · 40,593
Telegram ranks this channel #22 of 81 here — alongside 80 others — read 30 August 2026
Где повестки Днепр?
@agendaDnepr · 360,641
Telegram ranks this channel #23 of 70 here — alongside 69 others — read 10 August 2026
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,230
Telegram ranks this channel #24 of 78 here — alongside 77 others — read 14 September 2026
news pavlograd 📰🔝
@news_pavlograd · 37,838
Telegram ranks this channel #28 of 72 here — alongside 71 others — read 31 August 2026
Типичный Днепр 🇺🇦
@typical_dnepr · 24,336
Telegram ranks this channel #30 of 73 here — alongside 72 others — read 16 September 2026
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 238,598
Telegram ranks this channel #30 of 75 here — alongside 74 others — read 11 August 2026
Борис Філатов
@borys_filatovv · 78,548
Telegram ranks this channel #36 of 88 here — alongside 87 others — read 19 August 2026
‼️‼️‼️ Повітряна тривога Павлоград🚨‼️‼️
@pavlogradsirena · 26,132
Telegram ranks this channel #45 of 56 here — alongside 55 others — read 13 September 2026
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,595
Telegram ranks this channel #47 of 81 here — alongside 80 others — read 9 August 2026
Сірий Кріт
@seryy_krot99 · 40,515
Telegram ranks this channel #48 of 56 here — alongside 55 others — read 29 August 2026
Що? Куди?
@ShoKudaNik · 66,210
Telegram ranks this channel #52 of 75 here — alongside 74 others — read 12 September 2026
Pavlograd_now | 24/7 Павлоград Терновка Першотравенск
@pavlograd_now · 97,192
Telegram ranks this channel #59 of 75 here — alongside 74 others — read 16 August 2026
Петушиное кубло
@cockscublo · 61,879
Telegram ranks this channel #60 of 74 here — alongside 73 others — read 29 August 2026

This channel appears in 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Дніпро Аварійна служба (Світло | Графіки)” (@avariykaaa), 77,737 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/avariykaaa.

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.