Telegram RegisterThe public register of Telegram
Telegram profile photo for Диспетчерская служба администрации Волновахского МО

Channel

Диспетчерская служба администрации Волновахского МО

@civilprotect22

On this record: Topic · Observations · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry

7,543subscribers

+333 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001761159683
TypeChannel
Username@civilprotect22
Created24 June 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/civilprotect22

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

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 in near-verbatim form 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@civilprotect22/6427 · this entry12 Nov 2026, 14:24 UTC@volnovahaDNR/11442312 Nov 2026, 15:09 UTC1.0046 minutes
@civilprotect22/6436 · this entry13 Nov 2026, 13:06 UTC@volnovahaDNR/11450613 Nov 2026, 13:25 UTC1.0019 minutes
@civilprotect22/6437 · this entry13 Nov 2026, 13:22 UTC@volnovahaDNR/11450713 Nov 2026, 13:25 UTC1.003 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@volnovahaDNR27 (8/8 hand-verifiable sample passed)1.0028 minutesthis entry (27–0)

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 251 comparable posts for this entry, running 4 August 2026 to 17 November 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).

Recorded under the key clone_source, last confirmed 18 November 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.

Growth

7,2107,5437,376.56 August 2026 — 7,210 subscribers6 August 2026 — 7,210 subscribers6 August 2026 — 7,228 subscribers9 August 2026 — 7,327 subscribers13 August 2026 — 7,343 subscribers16 August 2026 — 7,369 subscribers22 August 2026 — 7,378 subscribers25 August 2026 — 7,396 subscribers28 August 2026 — 7,411 subscribers31 August 2026 — 7,417 subscribers4 September 2026 — 7,421 subscribers9 September 2026 — 7,455 subscribers12 September 2026 — 7,456 subscribers17 September 2026 — 7,481 subscribers25 September 2026 — 7,520 subscribers5 October 2026 — 7,521 subscribers11 October 2026 — 7,505 subscribers20 October 2026 — 7,511 subscribers23 October 2026 — 7,503 subscribers26 October 2026 — 7,509 subscribers29 October 2026 — 7,527 subscribers2 November 2026 — 7,524 subscribers5 November 2026 — 7,532 subscribers8 November 2026 — 7,540 subscribers12 November 2026 — 7,537 subscribers18 November 2026 — 7,543 subscribers6 August 202618 November 2026
26 measurements spanning 104 days, net +333. 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 7,160–7,593 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
18 Nov 2026, 06:397,543+6
12 Nov 2026, 18:307,537-3
8 Nov 2026, 14:347,540+8
5 Nov 2026, 00:257,532+8
2 Nov 2026, 05:177,524-3
29 Oct 2026, 18:187,527+18
26 Oct 2026, 12:297,509+6
23 Oct 2026, 03:147,503-8
20 Oct 2026, 12:507,511+6
11 Oct 2026, 03:197,505-16
5 Oct 2026, 00:217,521+1
25 Sept 2026, 17:587,520+39
17 Sept 2026, 01:387,481+25
12 Sept 2026, 20:187,456+1
9 Sept 2026, 05:567,455+34
4 Sept 2026, 07:217,421+4
31 Aug 2026, 13:127,417+6
28 Aug 2026, 12:437,411+15
25 Aug 2026, 11:367,396+18
22 Aug 2026, 16:177,378first reading

Engagement

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

ERR · 30 days
41.4%
avg views ÷ 7,543 subscribers
Avg views / post
3,120
94 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
94
of 251 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 17 November 2026
Posts held251 (4 August 2026 – 17 November 2026)
Views total293,530
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 06:27 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 94 posts held from the last 30 days (2.13%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 13:33 UTC≈1,860 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 17.11.2026г., подача воды в г. Волноваха будет осуществляться по графику: с 18:00 до 22:00.

17 Nov 2026, 13:31 UTC≈1,860 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 17.11.2026г., восстановлена подача водоснабжения в пгт. Новотроицкое: ул.Шевцовой, ул.Советская, пер. Центральный. Ремонтные работы завершены.

17 Nov 2026, 13:30 UTC≈1,840 viewsread 18 November 2026

Диспетчерская служба информирует: В связи с ремонтными работами прекращена подача водоснабжения в с. Ближнее, ул. Октябрьская. Ремонтные работы переносятся на 18.11.2026г.

17 Nov 2026, 02:45 UTC≈2,010 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 17.11.2026 г., в связи с заполнением резервуаров подача водоснабжения на г. Волноваха (р-н СМЭУ) подаваться не будет. После заполнения резервуаров подача водоснабжения нормализуется.

17 Nov 2026, 02:45 UTC≈1,990 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 17.11.2026г., подача воды в г. Волноваха будет осуществляться по графику: с 06:00 до 09:00.

16 Nov 2026, 16:59 UTC≈2,120 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 16.11.2026г., в связи с ремонтными работами прекращена подача водоснабжения в пгт. Новотроицкое, перекрыты: ул.Шевцовой, ул.Советская, пер. Центральный. Ремонтные работы переносятся на 17.11.2026г.

16 Nov 2026, 14:12 UTC≈2,620 viewsread 18 November 2026

Диспетчерская служба информирует: В связи с ремонтными работами прекращена подача водоснабжения в с. Ближнее, ул. Октябрьская. Ремонтные работы переносятся на 17.11.2026г.

16 Nov 2026, 14:11 UTC≈3,520 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 16.11.2026г., подача воды в г. Волноваха (р-н СМЭУ) будет осуществляться по графику: с 18:00 до 21:00

16 Nov 2026, 14:11 UTC≈3,490 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 16.11.2026г., подача воды в г. Волноваха будет осуществляться по графику: с 18:00 до 22:00.

15 Nov 2026, 10:40 UTC≈2,540 viewsread 18 November 2026

Диспетчерская служба информирует: Сегодня, 15.11.2026, восстановлена подача электроэнергии в с. Ивановка, с. Новотатаровка, с. Новогригоровка, с. Новопавловка. Ремонтные работы завершены.

15 Nov 2026, 06:25 UTC≈2,560 viewsread 18 November 2026
Photo

❗️Увидел беспилотник — сообщи по номеру 109 Для защиты территории ДНР начала работу Республиканская служба по работе с населением при угрозах атак БПЛА. При обнаружении любой информации, способной помочь предотвратить атаку или снизить её последствия, необходимо сообщать по номеру 109. 🔻 Если вы заметили БПЛА в воздухе: • Немедленно позвоните по номеру 109 и сообщите место, время, количество дронов, их тип, направлен…

15 Nov 2026, 06:25 UTC≈2,190 viewsread 18 November 2026
Photo

‼️ ОМВД России «Волновахский» обращается ко всем жителям Волновахского округа‼️ ⚠️ Обнаружив подозрительный или взрывоопасный предмет (гранату, снаряд, мину, бомбу и т.п.), не подходите близко к нему, обратитесь к находящимся поблизости людям и попросите их немедленно сообщить об опасной находке в полицию по телефону 102. 📢 Если рядом ведутся какие-либо работы или живут люди, предупредите их; необходимо заглушить д…

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

Posts edited after publishing

@civilprotect22 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
8 August 2026

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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 18 November 2026 — this entry's latest reading, not the date you are reading this.

“Диспетчерская служба администрации Волновахского МО” (@civilprotect22), 7,543 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/civilprotect22.

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.